From: Zhang Yi <yi.zhang@huaweicloud.com>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, tytso@mit.edu,
adilger.kernel@dilger.ca, yi.zhang@huawei.com,
chengzhihao1@huawei.com, yukuai3@huawei.com
Subject: Re: [PATCH 11/12] ext4: cleanup ext4_get_dev_journal() and ext4_get_journal()
Date: Mon, 7 Aug 2023 19:36:45 +0800 [thread overview]
Message-ID: <1dcada9b-77ba-504e-b2dd-b0437afa9962@huaweicloud.com> (raw)
In-Reply-To: <20230803161446.6ac3ffhvfihmpyr6@quack3>
On 2023/8/4 0:14, Jan Kara wrote:
> On Tue 04-07-23 21:42:32, Zhang Yi wrote:
>> From: Zhang Yi <yi.zhang@huawei.com>
>>
>> Factor out a new helper form ext4_get_dev_journal() to get external
>> journal bdev and check validation of this device, drop ext4_blkdev_get()
>> helper, and also remove duplicate check of journal feature. It makes
>> ext4_get_dev_journal() more clear than before.
>>
>> Signed-off-by: Zhang Yi <yi.zhang@huawei.com>
>
> One comment below:
>
>> @@ -5838,25 +5815,25 @@ static journal_t *ext4_get_journal(struct super_block *sb,
>> return journal;
>> }
>>
>> -static journal_t *ext4_get_dev_journal(struct super_block *sb,
>> - dev_t j_dev)
>> +static struct block_device *ext4_get_journal_dev(struct super_block *sb,
>> + dev_t j_dev, ext4_fsblk_t *j_start,
>> + ext4_fsblk_t *j_len)
>> {
>> struct buffer_head *bh;
>> - journal_t *journal;
>> - ext4_fsblk_t start;
>> - ext4_fsblk_t len;
>> + struct block_device *bdev;
>> int hblock, blocksize;
>> ext4_fsblk_t sb_block;
>> unsigned long offset;
>> struct ext4_super_block *es;
>> - struct block_device *bdev;
>>
>> - if (WARN_ON_ONCE(!ext4_has_feature_journal(sb)))
>> - return NULL;
>> -
>> - bdev = ext4_blkdev_get(j_dev, sb);
>> - if (bdev == NULL)
>> + bdev = blkdev_get_by_dev(j_dev, BLK_OPEN_READ | BLK_OPEN_WRITE, sb,
>> + &ext4_holder_ops);
>> + if (IS_ERR(bdev)) {
>> + ext4_msg(sb, KERN_ERR,
>> + "failed to open journal device unknown-block(%u,%u) %ld",
>> + MAJOR(j_dev), MINOR(j_dev), PTR_ERR(bdev));
>> return NULL;
>> + }
>>
>> blocksize = sb->s_blocksize;
>> hblock = bdev_logical_block_size(bdev);
>> @@ -5869,7 +5846,8 @@ static journal_t *ext4_get_dev_journal(struct super_block *sb,
>> sb_block = EXT4_MIN_BLOCK_SIZE / blocksize;
>> offset = EXT4_MIN_BLOCK_SIZE % blocksize;
>> set_blocksize(bdev, blocksize);
>> - if (!(bh = __bread(bdev, sb_block, blocksize))) {
>> + bh = __bread(bdev, sb_block, blocksize);
>> + if (!bh) {
>> ext4_msg(sb, KERN_ERR, "couldn't read superblock of "
>> "external journal");
>> goto out_bdev;
>> @@ -5879,56 +5857,67 @@ static journal_t *ext4_get_dev_journal(struct super_block *sb,
>> if ((le16_to_cpu(es->s_magic) != EXT4_SUPER_MAGIC) ||
>> !(le32_to_cpu(es->s_feature_incompat) &
>> EXT4_FEATURE_INCOMPAT_JOURNAL_DEV)) {
>> - ext4_msg(sb, KERN_ERR, "external journal has "
>> - "bad superblock");
>> - brelse(bh);
>> - goto out_bdev;
>> + ext4_msg(sb, KERN_ERR, "external journal has bad superblock");
>> + goto out_bh;
>> }
>>
>> if ((le32_to_cpu(es->s_feature_ro_compat) &
>> EXT4_FEATURE_RO_COMPAT_METADATA_CSUM) &&
>> es->s_checksum != ext4_superblock_csum(sb, es)) {
>> - ext4_msg(sb, KERN_ERR, "external journal has "
>> - "corrupt superblock");
>> - brelse(bh);
>> - goto out_bdev;
>> + ext4_msg(sb, KERN_ERR, "external journal has corrupt superblock");
>> + goto out_bh;
>> }
>>
>> if (memcmp(EXT4_SB(sb)->s_es->s_journal_uuid, es->s_uuid, 16)) {
>> ext4_msg(sb, KERN_ERR, "journal UUID does not match");
>> - brelse(bh);
>> - goto out_bdev;
>> + goto out_bh;
>> }
>>
>> - len = ext4_blocks_count(es);
>> - start = sb_block + 1;
>> - brelse(bh); /* we're done with the superblock */
>> + brelse(bh);
>> + *j_start = sb_block + 1;
>> + *j_len = ext4_blocks_count(es);
>
> Here the ext4_blocks_count() is a use-after-free since you've released the
> bh a few lines above.
>
Indeed, will move it before the brelse(bh).
Thanks,
Yi.
next prev parent reply other threads:[~2023-08-07 11:54 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-04 13:42 [PATCH 00/12] ext4,jbd2: cleanup journal load and initialization process Zhang Yi
2023-07-04 13:42 ` [PATCH 01/12] jbd2: move load_superblock() dependent functions Zhang Yi
2023-08-03 14:07 ` Jan Kara
2023-07-04 13:42 ` [PATCH 02/12] jbd2: move load_superblock() into journal_init_common() Zhang Yi
2023-08-03 14:13 ` Jan Kara
2023-07-04 13:42 ` [PATCH 03/12] jbd2: don't load superblock in jbd2_journal_check_used_features() Zhang Yi
2023-08-03 14:14 ` Jan Kara
2023-07-04 13:42 ` [PATCH 04/12] jbd2: checking valid features early in journal_get_superblock() Zhang Yi
2023-08-03 14:18 ` Jan Kara
2023-07-04 13:42 ` [PATCH 05/12] jbd2: open code jbd2_verify_csum_type() helper Zhang Yi
2023-08-03 14:19 ` Jan Kara
2023-07-04 13:42 ` [PATCH 06/12] jbd2: cleanup load_superblock() Zhang Yi
2023-08-03 14:28 ` Jan Kara
2023-07-04 13:42 ` [PATCH 07/12] jbd2: add fast_commit space check Zhang Yi
2023-08-03 14:38 ` Jan Kara
2023-08-07 10:53 ` Zhang Yi
2023-08-07 13:33 ` Jan Kara
2023-07-04 13:42 ` [PATCH 08/12] jbd2: cleanup journal_init_common() Zhang Yi
2023-08-03 15:48 ` Jan Kara
2023-07-04 13:42 ` [PATCH 09/12] jbd2: drop useless error tag in jbd2_journal_wipe() Zhang Yi
2023-08-03 15:49 ` Jan Kara
2023-07-04 13:42 ` [PATCH 10/12] jbd2: jbd2_journal_init_{dev,inode} return proper error return value Zhang Yi
2023-08-03 15:56 ` Jan Kara
2023-07-04 13:42 ` [PATCH 11/12] ext4: cleanup ext4_get_dev_journal() and ext4_get_journal() Zhang Yi
2023-08-03 16:14 ` Jan Kara
2023-08-07 11:36 ` Zhang Yi [this message]
2023-07-04 13:42 ` [PATCH 12/12] ext4: ext4_get_{dev}_journal return proper error value Zhang Yi
2023-08-03 16:19 ` Jan Kara
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=1dcada9b-77ba-504e-b2dd-b0437afa9962@huaweicloud.com \
--to=yi.zhang@huaweicloud.com \
--cc=adilger.kernel@dilger.ca \
--cc=chengzhihao1@huawei.com \
--cc=jack@suse.cz \
--cc=linux-ext4@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yi.zhang@huawei.com \
--cc=yukuai3@huawei.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).