From: Andrew Morton <akpm@linux-foundation.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: david@kernel.org, ljs@kernel.org, jannh@google.com,
liam@infradead.org, willy@infradead.org, paulmck@kernel.org,
pfalcato@suse.de, usama.arif@linux.dev, vbabka@kernel.org,
linux-fsdevel@vger.kernel.org, yi1.lai@intel.com,
oe-lkp@lists.linux.dev, lkp@intel.com,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/1] selftests/proc: use RSS in /proc/pid/smaps_rollup tearing tests
Date: Mon, 2 Nov 2026 09:01:25 -0800 [thread overview]
Message-ID: <20261102090125.58a2e80d1669c681c33ed20b@linux-foundation.org> (raw)
In-Reply-To: <CAJuCfpGwZqGkOm25=BWAh2QgA8Y00OUmwxsDU+_qOsVsc+KHhg@mail.gmail.com>
On Mon, 2 Nov 2026 08:15:47 -0800 Suren Baghdasaryan <surenb@google.com> wrote:
> > Ah, I see now why handling READ_IMPLIES_EXEC is needed. Then your
> > complete fix looks fine. Perhaps we should mention this pre-ARMv6 CPU
> > detail in the changelog of your fix to explain why READ_IMPLIES_EXEC
> > is important here?
>
> I guess I have to ask whether you want to post your fix as a followup
> to mine or if I should fold them into one patch and post a v3. What's
> your preference?
yes, please just prepare a v3. I don't think bot will be offended.
next prev parent reply other threads:[~2026-11-02 17:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-01 15:45 Suren Baghdasaryan
2026-11-01 19:01 ` Andrew Morton
2026-11-02 13:08 ` Pedro Falcato
2026-11-02 15:31 ` Suren Baghdasaryan
2026-11-02 15:43 ` Suren Baghdasaryan
2026-11-02 16:01 ` Andrew Morton
2026-11-02 16:11 ` Suren Baghdasaryan
2026-11-02 16:15 ` Suren Baghdasaryan
2026-11-02 17:01 ` Andrew Morton [this message]
2026-11-02 17:21 ` Suren Baghdasaryan
2026-11-02 13:26 ` Pedro Falcato
2026-11-02 15:59 ` Suren Baghdasaryan
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=20261102090125.58a2e80d1669c681c33ed20b@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@kernel.org \
--cc=jannh@google.com \
--cc=liam@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ljs@kernel.org \
--cc=lkp@intel.com \
--cc=oe-lkp@lists.linux.dev \
--cc=paulmck@kernel.org \
--cc=pfalcato@suse.de \
--cc=surenb@google.com \
--cc=usama.arif@linux.dev \
--cc=vbabka@kernel.org \
--cc=willy@infradead.org \
--cc=yi1.lai@intel.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 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®