From: Christian Brauner <brauner@kernel.org>
To: Phillip Lougher <phillip@squashfs.org.uk>
Cc: Christian Brauner <brauner@kernel.org>,
Lizhi Xu <lizhi.xu@windriver.com>,
syzbot+24ac24ff58dc5b0d26b9@syzkaller.appspotmail.com,
akpm@linux-foundation.org, viro@zeniv.linux.org.uk, jack@suse.cz,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH V2] Squashfs: sanity check symbolic link size
Date: Tue, 13 Aug 2024 13:57:01 +0200 [thread overview]
Message-ID: <20240813-chemie-rotation-5ab2a178d043@brauner> (raw)
In-Reply-To: <20240811232821.13903-1-phillip@squashfs.org.uk>
On Mon, 12 Aug 2024 00:28:21 +0100, Phillip Lougher wrote:
> Syzkiller reports a "KMSAN: uninit-value in pick_link" bug.
>
> This is caused by an uninitialised page, which is ultimately caused
> by a corrupted symbolic link size read from disk.
>
> The reason why the corrupted symlink size causes an uninitialised
> page is due to the following sequence of events:
>
> [...]
I've grabbed this. Let me know if this needs to go through elsewhere.
---
Applied to the vfs.fixes branch of the vfs/vfs.git tree.
Patches in the vfs.fixes branch should appear in linux-next soon.
Please report any outstanding bugs that were missed during review in a
new review to the original patch series allowing us to drop it.
It's encouraged to provide Acked-bys and Reviewed-bys even though the
patch has now been applied. If possible patch trailers will be updated.
Note that commit hashes shown below are subject to change due to rebase,
trailer updates or similar. If in doubt, please check the listed branch.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/vfs/vfs.git
branch: vfs.fixes
[1/1] Squashfs: sanity check symbolic link size
https://git.kernel.org/vfs/vfs/c/810ee43d9cd2
prev parent reply other threads:[~2024-08-13 11:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-11 23:28 [PATCH V2] Squashfs: sanity check symbolic link size Phillip Lougher
2024-08-13 11:57 ` Christian Brauner [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=20240813-chemie-rotation-5ab2a178d043@brauner \
--to=brauner@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--cc=phillip@squashfs.org.uk \
--cc=syzbot+24ac24ff58dc5b0d26b9@syzkaller.appspotmail.com \
--cc=viro@zeniv.linux.org.uk \
/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).