From: Nikolay Borisov <nborisov@suse.com>
To: Christoph Anton Mitterer <calestyo@scientia.net>,
Btrfs BTRFS <linux-btrfs@vger.kernel.org>
Subject: Re: BUG: unable to handle kernel paging request at ffff9fb75f827100
Date: Wed, 21 Feb 2018 19:56:55 +0200 [thread overview]
Message-ID: <4ff967fe-a5b9-b3c0-a8b4-230aaf0bd225@suse.com> (raw)
In-Reply-To: <678817B2-D758-466B-A41D-FF8AFD0692AA@scientia.net>
On 21.02.2018 19:18, Christoph Anton Mitterer wrote:
> e8f1bc1493855e32b7a2a019decc3c353d94daf6
>
> That bug... When was that introduced and how can I find out whether an fs was affected/corrupted by this? Cause I've mounted and wrote to some extremely important (to me) fs recently.
The bug that this patch solves is unlikely to lead to fs-wide corruption
or indeed, any corruption at all. At mostit might make you deref a null
pointer and cause a crash - the first thing you reported. The follow up
reports don't really correspond to it.
The bug was introduced in 4.7 kernel (as evident from the stable tag on
the patch)
>
> Thanks, Chris.
>
next prev parent reply other threads:[~2018-02-21 17:56 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-21 4:09 BUG: unable to handle kernel paging request at ffff9fb75f827100 Christoph Anton Mitterer
2018-02-21 6:34 ` Nikolay Borisov
2018-02-21 14:20 ` Christoph Anton Mitterer
2018-02-21 14:51 ` Christoph Anton Mitterer
2018-02-21 17:18 ` Christoph Anton Mitterer
2018-02-21 17:56 ` Nikolay Borisov [this message]
2018-02-21 17:59 ` Christoph Anton Mitterer
2018-02-21 16:42 ` Christoph Anton Mitterer
2018-02-21 16:48 ` Christoph Anton Mitterer
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=4ff967fe-a5b9-b3c0-a8b4-230aaf0bd225@suse.com \
--to=nborisov@suse.com \
--cc=calestyo@scientia.net \
--cc=linux-btrfs@vger.kernel.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).