From: syzbot <syzbot+1f1fbecb9413cdbfbef8@syzkaller•appspotmail.com>
To: ast@kernel•org, bpf@vger•kernel.org,
linux-kernel@vger•kernel.org, listout@listout•xyz,
netdev@vger•kernel.org, syzkaller-bugs@googlegroups•com,
yonghong.song@linux•dev
Subject: Re: [syzbot] [bpf?] [net?] BUG: sleeping function called from invalid context in sock_map_delete_elem
Date: Thu, 09 Oct 2025 16:29:02 -0700 [thread overview]
Message-ID: <68e8453e.050a0220.91a22.000f.GAE@google.com> (raw)
In-Reply-To: <20251009222836.1433789-1-listout@listout.xyz>
Hello,
syzbot has tested the proposed patch and the reproducer did not trigger any issue:
Reported-by: syzbot+1f1fbecb9413cdbfbef8@syzkaller•appspotmail.com
Tested-by: syzbot+1f1fbecb9413cdbfbef8@syzkaller•appspotmail.com
Tested on:
commit: 5472d60c Merge tag 'trace-v6.18-2' of git://git.kernel..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=159b91e2580000
kernel config: https://syzkaller.appspot.com/x/.config?x=2b842a78bbee09b1
dashboard link: https://syzkaller.appspot.com/bug?extid=1f1fbecb9413cdbfbef8
compiler: Debian clang version 20.1.8 (++20250708063551+0c9f909b7976-1~exp1~20250708183702.136), Debian LLD 20.1.8
patch: https://syzkaller.appspot.com/x/patch.diff?x=11f50dcd980000
Note: testing is done by a robot and is best-effort only.
next prev parent reply other threads:[~2025-10-09 23:29 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-27 23:56 [syzbot] [bpf?] [net?] BUG: sleeping function called from invalid context in sock_map_delete_elem syzbot
2025-10-09 22:28 ` [PATCH] bpf: avoid sleeping in invalid context during sock_map_delete_elem path Brahmajit Das
2025-10-09 22:38 ` Alexei Starovoitov
2025-10-09 23:29 ` syzbot [this message]
2025-10-13 17:11 ` [PATCH v2] " Brahmajit Das
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=68e8453e.050a0220.91a22.000f.GAE@google.com \
--to=syzbot+1f1fbecb9413cdbfbef8@syzkaller$(echo .)appspotmail.com \
--cc=ast@kernel$(echo .)org \
--cc=bpf@vger$(echo .)kernel.org \
--cc=linux-kernel@vger$(echo .)kernel.org \
--cc=listout@listout$(echo .)xyz \
--cc=netdev@vger$(echo .)kernel.org \
--cc=syzkaller-bugs@googlegroups$(echo .)com \
--cc=yonghong.song@linux$(echo .)dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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