linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Marc Dionne <marc.c.dionne@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	 Vlastimil Babka <vbabka@suse.cz>
Subject: Re: [PATCH v2] tools/mm: Fix slabinfo crash when MAX_SLABS is exceeded
Date: Wed, 30 Oct 2024 08:47:19 -0300	[thread overview]
Message-ID: <CAB9dFdtd3paOGdYU8qJM5grD3pEFMiiCXk=fmPFW7k6s6yOBpQ@mail.gmail.com> (raw)
In-Reply-To: <20241029174518.60fa703fc9cb304d6e69e9a0@linux-foundation.org>

On Tue, Oct 29, 2024 at 9:45 PM Andrew Morton <akpm@linux-foundation.org> wrote:
>
> On Tue, 29 Oct 2024 13:13:41 -0300 Marc Dionne <marc.c.dionne@gmail.com> wrote:
>
> > From: Marc Dionne <marc.dionne@auristor.com>
> >
> > The number of slabs can easily exceed the hard coded MAX_SLABS in the
> > slabinfo tool, causing it to overwrite memory and crash.
> >
> > Increase the value of MAX_SLABS, and check if that has been exceeded for
> > each new slab, instead of at the end when it's already too late.  Also
> > move the check for MAX_ALIASES into the loop body.
>
> Thanks.
>
> > --- a/tools/mm/slabinfo.c
> > +++ b/tools/mm/slabinfo.c
> > @@ -21,7 +21,7 @@
> >  #include <regex.h>
> >  #include <errno.h>
> >
> > -#define MAX_SLABS 500
> > +#define MAX_SLABS 1000
>
> That isn't a very large increase.

Fair point, given how quickly it has grown, maybe something like 4k
would give more headroom.

>
> >  #define MAX_ALIASES 500
> >  #define MAX_NODES 1024
> >
> > @@ -1240,6 +1240,8 @@ static void read_slab_dir(void)
> >                               p--;
> >                       alias->ref = strdup(p);
> >                       alias++;
> > +                     if (alias - aliasinfo > MAX_ALIASES)
> > +                             fatal("Too many aliases\n");
> >                       break;
> >                  case DT_DIR:
> >                       if (chdir(de->d_name))
> > @@ -1301,6 +1303,8 @@ static void read_slab_dir(void)
> >                       if (slab->name[0] == ':')
> >                               alias_targets++;
> >                       slab++;
> > +                     if (slab - slabinfo > MAX_SLABS)
> > +                             fatal("Too many slabs\n");
> >                       break;
>
> This could be improved - if the number of slabs is exactly equal to
> MAX_SLABS we'll unnecessarily report an error.  Wouldn't this
> alteration be better?

Actually the issue is rather that we'll accept MAX_SLABS + 1 when we
shouldn't, so yes the checks should be >=, or could also be just ==,
sorry.

>
> --- a/tools/mm/slabinfo.c~tools-mm-fix-slabinfo-crash-when-max_slabs-is-exceeded-fix
> +++ a/tools/mm/slabinfo.c
> @@ -1228,6 +1228,8 @@ static void read_slab_dir(void)
>                                 continue;
>                 switch (de->d_type) {
>                    case DT_LNK:
> +                       if (alias - aliasinfo >= MAX_ALIASES)
> +                               fatal("Too many aliases\n");
>                         alias->name = strdup(de->d_name);
>                         count = readlink(de->d_name, buffer, sizeof(buffer)-1);
>
> @@ -1240,10 +1242,10 @@ static void read_slab_dir(void)
>                                 p--;
>                         alias->ref = strdup(p);
>                         alias++;
> -                       if (alias - aliasinfo > MAX_ALIASES)
> -                               fatal("Too many aliases\n");
>                         break;
>                    case DT_DIR:
> +                       if (slab - slabinfo >= MAX_SLABS)
> +                               fatal("Too many slabs\n");
>                         if (chdir(de->d_name))
>                                 fatal("Unable to access slab %s\n", slab->name);
>                         slab->name = strdup(de->d_name);
> @@ -1305,8 +1307,6 @@ static void read_slab_dir(void)
>                         if (slab->name[0] == ':')
>                                 alias_targets++;
>                         slab++;
> -                       if (slab - slabinfo > MAX_SLABS)
> -                               fatal("Too many slabs\n");
>                         break;
>                    default :
>                         fatal("Unknown file type %lx\n", de->d_type);
> _
>


      reply	other threads:[~2024-10-30 11:47 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29 16:13 Marc Dionne
2024-10-30  0:45 ` Andrew Morton
2024-10-30 11:47   ` Marc Dionne [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAB9dFdtd3paOGdYU8qJM5grD3pEFMiiCXk=fmPFW7k6s6yOBpQ@mail.gmail.com' \
    --to=marc.c.dionne@gmail.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=vbabka@suse.cz \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox