public inbox for linux-mm@kvack.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Fujunjie <fujunjie1@qq.com>
Cc: Lorenzo Stoakes <ljs@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org, sj@kernel.org
Subject: Re: [PATCH v2] mm/madvise: reject invalid process_madvise() advice for zero-length vectors
Date: Sun, 3 May 2026 09:50:50 -0700	[thread overview]
Message-ID: <20260503095050.93736c201548e71d7d0f4210@linux-foundation.org> (raw)
In-Reply-To: <tencent_C18B14AEB4E720C5E2F9500FB9118E1B5607@qq.com>

On Mon, 4 May 2026 00:45:16 +0800 Fujunjie <fujunjie1@qq.com> wrote:

> >  		/*
> >  		 * An madvise operation is attempting to restart the syscall,
> >  		 * but we cannot proceed as it would not be correct to repeat
> > --
> > 2.54.0
> 
> Thanks, Lorenzo. That looks clearer to me too.
> 
> Since this is already in mm-unstable,

That's OK - it's called "unstable" for a reason!  Things come in,
things get removed, things get changed.  All the time.

> I'll wait for Andrew's preference.
> If a respin is needed, I'll fold this in together with SJ's comments.

Please prepare a v3 in the usual fashion.


      reply	other threads:[~2026-05-03 16:50 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-26 11:08 [PATCH] mm/madvise: reject invalid process_madvise() advice for zero-length vectors fujunjie
2026-04-26 19:41 ` Andrew Morton
2026-04-27  6:51   ` fujunjie
2026-04-27  7:49 ` David Hildenbrand (Arm)
2026-04-27  9:43 ` [PATCH v2] " fujunjie
2026-04-27 11:49   ` David Hildenbrand (Arm)
2026-04-28  7:05     ` Lorenzo Stoakes
2026-05-03 16:36     ` Fujunjie
2026-04-28  1:11   ` SeongJae Park
2026-04-28  7:02   ` Lorenzo Stoakes
2026-05-03 16:45     ` Fujunjie
2026-05-03 16:50       ` Andrew Morton [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=20260503095050.93736c201548e71d7d0f4210@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=fujunjie1@qq.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=sj@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