From: "Theodore Ts'o" <tytso@mit.edu>
To: libaokun1@huawei.com, linux-ext4@vger.kernel.org
Cc: "Theodore Ts'o" <tytso@mit.edu>,
lczerner@redhat.com, yebin10@huawei.com, ritesh.list@gmail.com,
yi.zhang@huawei.com, jack@suse.cz, linux-kernel@vger.kernel.org,
yukuai3@huawei.com, adilger.kernel@dilger.ca, enwlinux@gmail.com
Subject: Re: [PATCH] ext4: fix null-ptr-deref in ext4_write_info
Date: Tue, 27 Sep 2022 17:53:35 -0400 [thread overview]
Message-ID: <166431556707.3511882.842144509167145042.b4-ty@mit.edu> (raw)
In-Reply-To: <20220805123947.565152-1-libaokun1@huawei.com>
On Fri, 5 Aug 2022 20:39:47 +0800, Baokun Li wrote:
> I caught a null-ptr-deref bug as follows:
> ==================================================================
> KASAN: null-ptr-deref in range [0x0000000000000068-0x000000000000006f]
> CPU: 1 PID: 1589 Comm: umount Not tainted 5.10.0-02219-dirty #339
> RIP: 0010:ext4_write_info+0x53/0x1b0
> [...]
> Call Trace:
> dquot_writeback_dquots+0x341/0x9a0
> ext4_sync_fs+0x19e/0x800
> __sync_filesystem+0x83/0x100
> sync_filesystem+0x89/0xf0
> generic_shutdown_super+0x79/0x3e0
> kill_block_super+0xa1/0x110
> deactivate_locked_super+0xac/0x130
> deactivate_super+0xb6/0xd0
> cleanup_mnt+0x289/0x400
> __cleanup_mnt+0x16/0x20
> task_work_run+0x11c/0x1c0
> exit_to_user_mode_prepare+0x203/0x210
> syscall_exit_to_user_mode+0x5b/0x3a0
> do_syscall_64+0x59/0x70
> entry_SYSCALL_64_after_hwframe+0x44/0xa9
> ==================================================================
>
> [...]
Applied, thanks!
[1/1] ext4: fix null-ptr-deref in ext4_write_info
commit: 647642bf8f326994d7eaf785bba3fa9dad92cff0
Best regards,
--
Theodore Ts'o <tytso@mit.edu>
prev parent reply other threads:[~2022-09-27 21:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 12:39 [PATCH] ext4: fix null-ptr-deref in ext4_write_info Baokun Li
2022-08-05 13:07 ` Lukas Czerner
2022-08-10 7:20 ` Baokun Li
2022-08-15 15:34 ` Jan Kara
2022-09-27 21:53 ` 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=166431556707.3511882.842144509167145042.b4-ty@mit.edu \
--to=tytso@mit.edu \
--cc=adilger.kernel@dilger.ca \
--cc=enwlinux@gmail.com \
--cc=jack@suse.cz \
--cc=lczerner@redhat.com \
--cc=libaokun1@huawei.com \
--cc=linux-ext4@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ritesh.list@gmail.com \
--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.