From: "David Hildenbrand (Arm)" <david@kernel.org>
To: Anshuman Tewari <anshumantewari123@gmail.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Lorenzo Stoakes <ljs@kernel.org>, Shuah Khan <shuah@kernel.org>,
Zi Yan <ziy@nvidia.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
"Liam R . Howlett" <liam@infradead.org>,
Nico Pache <nico.pache@linux.dev>,
Ryan Roberts <ryan.roberts@arm.com>, Dev Jain <dev.jain@arm.com>,
Barry Song <baohua@kernel.org>, Lance Yang <lance.yang@linux.dev>,
Usama Arif <usama.arif@linux.dev>,
Vlastimil Babka <vbabka@kernel.org>,
Mike Rapoport <rppt@kernel.org>,
Suren Baghdasaryan <surenb@google.com>,
Michal Hocko <mhocko@suse.com>,
linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] selftests/mm: check strdup() and fix buf leak in parse_test_type()
Date: Tue, 25 Aug 2026 13:03:21 +0200 [thread overview]
Message-ID: <b993b8b3-351c-4d2e-9bd9-12c622f427ff@kernel.org> (raw)
In-Reply-To: <CAJqi8kKaNsxBM86Hg4W09gLo2rj0+kc9dAvps48jmQCshUkxqQ@mail.gmail.com>
On 8/21/26 22:14, Anshuman Tewari wrote:
> Sounds good, no objection from me — happy to go with your version.
>
> One small ask: since this fixes the issue from my original patch,
> could you add a Reported-by: Anshuman Tewari
> <anshumantewari123@gmail.com> when you post/apply it?
We typically use Reported-by: for actual bugs and must accompany it with a
Closes: link. That doesn't quite apply here because this isn't really
something that would ever trigger and really needs fixing. It's
Suggested-by or Debugged-by also don't apply here.
I will add
"
This patch is inspired by previous work from Anshuman Tewari [1].
Link: https://lore.kernel.org/r/20260821114416.12255-1-anshumantewari123@gmail.com [1]
"
If you want you can send your Reviewed-by or Tested-by tags once
I send it out officially.
--
Cheers,
David
next prev parent reply other threads:[~2026-08-25 11:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-21 11:44 [PATCH] selftests/mm: check strdup() and fix buf leak in parse_test_type() Anshuman
2026-08-21 14:18 ` David Hildenbrand (Arm)
2026-08-21 16:09 ` Anshuman Tewari
2026-08-21 16:18 ` David Hildenbrand (Arm)
2026-08-21 20:14 ` Anshuman Tewari
2026-08-25 11:03 ` David Hildenbrand (Arm) [this message]
2026-08-25 18:20 ` Anshuman Tewari
2026-08-25 18:32 ` David Hildenbrand (Arm)
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=b993b8b3-351c-4d2e-9bd9-12c622f427ff@kernel.org \
--to=david@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=anshumantewari123@gmail.com \
--cc=baohua@kernel.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dev.jain@arm.com \
--cc=lance.yang@linux.dev \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=nico.pache@linux.dev \
--cc=rppt@kernel.org \
--cc=ryan.roberts@arm.com \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=ziy@nvidia.com \
/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.