Re: [PATCH 28/41] fs: Move metadata bhs tracking to a separate struct
Christoph Hellwig <[email protected]> Mon, 23 Mar 2026 22:47:13 -0700
| Newsgroups | gmane.linux.kernel.aio.general,gmane.linux.file-systems,gmane.linux.block,gmane.comp.file-systems.ext4,gmane.linux.kernel.mm |
|---|---|
| Message-ID | <[email protected]> |
On Fri, Mar 20, 2026 at 02:41:23PM +0100, Jan Kara wrote: > Instead of tracking metadata bhs for a mapping using i_private_list and > i_private_lock we create a dedicated mapping_metadata_bhs struct for it. s/we //g ? > So far this struct is embedded in address_space but that will be > switched for per-fs private inode parts later in the series. This also > changes the locking from bdev mapping's i_private_lock to lock embedded Instead of "to lock" I'd expect "to a new lock" or similar. > + /* > + * The locking dance is ugly here. We need to acquire lock s/lock/the lock/ > + * protecting metadata bh list while possibly racing with bh "the metadata bh list" (or spell out the field name without the "the"). Otherwise looks good: Reviewed-by: Christoph Hellwig <[email protected]> -- To unsubscribe, send a message with 'unsubscribe linux-aio' in the body to [email protected]. For more info on Linux AIO, see: http://www.kvack.org/aio/ Don't email: <a href=mailto:"[email protected]">[email protected]</a>