From: "Fabio M. De Francesco" <fmdefrancesco@gmail.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Ira Weiny <ira.weiny@intel.com>,
Catalin Marinas <catalin.marinas@arm.com>,
"Matthew Wilcox (Oracle)" <willy@infradead.org>,
Peter Collingbourne <pcc@google.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm/highmem: VM_BUG_ON() if offset + len > PAGE_SIZE
Date: Tue, 26 Apr 2022 23:10:44 +0200 [thread overview]
Message-ID: <5262074.Sb9uPGUboI@leap> (raw)
In-Reply-To: <20220426134811.63a398ea5d2212dfececfd83@linux-foundation.org>
On martedì 26 aprile 2022 22:48:11 CEST Andrew Morton wrote:
> On Tue, 26 Apr 2022 22:19:57 +0200 "Fabio M. De Francesco"
<fmdefrancesco@gmail.com> wrote:
>
> > On martedì 26 aprile 2022 21:34:12 CEST Andrew Morton wrote:
> > > On Tue, 26 Apr 2022 21:30:20 +0200 "Fabio M. De Francesco"
> > <fmdefrancesco@gmail.com> wrote:
> > >
> > > > Add VM_BUG_ON() bounds checking to make sure that, if "offset +
len>
> > > > PAGE_SIZE", memset() does not corrupt data in adjacent pages.
> > > >
> > >
> > > hm, why? To match all the other functions in there?
> > >
> > > I suppose that's logical. Or we could just delete all the other
> > > VM_BUG_ON()s. Have any of them proven to be at all useful?
> > >
> > I am not so sure about it being so useful. I just noted that
memzero_page()
> > is the only function of that family that is implemented with no
> > VM_BUG_ON(). I have no actual proofs of usefulness :(
> >
> > This is why yesterday I sent an "RFC Patch" (please see
> > https://lore.kernel.org/lkml/20220424104806.25396-1-fmdefrancesco@gmail.com/
> >
> > Soon after sending it I thought that VM_WARN_ON_ONCE() could have been
> > better suited, but Ira Weiny wrote to use VM_BUG_ON() for consistency.
> >
> > Now I could either delete all other VM_BUG_ON() or replace them with
> > VM_WARN_ON_ONCE() (or some other macro).
> >
> > Ah, a third solution might be to leave highmem.h as it is now :)
> >
> > What do you prefer?
>
> Merge this patch as-is, I guess. Going through and removing unuseful
> VM_BUG_ON()s is a separable activity.
>
Thanks!
While at this, I've just noted that you sent a confirmation which lists all
the patches of mine that are currently in your tree.
I see that you took v1 of "Extend and reorganize Highmem's documentation".
I suppose that you missed the v2 of that series at
https://lore.kernel.org/lkml/20220425162400.11334-1-fmdefrancesco@gmail.com/
Can you please check it?
Thanks,
Fabio
prev parent reply other threads:[~2022-04-26 21:10 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-26 19:30 [PATCH] mm/highmem: VM_BUG_ON() if offset + len > PAGE_SIZE Fabio M. De Francesco
2022-04-26 19:34 ` Andrew Morton
2022-04-26 20:19 ` Fabio M. De Francesco
2022-04-26 20:48 ` Andrew Morton
2022-04-26 21:10 ` Fabio M. De Francesco [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=5262074.Sb9uPGUboI@leap \
--to=fmdefrancesco@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=catalin.marinas@arm.com \
--cc=ira.weiny@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pcc@google.com \
--cc=willy@infradead.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