From: "Luck, Tony" <tony.luck@intel.com>
To: Aili Yao <yaoaili@kingsoft.com>,
Naoya Horiguchi <nao.horiguchi@gmail.com>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>,
Andrew Morton <akpm@linux-foundation.org>,
Oscar Salvador <osalvador@suse.de>,
"David Hildenbrand" <david@redhat.com>,
Borislav Petkov <bp@alien8.de>,
"Andy Lutomirski" <luto@kernel.org>,
Naoya Horiguchi <naoya.horiguchi@nec.com>,
Jue Wang <juew@google.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"yaoaili126@gmail.com" <yaoaili126@gmail.com>
Subject: RE: [PATCH v4 1/2] mm/memory-failure: Use a mutex to avoid memory_failure() races
Date: Thu, 6 May 2021 15:34:48 +0000 [thread overview]
Message-ID: <e50bbef65855443ba2be457a703ba1a5@intel.com> (raw)
In-Reply-To: <20210506173757.586580bd@alex-virtual-machine>
> Sorry to interrupt, I just thought one thing:
>
> This mutex seems not been bind to the error page, will there be some core case
> like test code or multi-poison case whick will break this mutex?
The mutex is a bigger hammer than strictly needed . If there are simultaneous
errors on different pages they could, int theory, proceed in parallel. But this mutex
will serialize the processing.
Is this a problem? Hopefully systems aren't seeing so many uncorrectable/recoverable
errors that this would be a significant bottleneck.
-Tony
next prev parent reply other threads:[~2021-05-06 15:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-27 6:29 [PATCH v4 0/2] mm,hwpoison: fix sending SIGBUS for Action Required MCE Naoya Horiguchi
2021-04-27 6:29 ` [PATCH v4 1/2] mm/memory-failure: Use a mutex to avoid memory_failure() races Naoya Horiguchi
2021-05-06 9:37 ` Aili Yao
2021-05-06 15:34 ` Luck, Tony [this message]
2021-04-27 6:29 ` [PATCH v4 2/2] mm,hwpoison: send SIGBUS when the page has already been poisoned Naoya Horiguchi
2021-05-07 9:38 ` Aili Yao
2021-05-10 7:21 ` HORIGUCHI NAOYA(堀口 直也)
2021-05-10 8:00 ` Aili Yao
2021-05-10 8:31 ` HORIGUCHI NAOYA(堀口 直也)
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=e50bbef65855443ba2be457a703ba1a5@intel.com \
--to=tony.luck@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bp@alien8.de \
--cc=david@redhat.com \
--cc=juew@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=luto@kernel.org \
--cc=nao.horiguchi@gmail.com \
--cc=naoya.horiguchi@nec.com \
--cc=osalvador@suse.de \
--cc=yaoaili126@gmail.com \
--cc=yaoaili@kingsoft.com \
/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