From: Bob Peterson <rpeterso@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] [syzbot] [gfs2?] KASAN: use-after-free Read in qd_unlock (2)
Date: Wed, 26 Jul 2023 11:14:05 -0500 [thread overview]
Message-ID: <b3c92f88-4fb7-c4ee-e1a2-8f38150d7edd@redhat.com> (raw)
In-Reply-To: <0000000000009655cc060165265f@google.com>
On 7/26/23 10:03 AM, syzbot wrote:
> syzbot suspects this issue was fixed by commit:
>
> commit 41a37d157a613444c97e8f71a5fb2a21116b70d7
> Author: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> Date: Mon Dec 26 04:21:51 2022 +0000
>
> arm64: dts: qcom: qcs404: use symbol names for PCIe resets
>
> bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=17b48111a80000
> start commit: [unknown]
> git tree: upstream
> kernel config: https://syzkaller.appspot.com/x/.config?x=fe56f7d193926860
> dashboard link: https://syzkaller.appspot.com/bug?extid=3f6a670108ce43356017
> syz repro: https://syzkaller.appspot.com/x/repro.syz?x=1209f878c80000
> C reproducer: https://syzkaller.appspot.com/x/repro.c?x=111a48ab480000
>
> If the result looks correct, please mark the issue as fixed by replying with:
>
> #syz fix: arm64: dts: qcom: qcs404: use symbol names for PCIe resets
>
> For information about bisection process see: https://goo.gl/tpsmEJ#bisection
>
The bisect is very likely to be wrong.
I have a lot of patches to gfs2's quota code in linux-gfs2/bobquota that
I hope to get into the next merge window, but the critical patch has
already been merged. I'm still working on others.
Regards,
Bob Peterson
gfs2 file system
prev parent reply other threads:[~2023-07-26 16:14 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 21:20 [Cluster-devel] [syzbot] [gfs2?] KASAN: use-after-free Read in qd_unlock (2) syzbot
2023-01-27 5:10 ` [Cluster-devel] [PATCH] gfs2: Fix uaf for qda in gfs2_quota_sync eadavis
2023-01-30 14:32 ` Andreas Gruenbacher
2023-08-20 5:04 ` eadavis
2023-08-22 19:32 ` Bob Peterson
2023-08-23 13:43 ` Andreas Gruenbacher
2023-08-24 21:24 ` Andreas Gruenbacher
2023-07-26 15:03 ` [Cluster-devel] [syzbot] [gfs2?] KASAN: use-after-free Read in qd_unlock (2) syzbot
2023-07-26 15:09 ` Aleksandr Nogikh
2023-07-26 15:45 ` Dmitry Baryshkov
2023-07-27 1:09 ` Theodore Ts'o
2023-07-26 16:14 ` Bob Peterson [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=b3c92f88-4fb7-c4ee-e1a2-8f38150d7edd@redhat.com \
--to=rpeterso@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 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 read-only IMAP folder(s) and NNTP newsgroup(s).