linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Joao Martins <joao.m.martins@oracle.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Jane Chu <jane.chu@oracle.com>,
	Naoya Horiguchi <naoya.horiguchi@nec.com>,
	linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
	Dan Williams <dan.j.williams@intel.com>
Subject: Re: [RFC] Missing compound_head() in memory-failure
Date: Tue, 1 Feb 2022 16:01:42 +0000	[thread overview]
Message-ID: <74d4bd51-6f16-542d-9710-3c609346cfe7@oracle.com> (raw)
In-Reply-To: <YflVxCA/rQ+3S2Up@casper.infradead.org>

On 2/1/22 15:46, Matthew Wilcox wrote:
> On Mon, Jan 31, 2022 at 08:54:39PM +0000, Joao Martins wrote:
>> On 1/31/22 20:29, Matthew Wilcox wrote:
>>> Unless I am mistaken, you have to pass the compound head of the page
>>> which has the error to collect_procs().  Am I mistaken?
>>>
>> -rc2 already has a fix for it:
>>
>> https://lore.kernel.org/linux-mm/20220129021420.PgBIZm-q9%25akpm@linux-foundation.org/
>>
>> Earlier in that function there's a:
>>
>> 	page = compound_head(page);
>>
>> So the @page passed to collect_procs() already is a head page.
> 
> It's wrong though ;-(  You set the HWPoison bit on the page after
> calling compound_head(), so you set the bit on the head page instead
> of the precise page that had the poison.
> 
Considering that on device-dax we would unmap the whole 2M page regardless
of the poisoned subpage isn't that actually representative still?

> I'm fixing this up as part of the folio patches, but you may wish to
> fix it earlier than that.



  reply	other threads:[~2022-02-01 16:02 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-31 20:29 [RFC] Missing compound_head() in memory-failure Matthew Wilcox
2022-01-31 20:54 ` Joao Martins
2022-02-01  2:34   ` Matthew Wilcox
2022-02-01 15:46   ` Matthew Wilcox
2022-02-01 16:01     ` Joao Martins [this message]
2022-02-01 17:40       ` Joao Martins
2022-02-01 17:47         ` Matthew Wilcox
2022-02-01 18:34           ` Joao Martins
2022-02-01 21:11     ` Jane Chu
2022-02-01 22:04       ` Joao Martins
2022-02-01 22:20         ` Dan Williams
2022-02-01 23:04           ` Jane Chu

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=74d4bd51-6f16-542d-9710-3c609346cfe7@oracle.com \
    --to=joao.m.martins@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=dan.j.williams@intel.com \
    --cc=jane.chu@oracle.com \
    --cc=linux-mm@kvack.org \
    --cc=naoya.horiguchi@nec.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;
as well as URLs for NNTP newsgroup(s).