From: Andrew Price <anprice@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] KASAN: slab-out-of-bounds Write in gfs2_fill_super
Date: Wed, 14 Oct 2020 13:38:30 +0100 [thread overview]
Message-ID: <4d7412bf-15ba-58ee-3fa2-e6641dbca723@redhat.com> (raw)
In-Reply-To: <ceed2e5f-c03e-721f-ba2f-a581d6214e5c@gmail.com>
On 14/10/2020 13:19, Anant Thazhemadam wrote:
>
> On 30/09/20 7:52 pm, Andrew Price wrote:
>> On 30/09/2020 13:39, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following issue on:
>>>
>>> HEAD commit:??? fb0155a0 Merge tag 'nfs-for-5.9-3' of git://git.linux-nfs...
>>> git tree:?????? upstream
>>> console output: https://syzkaller.appspot.com/x/log.txt?x=13458c0f900000
>>> kernel config:? https://syzkaller.appspot.com/x/.config?x=adebb40048274f92
>>> dashboard link: https://syzkaller.appspot.com/bug?extid=af90d47a37376844e731
>
> Just saw this report.
> This seems to be the same as
> ??? https://syzkaller.appspot.com/bug?extid=a5e2482a693e6b1e444b ,
> for which I have recently sent in a fix (https://lkml.org/lkml/2020/10/13/588).
Thanks. The gfs2 maintainers are probably busy but I'll review the patch.
> Since the "Reported-by" tag in the patch sent is for the other instance of the
> same crash, can we close this one as a duplicate?
I expect the duplicates will get closed once a fix is in the tree so
there's no need to spend time on that.
Andy
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Price <anprice@redhat.com>
To: Anant Thazhemadam <anant.thazhemadam@gmail.com>
Cc: syzbot <syzbot+af90d47a37376844e731@syzkaller.appspotmail.com>,
agruenba@redhat.com, cluster-devel@redhat.com,
linux-kernel@vger.kernel.org, rpeterso@redhat.com,
syzkaller-bugs@googlegroups.com
Subject: Re: [Cluster-devel] KASAN: slab-out-of-bounds Write in gfs2_fill_super
Date: Wed, 14 Oct 2020 13:38:30 +0100 [thread overview]
Message-ID: <4d7412bf-15ba-58ee-3fa2-e6641dbca723@redhat.com> (raw)
In-Reply-To: <ceed2e5f-c03e-721f-ba2f-a581d6214e5c@gmail.com>
On 14/10/2020 13:19, Anant Thazhemadam wrote:
>
> On 30/09/20 7:52 pm, Andrew Price wrote:
>> On 30/09/2020 13:39, syzbot wrote:
>>> Hello,
>>>
>>> syzbot found the following issue on:
>>>
>>> HEAD commit: fb0155a0 Merge tag 'nfs-for-5.9-3' of git://git.linux-nfs...
>>> git tree: upstream
>>> console output: https://syzkaller.appspot.com/x/log.txt?x=13458c0f900000
>>> kernel config: https://syzkaller.appspot.com/x/.config?x=adebb40048274f92
>>> dashboard link: https://syzkaller.appspot.com/bug?extid=af90d47a37376844e731
>
> Just saw this report.
> This seems to be the same as
> https://syzkaller.appspot.com/bug?extid=a5e2482a693e6b1e444b ,
> for which I have recently sent in a fix (https://lkml.org/lkml/2020/10/13/588).
Thanks. The gfs2 maintainers are probably busy but I'll review the patch.
> Since the "Reported-by" tag in the patch sent is for the other instance of the
> same crash, can we close this one as a duplicate?
I expect the duplicates will get closed once a fix is in the tree so
there's no need to spend time on that.
Andy
next prev parent reply other threads:[~2020-10-14 12:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 12:39 [Cluster-devel] KASAN: slab-out-of-bounds Write in gfs2_fill_super syzbot
2020-09-30 12:39 ` syzbot
2020-09-30 14:22 ` [Cluster-devel] " Andrew Price
2020-09-30 14:22 ` Andrew Price
2020-10-14 12:19 ` Anant Thazhemadam
2020-10-14 12:19 ` Anant Thazhemadam
2020-10-14 12:38 ` Andrew Price [this message]
2020-10-14 12:38 ` Andrew Price
2020-10-14 13:16 ` [Cluster-devel] KASAN: slab-out-of-bounds Write in, gfs2_fill_super Fox Chen
2020-10-14 13:16 ` [Cluster-devel] KASAN: slab-out-of-bounds Write in,gfs2_fill_super Fox Chen
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=4d7412bf-15ba-58ee-3fa2-e6641dbca723@redhat.com \
--to=anprice@redhat.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.