From: Matthew Wilcox <willy@infradead.org>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Tuo Cao <91tuocao@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm: folio-compat: fix bug for pagecache_get_page
Date: Wed, 19 Oct 2022 14:13:23 +0100 [thread overview]
Message-ID: <Y0/38zsvEgShWjLw@casper.infradead.org> (raw)
In-Reply-To: <20221018134834.97e685f9a9445c4553ce158b@linux-foundation.org>
On Tue, Oct 18, 2022 at 01:48:34PM -0700, Andrew Morton wrote:
> On Tue, 18 Oct 2022 15:39:39 +0100 Matthew Wilcox <willy@infradead.org> wrote:
>
> > On Tue, Oct 18, 2022 at 10:36:39PM +0800, Tuo Cao wrote:
> > > The folio returned from __filemap_get_folio may be a NULL, it will
> > > causes the kernel crash when access folio->page.
> >
> > This is not a bug. &folio->page does not dereference folio but performs
> > pointer arithmetic.
>
> This is the third attempt to "fix" this. So far. I think we should
> take the hint and make the check for a null pointer more explicit.
I think it's doing a great job of pointing out how many alleged
kernel programmers don't actually understand C and aren't capable of
searching mailing lists to see if somebody else already sent a patch.
Hopefully somebody's keeping track and is feeding this information into
their hiring algorithms.
The real solution is to convert all the callers of pagecache_get_page()
to use folios, and then we can delete this code. I have a small series
in progress. The amount of text savings is immense; half a kilobyte
from one conversion alone. Our compound_head() has got very bloated.
prev parent reply other threads:[~2022-10-19 13:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-18 14:36 Tuo Cao
2022-10-18 14:39 ` Matthew Wilcox
2022-10-18 20:48 ` Andrew Morton
2022-10-19 13:13 ` Matthew Wilcox [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=Y0/38zsvEgShWjLw@casper.infradead.org \
--to=willy@infradead.org \
--cc=91tuocao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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