From: syzbot <syzbot+fe84fc6a684e0beb86e2@syzkaller.appspotmail.com>
To: diasyzhangqing@gmail.com, iommu@lists.linux.dev, jgg@ziepe.ca,
joro@8bytes.org, kevin.tian@intel.com,
krystianmkaniewski@gmail.com, linux-kernel@vger.kernel.org,
robin.murphy@arm.com, syzkaller-bugs@googlegroups.com,
tz2294@columbia.edu, will@kernel.org
Subject: Re: [syzbot] [iommu?] memory leak in iommu_fwspec_init
Date: Fri, 06 Nov 2026 22:56:01 -0800 [thread overview]
Message-ID: <6aeecb81.01e61036.17c8d.0000.GAE@google.com> (raw)
In-Reply-To: <20261107140000.1-1-diasyzhangqing@gmail.com>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+fe84fc6a684e0beb86e2@syzkaller.appspotmail.com
Tested-by: syzbot+fe84fc6a684e0beb86e2@syzkaller.appspotmail.com
Tested on:
commit: d4872371 Merge tag 'arm64-fixes' of git://git.kernel.o..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=14fa24d9580000
kernel config: https://syzkaller.appspot.com/x/.config?x=4361b1bb937ae1c4
dashboard link: https://syzkaller.appspot.com/bug?extid=fe84fc6a684e0beb86e2
compiler: gcc (Debian 14.2.0-19) 14.2.0, GNU ld (GNU Binutils for Debian) 2.44
patch: https://syzkaller.appspot.com/x/patch.diff?x=14e0d8d9580000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2026-11-07 6:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-30 2:36 syzbot
2026-11-02 4:01 ` syzbot
2026-11-03 9:18 ` Forwarded: [PATCH] iommu: Fix dev_iommu leak on mock fwspec initialization failure syzbot
2026-11-06 15:08 ` [syzbot] [iommu?] memory leak in iommu_fwspec_init Krystian Kaniewski
2026-11-06 15:23 ` Krystian Kaniewski
2026-11-07 6:21 ` Forwarded: [PATCH] iommu: Fix dev_iommu leak on mock fwspec initialization failure syzbot
2026-11-07 14:00 ` Qing Zhang
2026-11-07 6:56 ` syzbot [this message]
[not found] <20261103091833.26594-1-diasyzhang@tencent.com>
2026-11-03 21:11 ` [syzbot] [iommu?] memory leak in iommu_fwspec_init syzbot
[not found] <20261107062125.452010-1-diasyzhangqing@gmail.com>
2026-11-07 6:37 ` syzbot
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=6aeecb81.01e61036.17c8d.0000.GAE@google.com \
--to=syzbot+fe84fc6a684e0beb86e2@syzkaller.appspotmail.com \
--cc=diasyzhangqing@gmail.com \
--cc=iommu@lists.linux.dev \
--cc=jgg@ziepe.ca \
--cc=joro@8bytes.org \
--cc=kevin.tian@intel.com \
--cc=krystianmkaniewski@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tz2294@columbia.edu \
--cc=will@kernel.org \
/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®