[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210210164134.GA2169678@infradead.org>
Date: Wed, 10 Feb 2021 16:41:34 +0000
From: Christoph Hellwig <hch@...radead.org>
To: Ira Weiny <ira.weiny@...el.com>
Cc: Christoph Hellwig <hch@...radead.org>,
Andrew Morton <akpm@...ux-foundation.org>,
David Sterba <dsterba@...e.cz>,
Matthew Wilcox <willy@...radead.org>, clm@...com,
josef@...icpanda.com, linux-kernel@...r.kernel.org,
linux-fsdevel@...r.kernel.org
Subject: Re: [PATCH V2 4/8] mm/highmem: Add VM_BUG_ON() to mem*_page() calls
On Wed, Feb 10, 2021 at 08:29:01AM -0800, Ira Weiny wrote:
> On Wed, Feb 10, 2021 at 12:55:02PM +0000, Christoph Hellwig wrote:
> > On Tue, Feb 09, 2021 at 10:22:17PM -0800, ira.weiny@...el.com wrote:
> > > From: Ira Weiny <ira.weiny@...el.com>
> > >
> > > Add VM_BUG_ON bounds checks to ensure the newly lifted and created page
> > > memory operations do not result in corrupted data in neighbor pages and
> > > to make them consistent with zero_user().[1][2]
> >
> > s/VM_BUG_ON/BUG_ON/g ?
>
> Andrew wanted VM_BUG_ON.[1]
I don't care either way, but the patch uses BUG_ON, so the description
should match.
Powered by blists - more mailing lists