From: Christoph Hellwig <hch@lst.de>
To: Harry Yoo <harry@kernel.org>
Cc: Nickolai Zeldovich <nickolai@csail.mit.edu>,
Vlastimil Babka <vbabka@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Hao Li <hao.li@linux.dev>, Christoph Lameter <cl@gentwo.org>,
David Rientjes <rientjes@google.com>,
Roman Gushchin <roman.gushchin@linux.dev>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Christoph Hellwig <hch@lst.de>,
Vitaly Wool <vitaly.wool@konsulko.se>,
Vitaly Vul <vitaly.vul@partner.samsung.com>
Subject: Re: [PATCH v1] mempool: fix min_nr exceeding the elements array after concurrent resizes
Date: Wed, 28 Oct 2026 16:44:56 +0100 [thread overview]
Message-ID: <20261028154456.GA19025@lst.de> (raw)
In-Reply-To: <atJBK6hWYh2AqXwK@thinkstation>
The patch looks good:
Reviewed-by: Christoph Hellwig <hch@lst.de>
and I'm a bit surprised that someone folks later in the thread still
don't get the basic idea of separating fixes from random "improvements".
next prev parent reply other threads:[~2026-10-28 15:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-16 13:25 [PATCH v1] mempool: fix min_nr exceeding the elements array after concurrent resizes Nickolai Zeldovich
2026-10-16 15:46 ` Harry Yoo
2026-10-16 16:33 ` Nickolai Zeldovich
2026-10-18 15:01 ` Vitaly Wool
2026-10-18 15:15 ` Harry Yoo
2026-10-18 16:03 ` Vitaly Wool
2026-10-18 16:15 ` Harry Yoo
2026-10-19 6:45 ` Vitaly Wool
2026-10-19 13:27 ` Harry Yoo
2026-10-20 8:27 ` Vlastimil Babka (SUSE)
2026-10-20 10:50 ` Vitaly Wool
2026-10-20 10:57 ` Harry Yoo
2026-10-20 8:42 ` Vlastimil Babka (SUSE)
2026-10-29 20:51 ` Harry Yoo
2026-10-28 15:44 ` Christoph Hellwig [this message]
2026-10-29 20:59 ` Harry Yoo (Meta)
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=20261028154456.GA19025@lst.de \
--to=hch@lst.de \
--cc=akpm@linux-foundation.org \
--cc=cl@gentwo.org \
--cc=hao.li@linux.dev \
--cc=harry@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nickolai@csail.mit.edu \
--cc=rientjes@google.com \
--cc=roman.gushchin@linux.dev \
--cc=vbabka@kernel.org \
--cc=vitaly.vul@partner.samsung.com \
--cc=vitaly.wool@konsulko.se \
/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.