All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+cfbe1da5fdfc39efc293@syzkaller.appspotmail.com>
To: kadlec@netfilter.org, linux-kernel@vger.kernel.org,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfilter?] net-next test error: WARNING: suspicious RCU usage in _destroy_all_sets
Date: Tue, 18 Jun 2024 05:38:02 -0700	[thread overview]
Message-ID: <0000000000004b8b81061b295a04@google.com> (raw)
In-Reply-To: <b82ee1f4-0a09-7976-0b5b-c762f5eb4186@netfilter.org>

Hello,

syzbot has tested the proposed patch and the reproducer did not trigger any issue:

Reported-and-tested-by: syzbot+cfbe1da5fdfc39efc293@syzkaller.appspotmail.com

Tested on:

commit:         0eb94209 netfilter: ipset: Fix suspicious rcu_derefere..
git tree:       git://blackhole.szhk.kfki.hu/nf main
kernel config:  https://syzkaller.appspot.com/x/.config?x=33d942c3f3616a8f
dashboard link: https://syzkaller.appspot.com/bug?extid=cfbe1da5fdfc39efc293
compiler:       Debian clang version 15.0.6, GNU ld (GNU Binutils for Debian) 2.40

Note: no patches were applied.
Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2024-06-18 12:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <b82ee1f4-0a09-7976-0b5b-c762f5eb4186@netfilter.org>
2024-06-18 12:38 ` syzbot [this message]
     [not found] <3cdc2784-6c02-e251-579a-24df9036424e@netfilter.org>
2024-06-14 10:18 ` [syzbot] [netfilter?] net-next test error: WARNING: suspicious RCU usage in _destroy_all_sets syzbot
     [not found] <3edac706-efb7-946a-ec72-02445ffb8ea4@netfilter.org>
2024-06-14 10:03 ` syzbot
2024-06-14  8:20 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=0000000000004b8b81061b295a04@google.com \
    --to=syzbot+cfbe1da5fdfc39efc293@syzkaller.appspotmail.com \
    --cc=kadlec@netfilter.org \
    --cc=linux-kernel@vger.kernel.org \
    --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.