Re: [RFC v4 linux-next 06/19] cramfs: prevent direct access of bd_inode

To: Yu Kuai <yukuai1@xxxxxxxxxxxxxxx>
Subject: Re: [RFC v4 linux-next 06/19] cramfs: prevent direct access of bd_inode
From: Christoph Hellwig <hch@xxxxxx>
Date: Sun, 17 Mar 2024 22:23:44 +0100
Cc: jack@xxxxxxx, hch@xxxxxx, brauner@xxxxxxxxxx, axboe@xxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx, linux-block@xxxxxxxxxxxxxxx, yukuai3@xxxxxxxxxx, yi.zhang@xxxxxxxxxx, yangerkun@xxxxxxxxxx
In-reply-to: <20240222124555.2049140-7-yukuai1@huaweicloud.com>
References: <20240222124555.2049140-1-yukuai1@huaweicloud.com> <20240222124555.2049140-7-yukuai1@huaweicloud.com>
User-agent: Mutt/1.5.17 (2007-11-01)

Looks good:

Reviewed-by: Christoph Hellwig <hch@xxxxxx>

References:
- [RFC v4 linux-next 00/19] fs & block: remove bdev->bd_inode
  - From: Yu Kuai
- [RFC v4 linux-next 06/19] cramfs: prevent direct access of bd_inode
  - From: Yu Kuai