From: Jens Axboe <axboe@kernel.dk>
To: Raphael Pinsonneault-Thibeault <rpthibeault@gmail.com>
Cc: jack@suse.cz,
syzbot+3ee481e21fd75e14c397@syzkaller.appspotmail.com,
linux-block@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-kernel-mentees@lists.linux.dev,
Yongpeng Yang <yangyongpeng@xiaomi.com>
Subject: Re: [PATCH v2] loop: don't change loop device under exclusive opener in loop_set_status
Date: Tue, 06 Jan 2026 05:30:34 -0700 [thread overview]
Message-ID: <176770263471.676302.4742936561051912973.b4-ty@kernel.dk> (raw)
In-Reply-To: <20251217190040.490204-2-rpthibeault@gmail.com>
On Wed, 17 Dec 2025 14:00:40 -0500, Raphael Pinsonneault-Thibeault wrote:
> loop_set_status() is allowed to change the loop device while there
> are other openers of the device, even exclusive ones.
>
> In this case, it causes a KASAN: slab-out-of-bounds Read in
> ext4_search_dir(), since when looking for an entry in an inlined
> directory, e_value_offs is changed underneath the filesystem by
> loop_set_status().
>
> [...]
Applied, thanks!
[1/1] loop: don't change loop device under exclusive opener in loop_set_status
commit: 08e136ebd193eae7d5eff4c66d576c4a2dabdc3f
Best regards,
--
Jens Axboe
prev parent reply other threads:[~2026-01-06 12:30 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-14 14:42 [PATCH] loop: don't change loop device under exclusive opener in loop_set_status Raphael Pinsonneault-Thibeault
2025-11-18 7:10 ` Yongpeng Yang
2025-12-01 12:38 ` Jan Kara
2025-12-02 9:03 ` Yongpeng Yang
2025-12-02 10:07 ` Jan Kara
2025-12-17 17:48 ` Jan Kara
2025-12-17 19:00 ` [PATCH v2] " Raphael Pinsonneault-Thibeault
2026-01-06 12:08 ` Jan Kara
2026-01-06 12:31 ` Jens Axboe
2026-01-06 12:30 ` Jens Axboe [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=176770263471.676302.4742936561051912973.b4-ty@kernel.dk \
--to=axboe@kernel.dk \
--cc=jack@suse.cz \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=rpthibeault@gmail.com \
--cc=syzbot+3ee481e21fd75e14c397@syzkaller.appspotmail.com \
--cc=yangyongpeng@xiaomi.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