From: Andrew Morton <akpm@linux-foundation.org>
To: Matthew Wilcox <willy@infradead.org>
Cc: linux-mm@kvack.org, "Borah,
Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
Subject: Re: [PATCH] mm: Fix list corruption in put_pages_list
Date: Wed, 6 Mar 2024 13:59:25 -0800 [thread overview]
Message-ID: <20240306135925.419a2320bfe98de9526b9e50@linux-foundation.org> (raw)
In-Reply-To: <Zejkd72TV80dMlQO@casper.infradead.org>
On Wed, 6 Mar 2024 21:47:35 +0000 Matthew Wilcox <willy@infradead.org> wrote:
> On Wed, Mar 06, 2024 at 01:45:57PM -0800, Andrew Morton wrote:
> > On Wed, 6 Mar 2024 21:27:30 +0000 "Matthew Wilcox (Oracle)" <willy@infradead.org> wrote:
> >
> > > My recent change to put_pages_list() dereferences folio->lru.next after
> > > returning the folio to the page allocator. Usually this is now on the
> > > pcp list with other free folios, so we try to free an already-free
> > > folio. This only happens with lists that have more than 15 entries, so
> > > it wasn't immediately discovered. Revert to using list_for_each_safe()
> > > so we dereference lru.next before disposing of the folio.
> > >
> > > Reported-by: "Borah, Chaitanya Kumar" <chaitanya.kumar.borah@intel.com>
> >
> > I'm unable to find the bug report on linux-mm. Help please?
>
> https://lore.kernel.org/intel-gfx/SJ1PR11MB61292145F3B79DA58ADDDA63B9232@SJ1PR11MB6129.namprd11.prod.outlook.com/
>
> (wasn't cc'd to linux-mm)
Ah, OK, thanks. I'll add that as a Closes: thingy.
prev parent reply other threads:[~2024-03-06 21:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-06 21:27 Matthew Wilcox (Oracle)
2024-03-06 21:45 ` Andrew Morton
2024-03-06 21:47 ` Matthew Wilcox
2024-03-06 21:59 ` Andrew Morton [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=20240306135925.419a2320bfe98de9526b9e50@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=chaitanya.kumar.borah@intel.com \
--cc=linux-mm@kvack.org \
--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