From: Andrew Morton <akpm@linux-foundation.org>
To: Lizhi Xu <lizhi.xu@windriver.com>
Cc: <syzbot+32d3767580a1ea339a81@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: squashfs_read_data need to check if the length is 0
Date: Thu, 16 Nov 2023 13:43:32 -0800 [thread overview]
Message-ID: <20231116134332.285510d340637171d2fe968c@linux-foundation.org> (raw)
In-Reply-To: <20231116031352.40853-1-lizhi.xu@windriver.com>
On Thu, 16 Nov 2023 11:13:52 +0800 Lizhi Xu <lizhi.xu@windriver.com> wrote:
> when the length passed in is 0, the subsequent process should be exited.
Thanks, but when fixing a bug, please always describe the runtime
effects of that bug. Amongst other things, other people need this
information to be able to decide which kernel versions need patching.
> Reported-by: syzbot+32d3767580a1ea339a81@syzkaller.appspotmail.com
Which is a reason why we're now adding the "Closes:" tag after
Reported-by:.
I googled the sysbot email address and so added
Closes: https://lkml.kernel.org/r/0000000000000526f2060a30a085@google.com
to the changelog.
I'll assume that a -stable kernel backport is needed.
next prev parent reply other threads:[~2023-11-16 21:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 13:10 [syzbot] [squashfs?] WARNING in squashfs_read_data syzbot
2023-11-16 1:14 ` [syzbot] [PATCH] test warning " syzbot
2023-11-16 3:13 ` [PATCH] squashfs: squashfs_read_data need to check if the length is 0 Lizhi Xu
2023-11-16 15:47 ` Phillip Lougher
2023-11-16 21:43 ` Andrew Morton [this message]
2023-11-17 2:17 ` Phillip Lougher
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=20231116134332.285510d340637171d2fe968c@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lizhi.xu@windriver.com \
--cc=phillip@squashfs.org.uk \
--cc=squashfs-devel@lists.sourceforge.net \
--cc=syzbot+32d3767580a1ea339a81@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
all inboxes | Powered by JetHome®