From: David Sterba <dsterba@suse.cz>
To: Qu Wenruo <quwenruo.btrfs@gmx.com>
Cc: Anand Jain <anand.jain@oracle.com>, Qu Wenruo <wqu@suse.com>,
linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs: Do super block verification before writing it to disk
Date: Mon, 16 Apr 2018 21:03:09 +0200 [thread overview]
Message-ID: <20180416190309.GY21272@twin.jikos.cz> (raw)
In-Reply-To: <8cc34db9-0d09-38de-ac59-ed2be758de58@gmx.com>
On Mon, Apr 16, 2018 at 09:00:38PM +0800, Qu Wenruo wrote:
>
>
> On 2018年04月16日 20:55, Anand Jain wrote:
> >
> >
> > On 04/16/2018 10:02 AM, Qu Wenruo wrote:
> >> There are already 2 reports about strangely corrupted super blocks,
> >> where csum type and incompat flags get some obvious garbage, but csum
> >> still matches and all other vitals are correct.
> >>
> >> This normally means some kernel memory corruption happens, although the
> >> cause is unknown, at least detect it and prevent further corruption.
> >>
> >> Signed-off-by: Qu Wenruo <wqu@suse.com>
> >> ---
> >
> > Can you help point those 2 cases here?
>
> Did you mean the reported-by tags?
> If so, no problem.
Yes please, also describe what got corrupted in the changelog, besides
the links to the bugreports.
next prev parent reply other threads:[~2018-04-16 19:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-16 2:02 [PATCH] btrfs: Do super block verification before writing it to disk Qu Wenruo
2018-04-16 12:55 ` Anand Jain
2018-04-16 13:00 ` Qu Wenruo
2018-04-16 19:03 ` David Sterba [this message]
2018-04-16 19:02 ` David Sterba
-- strict thread matches above, loose matches on Subject: below --
2018-04-17 1:47 [PATCH v3] " Qu Wenruo
2018-04-17 9:05 ` [PATCH] " Anand Jain
2018-04-17 9:58 ` Qu Wenruo
2018-04-17 14:32 ` Anand Jain
2018-04-17 14:44 ` Qu Wenruo
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=20180416190309.GY21272@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=quwenruo.btrfs@gmx.com \
--cc=wqu@suse.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