From: Andrew Morton <akpm@linux-foundation.org>
To: Marek Szyprowski <m.szyprowski@samsung.com>
Cc: Edward Adam Davis <eadavis@qq.com>,
syzbot+604424eb051c2f696163@syzkaller.appspotmail.com,
linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org,
phillip@squashfs.org.uk, squashfs-devel@lists.sourceforge.net,
syzkaller-bugs@googlegroups.com
Subject: Re: [PATCH] squashfs: fix oob in squashfs_readahead
Date: Fri, 17 Nov 2023 07:48:04 -0800 [thread overview]
Message-ID: <20231117074804.d475cadb2c5adbcbdb28f679@linux-foundation.org> (raw)
In-Reply-To: <b28b25ab-87eb-4905-855a-7809dda11f39@samsung.com>
On Fri, 17 Nov 2023 14:17:17 +0100 Marek Szyprowski <m.szyprowski@samsung.com> wrote:
> > Reported-and-tested-by: syzbot+604424eb051c2f696163@syzkaller.appspotmail.com
> > Fixes: f268eedddf35 ("squashfs: extend "page actor" to handle missing pages")
> > Signed-off-by: Edward Adam Davis <eadavis@qq.com>
>
> This patch, merged to linux-next as commit 1ff947abe24a ("squashfs: fix
> oob in squashfs_readahead"), breaks mounting squashfs volumes on all my
> test systems. Let me know if you need more information to debug this issue.
Thanks. The patch has been dropped.
prev parent reply other threads:[~2023-11-17 15:48 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 5:32 [syzbot] [squashfs?] KASAN: slab-out-of-bounds Write in squashfs_readahead (2) syzbot
2023-11-13 11:00 ` [syzbot] [PATCH] Test oob in squashfs readahead syzbot
2023-11-13 12:10 ` syzbot
2023-11-13 15:27 ` [syzbot] [squashfs?] KASAN: slab-out-of-bounds Write in squashfs_readahead (2) Phillip Lougher
2023-11-14 0:22 ` [syzbot] [PATCH] Test oob in squashfs readahead syzbot
2023-11-14 1:04 ` syzbot
2023-11-14 1:55 ` syzbot
2023-11-14 3:33 ` syzbot
2023-11-14 4:06 ` syzbot
2023-11-14 6:35 ` syzbot
2023-11-14 7:53 ` syzbot
2023-11-14 8:58 ` syzbot
2023-11-15 2:21 ` syzbot
[not found] ` <tencent_35864B36740976B766CA3CC936A496AA3609@qq.com>
2023-11-15 22:39 ` [PATCH] squashfs: fix oob in squashfs_readahead Andrew Morton
2023-11-16 15:14 ` Phillip Lougher
[not found] ` <CGME20231117131718eucas1p13328b32942cce99a99197eb28e14a981@eucas1p1.samsung.com>
2023-11-17 13:17 ` Marek Szyprowski
2023-11-17 15:48 ` Andrew Morton [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=20231117074804.d475cadb2c5adbcbdb28f679@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=eadavis@qq.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=phillip@squashfs.org.uk \
--cc=squashfs-devel@lists.sourceforge.net \
--cc=syzbot+604424eb051c2f696163@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