From: Isaac Manjarres <isaacmanjarres@google.com>
To: David Hildenbrand <david@redhat.com>
Cc: Mike Rapoport <rppt@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
stable@vger.kernel.org, kernel-team@android.com,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v1] mm/mm_init: Fix hash table order logging in alloc_large_system_hash()
Date: Wed, 29 Oct 2025 08:50:39 -0700 [thread overview]
Message-ID: <aQI3z0x0gZ3T1fij@google.com> (raw)
In-Reply-To: <dcceca48-bbdc-4318-8c07-94bb7c2f75ff@redhat.com>
On Wed, Oct 29, 2025 at 11:03:18AM +0100, David Hildenbrand wrote:
> On 28.10.25 20:10, Isaac J. Manjarres wrote:
> > When emitting the order of the allocation for a hash table,
> > alloc_large_system_hash() unconditionally subtracts PAGE_SHIFT from
> > log base 2 of the allocation size. This is not correct if the
> > allocation size is smaller than a page, and yields a negative value
> > for the order as seen below:
> >
> > TCP established hash table entries: 32 (order: -4, 256 bytes, linear)
> > TCP bind hash table entries: 32 (order: -2, 1024 bytes, linear)
> >
> > Use get_order() to compute the order when emitting the hash table
> > information to correctly handle cases where the allocation size is
> > smaller than a page:
> >
> > TCP established hash table entries: 32 (order: 0, 256 bytes, linear)
> > TCP bind hash table entries: 32 (order: 0, 1024 bytes, linear)
> >
> > Fixes: 1da177e4c3f4 ("Linux-2.6.12-rc2")
> > Cc: stable@vger.kernel.org # v5.4+
>
> This is a pr_info(), why do you think this is stable material? Just curious,
> intuitively I'd have said that it's not that critical.
>
Hi David,
Thank you for taking the time to review this patch! I was just under the
impression that any bug--even those for informational logging--should be
sent to stable as well.
> > Signed-off-by: Isaac J. Manjarres <isaacmanjarres@google.com>
> > ---
> > mm/mm_init.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/mm/mm_init.c b/mm/mm_init.c
> > index 3db2dea7db4c..7712d887b696 100644
> > --- a/mm/mm_init.c
> > +++ b/mm/mm_init.c
> > @@ -2469,7 +2469,7 @@ void *__init alloc_large_system_hash(const char *tablename,
> > panic("Failed to allocate %s hash table\n", tablename);
> > pr_info("%s hash table entries: %ld (order: %d, %lu bytes, %s)\n",
> > - tablename, 1UL << log2qty, ilog2(size) - PAGE_SHIFT, size,
> > + tablename, 1UL << log2qty, get_order(size), size,
>
> So in case it's smaller than a page we now correctly return "0".
Correct.
> Reviewed-by: David Hildenbrand <david@redhat.com>
>
> --
> Cheers
>
> David / dhildenb
Thanks!
Isaac
next prev parent reply other threads:[~2025-10-29 15:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 19:10 [PATCH v1] mm/mm_init: Fix hash table order logging in alloc_large_system_hash() Isaac J. Manjarres
2025-10-29 10:03 ` David Hildenbrand
2025-10-29 15:50 ` Isaac Manjarres [this message]
2025-10-29 15:58 ` David Hildenbrand
2025-10-29 16:05 ` Isaac Manjarres
2025-10-29 11:45 ` Mike Rapoport
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=aQI3z0x0gZ3T1fij@google.com \
--to=isaacmanjarres@google.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@kernel.org \
--cc=stable@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.