From: syzbot ci <syzbot+cif9d1057e95d824fd@syzkaller.appspotmail.com>
To: syzbot@syzkaller.appspotmail.com, qwe.aldo@gmail.com,
syzbot@lists.linux.dev
Cc: syzbot@lists.linux.dev, syzkaller-bugs@googlegroups.com
Subject: [syzbot ci] Re: nfc: llcp: prevent resource leak on repeated connect after DM
Date: Sun, 27 Sep 2026 17:26:21 -0700 [thread overview]
Message-ID: <6ab9b42d.80e1c6cc.1e8e5f.0068.GAE@google.com> (raw)
In-Reply-To: <6ab9a58e.80e1c6cc.1e8e5f.0067.GAE@google.com>
syzbot ci has tested the suggested fix patch on top of the following series:
[v2] nfc: llcp: prevent resource leak on repeated connect after DM
https://lore.kernel.org/all/20260925184857.357926-1-qwe.aldo@gmail.com
Patch: https://ci.syzbot.org/jobs/3dd1e1c9-3945-4acc-ad14-ba72b83a6926/patch
The patch testing request could not be completed:
Testing failed due to an error.
Note: `#syz test` expects an incremental fix patch to be applied on top
of the tested series.
Testing results:
* [build 0] Build Patched: error
Full report is available here:
https://ci.syzbot.org/session/e4b2a66d-32a6-410d-9fe5-c4fe22bd6f0e
---
This report is generated by a bot. It may contain errors.
syzbot ci engineers can be reached at syzkaller@googlegroups.com.
next prev parent reply other threads:[~2026-09-28 0:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260927232347.2160670-1-qwe.aldo@gmail.com>
2026-09-27 23:23 ` Forwarded: nfc: llcp: clear stale device pointers on socket close syzbot
2026-09-28 0:26 ` syzbot ci [this message]
2026-09-28 1:46 Forwarded: [PATCH] " syzbot
2026-09-28 3:36 ` [syzbot ci] Re: nfc: llcp: prevent resource leak on repeated connect after DM syzbot ci
-- strict thread matches above, loose matches on Subject: below --
2026-09-25 18:48 [PATCH net v2] " Aldo Ariel Panzardo
2026-09-27 22:32 ` [syzbot ci] " syzbot ci
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=6ab9b42d.80e1c6cc.1e8e5f.0068.GAE@google.com \
--to=syzbot+cif9d1057e95d824fd@syzkaller.appspotmail.com \
--cc=qwe.aldo@gmail.com \
--cc=syzbot@lists.linux.dev \
--cc=syzbot@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 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.