From: Chris Mason <clm@fb.com>
To: Charles Gong <cggong@fb.com>, Alexander Viro <viro@zeniv.linux.org.uk>
Cc: <linux-fsdevel@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<kernel-team@fb.com>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] Fix sysrq emergency thaw
Date: Tue, 19 Jul 2016 08:15:45 -0400 [thread overview]
Message-ID: <bd757cf6-b467-4ebd-4bef-3fa16c93a61d@fb.com> (raw)
In-Reply-To: <5823da614460b8c40809e6e0a6de172a9c4f4611.1468015143.git.cggong@fb.com>
On 07/15/2016 08:38 PM, Charles Gong wrote:
> "SYSRQ + J" triggers a call to emergency_thaw_all(). Currently, this is an
> infinite loop. Once we trigger it, we'll need to do a hard power-cycle. There
> are users reporting this bug from 2012 to 2016, for example, at
> https://bugzilla.kernel.org/show_bug.cgi?id=47741.
>
> This happens because thaw_bdev() fails to return -EINVAL in the non-frozen case,
> and I fixed it so that do_one_thaw() can recognize this case and quit from
> looping. I checked that none of the other thaw_bdev() callers check the return
> value.
Hi Charles,
Can you please resend this without the hunks that change only
whitespace? Looks like your editor was properly killing off trailing
whitespace, but that's not related to your fix.
Also, please reference the commit where the regression was introduced:
commit 4504230a71566785a05d3e6b53fa1ee071b864eb
Author: Christoph Hellwig <hch@lst.de>
Date: Mon Aug 3 23:28:35 2009 +0200
freeze_bdev: grab active reference to frozen superblocks
Then you can add:
Reviewed-by: Chris Mason <clm@fb.com>
Thanks!
-chris
next parent reply other threads:[~2016-07-19 12:16 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5823da614460b8c40809e6e0a6de172a9c4f4611.1468015143.git.cggong@fb.com>
2016-07-19 12:15 ` Chris Mason [this message]
2016-07-20 23:11 Charles Gong
2016-08-05 20:14 ` Pavel Machek
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=bd757cf6-b467-4ebd-4bef-3fa16c93a61d@fb.com \
--to=clm@fb.com \
--cc=cggong@fb.com \
--cc=hch@lst.de \
--cc=kernel-team@fb.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome