From: Anand Jain <anand.jain@oracle.com>
To: linux-btrfs@vger.kernel.org
Cc: josef@toxicpanda.com
Subject: [PATCH v2 0/2] btrfs: match device by dev_t
Date: Sat, 11 Dec 2021 02:15:28 +0800 [thread overview]
Message-ID: <cover.1639155519.git.anand.jain@oracle.com> (raw)
Patch 1 is the actual bug fix and should go to stable 5.4 as well.
On 5.4 patch1 conflicts (outside of the changes in the patch),
so not yet marked for the stable.
Patch 2 simplifies calling lookup_bdev() in the device_matched()
by moving the same to the parent function two levels up.
Patch 2 is not merged with 1 because to keep the patch 1 changes local
to a function so that it can be easily backported to 5.4 and 5.10.
We should save the dev_t in struct btrfs_device with that may be
we could clean up a few more things, including fixing the below sparse
warning.
sparse: sparse: incorrect type in argument 1 (different address spaces)
For using without rcu:
error = lookup_bdev(device->name->str, &dev_old);
Anand Jain (2):
btrfs: harden identification of the stale device
btrfs: redeclare btrfs_stale_devices arg1 to dev_t
fs/btrfs/super.c | 8 +++++-
fs/btrfs/volumes.c | 72 +++++++++++++++++++++++++++++++++-------------
fs/btrfs/volumes.h | 2 +-
3 files changed, 60 insertions(+), 22 deletions(-)
--
2.33.1
next reply other threads:[~2021-12-10 18:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-10 18:15 Anand Jain [this message]
2021-12-10 18:15 ` [PATCH v2 1/2] btrfs: harden identification of the stale device Anand Jain
2021-12-13 15:04 ` Nikolay Borisov
2021-12-13 15:14 ` Nikolay Borisov
2021-12-14 14:27 ` Anand Jain
2022-01-04 18:56 ` David Sterba
2022-01-05 11:31 ` Anand Jain
2022-01-06 6:05 ` Su Yue
2022-01-07 14:48 ` David Sterba
2021-12-10 18:15 ` [PATCH v2 2/2] btrfs: redeclare btrfs_stale_devices arg1 to dev_t Anand Jain
2022-01-04 8:15 ` [PATCH v2 0/2] btrfs: match device by dev_t Anand Jain
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=cover.1639155519.git.anand.jain@oracle.com \
--to=anand.jain@oracle.com \
--cc=josef@toxicpanda.com \
--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 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.