public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Wei Yang <richard.weiyang@gmail.com>,
	peterz@infradead.org, vbabka@suse.cz, will@kernel.org,
	linyunsheng@huawei.com, aarcange@redhat.com, feng.tang@intel.com,
	ebiederm@xmission.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: remove offset check on page->compound_head and folio->lru
Date: Sat, 8 Jan 2022 00:49:53 +0000	[thread overview]
Message-ID: <YdjfsbAR0UlwyC6b@casper.infradead.org> (raw)
In-Reply-To: <20220107160825.13c71fdd871d7d5611d116b9@linux-foundation.org>

On Fri, Jan 07, 2022 at 04:08:25PM -0800, Andrew Morton wrote:
> On Fri, 7 Jan 2022 22:11:20 +0000 Matthew Wilcox <willy@infradead.org> wrote:
> 
> > On Fri, Jan 07, 2022 at 01:40:59PM +0000, Wei Yang wrote:
> > > On Fri, Jan 07, 2022 at 03:59:01AM +0000, Matthew Wilcox wrote:
> > > >On Thu, Jan 06, 2022 at 11:52:54PM +0000, Wei Yang wrote:
> > > >> FOLIO_MATCH() is used to make sure struct page and folio has identical
> > > >> layout for the first several words.
> > > >> 
> > > >> The comparison of offset between page->compound_head and folio->lru is
> > > >> more like an internal check in struct page.
> > > >> 
> > > >> This patch just removes it.
> > > >> 
> > > >> Signed-off-by: Wei Yang <richard.weiyang@gmail.com>
> > > >
> > > >No.
> > > 
> > > Hi, Matthew
> > > 
> > > Would you mind sharing some insight on this check?
> > 
> > It's right there in the comments.
> 
> Well I can't figure out which comment you're referring to?

         * WARNING: bit 0 of the first word is used for PageTail(). That
         * means the other users of this union MUST NOT use the bit to
         * avoid collision and false-positive PageTail().

> > If you can't be bothered to read, why should I write?
> 
> I don't think the punishment comes close to fitting the crime here :(

I felt I had to NACk it as quickly as possible so you didn't apply it.
Otherwise I'd've waited until I was back from holiday before replying
to the earlier patch.  But you applied that lickety-split, so clearly
I'm not allowed to take a week off.

  reply	other threads:[~2022-01-08  0:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 23:52 [PATCH] mm: remove offset check on page->compound_head and folio->lru Wei Yang
2022-01-07  3:59 ` Matthew Wilcox
2022-01-07 13:40   ` Wei Yang
2022-01-07 22:11     ` Matthew Wilcox
2022-01-08  0:08       ` Andrew Morton
2022-01-08  0:49         ` Matthew Wilcox [this message]
2022-01-08  2:41           ` Andrew Morton
2022-01-08  8:13           ` Wei Yang
2022-01-23  1:38             ` Wei Yang
2022-01-24 10:30               ` Vlastimil Babka
2022-01-24 22:55                 ` Wei Yang
2022-01-25 10:11                   ` Vlastimil Babka
2022-01-27  1:10                     ` Wei Yang
2022-01-27 15:42                       ` Vlastimil Babka
2022-01-29  0:47                         ` Wei Yang
2022-02-24  1:03                 ` Wei Yang
2022-02-17  0:34           ` Wei Yang
2022-01-08  0:27       ` Wei Yang

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=YdjfsbAR0UlwyC6b@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=aarcange@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=ebiederm@xmission.com \
    --cc=feng.tang@intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linyunsheng@huawei.com \
    --cc=peterz@infradead.org \
    --cc=richard.weiyang@gmail.com \
    --cc=vbabka@suse.cz \
    --cc=will@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