From: Oscar Salvador <osalvador@suse.de>
To: David Hildenbrand <david@redhat.com>
Cc: akpm@linux-foundation.org, n-horiguchi@ah.jp.nec.com,
vbabka@suse.cz, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] mm,hwpoison: Return -EBUSY when migration fails
Date: Wed, 9 Dec 2020 11:36:49 +0100 [thread overview]
Message-ID: <20201209103649.GD30892@linux> (raw)
In-Reply-To: <a30f4786-7c54-9fa8-0d39-6ae4d10f93c2@redhat.com>
On Wed, Dec 09, 2020 at 10:59:04AM +0100, David Hildenbrand wrote:
> On 09.12.20 10:28, Oscar Salvador wrote:
> Do we expect callers to retry immediately? -EAGAIN might make also
> sense. But -EBUSY is an obvious improvement. Do we have callers relying
> on this behavior?
Not really, unless something LTP takes a look at the error code in retries
in case EBUSY.
Take into account that most of the callers do not even really check the
return code (GHES, RAS/CEC, etc.)
--
Oscar Salvador
SUSE L3
next prev parent reply other threads:[~2020-12-09 10:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-09 9:28 Oscar Salvador
2020-12-09 9:57 ` HORIGUCHI NAOYA(堀口 直也)
2020-12-09 9:59 ` David Hildenbrand
2020-12-09 10:36 ` Oscar Salvador [this message]
2020-12-09 10:25 ` Vlastimil Babka
2020-12-09 10:38 ` Oscar Salvador
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=20201209103649.GD30892@linux \
--to=osalvador@suse.de \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=n-horiguchi@ah.jp.nec.com \
--cc=vbabka@suse.cz \
/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