All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: cxg <evers_chen@163.com>
Cc: "David Hildenbrand (Arm)" <david@kernel.org>,
	Shuah Khan <shuah@kernel.org>, Lorenzo Stoakes <ljs@kernel.org>,
	linux-mm@kvack.org, linux-kselftest@vger.kernel.org,
	linux-kernel@vger.kernel.org, chenxionggui@lanxincomputing.com
Subject: Re: [PATCH] selftests/mm: Handle implicit read permissions in madv_populate
Date: Mon, 16 Nov 2026 21:59:30 -0800	[thread overview]
Message-ID: <20261116215930.f257ed2f010b4a4e9fdca410@linux-foundation.org> (raw)
In-Reply-To: <206b5151-c527-4b7b-8694-dd9c6cfd916f@163.com>

On Mon, 16 Nov 2026 15:00:56 +0800 cxg <evers_chen@163.com> wrote:

> Thanks for the suggestion.
> 
> Agreed. Since this behavior is specific to RISC-V, a simple 
> architecture-specific check is sufficient.
> 
> I've simplified the patch to use |#ifdef __riscv|in |test_prot_write()|, 
> removing the |/proc/self/maps|parsing and the additional PROT_NONE test.
> 
> The updated test passes all 16 tests on RISC-V with Linux 7.2.0.
> 
> Since the original patch is already in Andrew's mm tree, would you 
> prefer a v2 or an incremental fix?

A v2, please.

  reply	other threads:[~2026-11-17  5:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-12  3:18 [PATCH] selftests/mm: Handle implicit read permissions in madv_populate Xionggui Chen
2026-11-12 19:32 ` Andrew Morton
2026-11-13  2:12   ` 陈熊贵 
2026-11-13  3:15   ` cxg
2026-11-13  3:19 ` sashiko-bot
2026-11-13  3:58   ` cxg
2026-11-13 19:02 ` David Hildenbrand (Arm)
2026-11-16  7:00   ` cxg
2026-11-17  5:59     ` Andrew Morton [this message]
2026-11-17  7:06 ` [PATCH v2] selftests/mm: handle " Xionggui Chen
2026-11-17  8:58   ` David Hildenbrand (Arm)
2026-11-17  9:34     ` cxg
2026-11-18  7:07   ` sashiko-bot
2026-11-18  8:03     ` cxg
2026-11-18  8:12       ` Andrew Morton

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=20261116215930.f257ed2f010b4a4e9fdca410@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=chenxionggui@lanxincomputing.com \
    --cc=david@kernel.org \
    --cc=evers_chen@163.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=shuah@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.