From: Christian Brauner <brauner@kernel.org>
To: Christoph Hellwig <hch@lst.de>, Jan Kara <jack@suse.cz>,
Richard Weinberger <richard@nod.at>
Cc: Miquel Raynal <miquel.raynal@bootlin.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
linux-mtd@lists.infradead.org, linux-fsdevel@vger.kernel.org,
Christian Brauner <brauner@kernel.org>
Subject: [PATCH 0/2] mtd: switch to keying by dev_t
Date: Tue, 29 Aug 2023 17:23:55 +0200 [thread overview]
Message-ID: <20230829-vfs-super-mtd-v1-0-fecb572e5df3@kernel.org> (raw)
Hey,
For this cycle Jan, Christoph, and myself switched the generic super
code to key superblocks for block devices by device number (sb->s_dev)
instead of block device pointers (sb->s_bdev).
Not just does this allow us to defer opening block devices after we
allocated a superblock it also allows us to move closing block devices
to a later point to avoid various deadlocks.
Similar to the generic code for block devices we need to switch mtd
devices to rely on sb->s_dev instead of sb->s_mtd to avoid potential
use-after-free issues.
I plan on taking this upstream as a fix during the merge window.
Thanks!
Christian
---
---
base-commit: dc3216b1416056b04712e53431f6e9aefdc83177
change-id: 20230829-vfs-super-mtd-1bb602abfc00
next reply other threads:[~2023-08-29 15:25 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-29 15:23 Christian Brauner [this message]
2023-08-29 15:23 ` [PATCH 1/2] fs: export sget_dev() Christian Brauner
2023-08-29 16:29 ` Christian Brauner
2023-08-29 16:55 ` Richard Weinberger
2023-08-30 6:13 ` hch
2023-08-30 7:51 ` Christian Brauner
2023-08-30 6:14 ` Christoph Hellwig
2023-08-30 8:05 ` Christian Brauner
2023-08-30 9:38 ` Jan Kara
2023-08-30 9:43 ` Christian Brauner
2023-08-30 10:02 ` Christian Brauner
2023-08-30 10:10 ` Jan Kara
2023-08-29 15:23 ` [PATCH 2/2] mtd: key superblock by device number Christian Brauner
2023-08-30 10:13 ` Jan Kara
2023-08-30 9:50 ` [PATCH 0/2] mtd: switch to keying by dev_t Christian Brauner
2023-08-30 10:15 ` Richard Weinberger
2023-08-30 11:52 ` Christoph Hellwig
2023-08-30 12:19 ` Christian Brauner
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=20230829-vfs-super-mtd-v1-0-fecb572e5df3@kernel.org \
--to=brauner@kernel.org \
--cc=hch@lst.de \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=miquel.raynal@bootlin.com \
--cc=richard@nod.at \
--cc=vigneshr@ti.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;
as well as URLs for NNTP newsgroup(s).