From: Matthew Wilcox <willy@infradead.org>
To: Edward Adam Davis <eadavis@qq.com>
Cc: syzbot+c244f4a09ca85dd2ebc1@syzkaller.appspotmail.com,
jfs-discussion@lists.sourceforge.net,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
shaggy@kernel.org, syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] jfs: fix uaf in jfs_syncpt
Date: Tue, 20 Feb 2024 04:07:09 +0000 [thread overview]
Message-ID: <ZdQlbc0Hb0UZy6od@casper.infradead.org> (raw)
In-Reply-To: <tencent_E860EA86EF0ECC0079FA6D3C2D496D30940A@qq.com>
On Tue, Feb 20, 2024 at 11:55:18AM +0800, Edward Adam Davis wrote:
> During the execution of the jfs lazy commit, the jfs file system was unmounted,
> causing the sbi and jfs log objects to be released, triggering this issue.
> The solution is to add mutex to synchronize jfs lazy commit and jfs unmount
> operations.
Why is that the solution? LAZY_LOCK with IN_LAZYCOMMIT is supposed to
cover this. Please be more verbose in your commit messages. Describe
what is going wrong and why; that will allow people to understand why
this is the correct solution to the problem.
next prev parent reply other threads:[~2024-02-20 4:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 9:29 [syzbot] [jfs?] KASAN: slab-use-after-free Read " syzbot
2024-02-18 0:06 ` syzbot
2024-02-20 2:39 ` Edward Adam Davis
2024-02-20 3:05 ` syzbot
2024-02-20 3:23 ` Edward Adam Davis
2024-02-20 3:45 ` syzbot
2024-02-20 3:55 ` [PATCH] jfs: fix uaf " Edward Adam Davis
2024-02-20 4:07 ` Matthew Wilcox [this message]
2024-02-20 6:17 ` Edward Adam Davis
2026-04-30 23:13 ` Forwarded: Re: [syz] KASAN: slab-use-after-free Read " syzbot
2026-05-05 12:34 ` syzbot
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=ZdQlbc0Hb0UZy6od@casper.infradead.org \
--to=willy@infradead.org \
--cc=eadavis@qq.com \
--cc=jfs-discussion@lists.sourceforge.net \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shaggy@kernel.org \
--cc=syzbot+c244f4a09ca85dd2ebc1@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.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
Powered by JetHome