From: "Jose A. Perez de Azpillaga" <azpijr@gmail.com>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
박태선/컴퓨터·AI학부 <ts930@dgu.ac.kr>,
"Andrew Morton" <akpm@linux-foundation.org>,
"Liam R. Howlett" <liam@infradead.org>,
"Vlastimil Babka" <vbabka@kernel.org>,
"Jann Horn" <jannh@google.com>,
"Pedro Falcato" <pfalcato@suse.de>,
"Michal Hocko" <mhocko@suse.com>,
"Mike Rapoport" <rppt@kernel.org>,
"Suren Baghdasaryan" <surenb@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/mlock: fix zero-length request normalization and integer overflows
Date: Wed, 30 Sep 2026 22:42:37 +0200 [thread overview]
Message-ID: <ar1y9pekhVr19MDm@gmail.com> (raw)
In-Reply-To: <ar00Lx1xB5rvKOdu@gremlin>
On Wed, Sep 30, 2026 at 05:09:26PM +0100, Lorenzo Stoakes (ARM) wrote:
> On Wed, Sep 30, 2026 at 06:08:15PM +0200, David Hildenbrand (Arm) wrote:
> > >> So is this patch doing more harm than good?
> > >
> > > As above, I think the submitter has decided to drop this patch?
> >
> > Sure, but I still got CI noise because the patch was apparently not even
> > properly tested?
> >
> > So I really want people that send "fixes" to test stuff first.
>
> Entirely agreed!
if nobody has picked this up, could I take the wrap around part on its
own? I would implement it cleanly and test it before posting :)
--
cheers,
jose a. p-a
prev parent reply other threads:[~2026-09-30 20:42 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 5:56 Park Tae-sun
2026-09-29 8:30 ` Jose A. Perez de Azpillaga
2026-09-29 8:38 ` Lorenzo Stoakes (ARM)
2026-09-29 8:40 ` David Hildenbrand (Arm)
2026-09-29 8:47 ` Lorenzo Stoakes (ARM)
2026-09-29 9:39 ` 박태선/컴퓨터·AI학부
2026-09-30 11:43 ` David Hildenbrand (Arm)
2026-09-30 12:14 ` Lorenzo Stoakes (ARM)
2026-09-30 16:08 ` David Hildenbrand (Arm)
2026-09-30 16:09 ` Lorenzo Stoakes (ARM)
2026-09-30 20:42 ` Jose A. Perez de Azpillaga [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=ar1y9pekhVr19MDm@gmail.com \
--to=azpijr@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=rppt@kernel.org \
--cc=surenb@google.com \
--cc=ts930@dgu.ac.kr \
--cc=vbabka@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®