From: David Sterba <dsterba@suse.cz>
To: Josef Bacik <josef@toxicpanda.com>
Cc: Anand Jain <anand.jain@oracle.com>,
linux-btrfs@vger.kernel.org,
syzbot+4cfe71a4da060be47502@syzkaller.appspotmail.com
Subject: Re: [PATCH add reported by] btrfs: fix rw_devices count in __btrfs_free_extra_devids
Date: Thu, 24 Sep 2020 13:25:13 +0200 [thread overview]
Message-ID: <20200924112513.GT6756@twin.jikos.cz> (raw)
In-Reply-To: <a9910086-ad40-2cc8-8dd5-923ba6ff3990@toxicpanda.com>
On Wed, Sep 23, 2020 at 09:42:17AM -0400, Josef Bacik wrote:
> On 9/23/20 12:42 AM, Anand Jain wrote:
> > On 22/9/20 9:08 pm, Josef Bacik wrote:
> >> On 9/22/20 8:33 AM, Anand Jain wrote:
> Yeah I mean we do something in btrfs_init_dev_replace(), like when we search for
> the key, we double check to make sure we don't have a devid ==
> BTRFS_DEV_REPLACE_DEVID in our devices if we don't find a key. If we do we
> return -EIO and bail out of the mount. Thanks,
From user perspective, then do what? Or do we treat this with minimal
efforts to provide a sane fallback and error handling just to pass
fuzzers (like in many other cases)?
next prev parent reply other threads:[~2020-09-24 11:26 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-22 12:30 [PATCH] btrfs: fix rw_devices count in __btrfs_free_extra_devids Anand Jain
2020-09-22 12:33 ` [PATCH add reported by] " Anand Jain
2020-09-22 13:08 ` Josef Bacik
2020-09-23 4:42 ` Anand Jain
2020-09-23 13:42 ` Josef Bacik
2020-09-24 5:19 ` Anand Jain
2020-09-24 11:25 ` David Sterba [this message]
2020-09-24 14:02 ` Josef Bacik
2020-09-25 10:11 ` Anand Jain
2020-09-25 14:28 ` Josef Bacik
2020-10-06 13:12 ` Anand Jain
2020-09-22 12:33 Anand Jain
2020-10-06 13:08 ` [PATCH] btrfs: fix devid 0 without a replace item by failing the mount Anand Jain
2020-10-06 13:12 ` [PATCH v2] " Anand Jain
2020-10-06 14:54 ` [PATCH] " kernel test robot
2020-10-06 14:54 ` kernel test robot
2020-10-07 2:07 ` Anand Jain
2020-10-07 2:07 ` Anand Jain
2020-10-12 2:51 ` [kbuild-all] " Rong Chen
2020-10-12 2:51 ` Rong Chen
2020-10-06 16:44 ` kernel test robot
2020-10-06 16:44 ` kernel test robot
2020-10-06 13:12 [PATCH v2] " Anand Jain
2020-10-12 5:26 ` [PATCH v2 add prerequisite-patch-id] " Anand Jain
2020-10-21 4:02 ` [PATCH RESEND " Anand Jain
2020-10-12 5:36 ` [PATCH " Anand Jain
2020-10-21 5:49 ` [PATCH RESEND " kernel test robot
2020-10-21 5:49 ` kernel test robot
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=20200924112513.GT6756@twin.jikos.cz \
--to=dsterba@suse.cz \
--cc=anand.jain@oracle.com \
--cc=josef@toxicpanda.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=syzbot+4cfe71a4da060be47502@syzkaller.appspotmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.