From: "Theodore Ts'o" <tytso@mit.edu>
To: Baokun Li <libaokun1@huawei.com>, linux-ext4@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>,
yebin10@huawei.com, yukuai3@huawei.com, yi.zhang@huawei.com,
jack@suse.cz, adilger.kernel@dilger.ca,
Hulk Robot <hulkci@huawei.com>,
stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] ext4: fix race condition between ext4_write and ext4_convert_inline_data
Date: Wed, 18 May 2022 21:29:04 -0400 [thread overview]
Message-ID: <165292370259.1197022.17166433087491869557.b4-ty@mit.edu> (raw)
In-Reply-To: <20220428134031.4153381-1-libaokun1@huawei.com>
On Thu, 28 Apr 2022 21:40:31 +0800, Baokun Li wrote:
> Hulk Robot reported a BUG_ON:
> ==================================================================
> EXT4-fs error (device loop3): ext4_mb_generate_buddy:805: group 0,
> block bitmap and bg descriptor inconsistent: 25 vs 31513 free clusters
> kernel BUG at fs/ext4/ext4_jbd2.c:53!
> invalid opcode: 0000 [#1] SMP KASAN PTI
> CPU: 0 PID: 25371 Comm: syz-executor.3 Not tainted 5.10.0+ #1
> RIP: 0010:ext4_put_nojournal fs/ext4/ext4_jbd2.c:53 [inline]
> RIP: 0010:__ext4_journal_stop+0x10e/0x110 fs/ext4/ext4_jbd2.c:116
> [...]
> Call Trace:
> ext4_write_inline_data_end+0x59a/0x730 fs/ext4/inline.c:795
> generic_perform_write+0x279/0x3c0 mm/filemap.c:3344
> ext4_buffered_write_iter+0x2e3/0x3d0 fs/ext4/file.c:270
> ext4_file_write_iter+0x30a/0x11c0 fs/ext4/file.c:520
> do_iter_readv_writev+0x339/0x3c0 fs/read_write.c:732
> do_iter_write+0x107/0x430 fs/read_write.c:861
> vfs_writev fs/read_write.c:934 [inline]
> do_pwritev+0x1e5/0x380 fs/read_write.c:1031
> [...]
> ==================================================================
>
> [...]
Applied, thanks!
[1/1] ext4: fix race condition between ext4_write and ext4_convert_inline_data
commit: f87c7a4b084afc13190cbb263538e444cb2b392a
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2022-05-19 1:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-28 13:40 [PATCH v3] ext4: fix race condition between ext4_write and ext4_convert_inline_data Baokun Li
2022-04-28 16:57 ` Jan Kara
2022-05-09 1:25 ` libaokun (A)
2022-05-17 6:01 ` libaokun (A)
2022-05-19 1:29 ` Theodore Ts'o [this message]
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=165292370259.1197022.17166433087491869557.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=hulkci@huawei.com \
--cc=jack@suse.cz \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=yebin10@huawei.com \
--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 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.