All of lore.kernel.org
 help / color / mirror / Atom feed
From: syzbot <syzbot+521f7e7e2b974abde99a@syzkaller.appspotmail.com>
To: linux-kernel@vger.kernel.org, mike.michalo@gmail.com,
	 syzkaller-bugs@googlegroups.com
Subject: Re: [syzbot] [netfilter?] WARNING in nf_flow_table_extend_ct_timeout
Date: Fri, 23 Oct 2026 05:57:02 -0700	[thread overview]
Message-ID: <6adb599e.3f6e6ada.1e998b.0027.GAE@google.com> (raw)
In-Reply-To: <CAO+rqLjx9RqNs4kjyeko4zYqWyH0VZhNtT4jFKmkjESv3v178Q@mail.gmail.com>

Hello,

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

Reported-by: syzbot+521f7e7e2b974abde99a@syzkaller.appspotmail.com
Tested-by: syzbot+521f7e7e2b974abde99a@syzkaller.appspotmail.com

Tested on:

commit:         734bef54 Merge tag 'net-next-7.4' of git://git.kernel...
git tree:       https://kernel.googlesource.com/pub/scm/linux/kernel/git/netdev/net main
console output: https://syzkaller.appspot.com/x/log.txt?x=15c66d21580000
kernel config:  https://syzkaller.appspot.com/x/.config?x=68bf488210f470aa
dashboard link: https://syzkaller.appspot.com/bug?extid=521f7e7e2b974abde99a
compiler:       Debian clang version 22.1.8 (1~deb13u4), Debian LLD 22.1.8
patch:          https://syzkaller.appspot.com/x/patch.diff?x=11b2b93e580000

Note: testing is done by a robot and is best-effort only.

       reply	other threads:[~2026-10-23 12:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAO+rqLjx9RqNs4kjyeko4zYqWyH0VZhNtT4jFKmkjESv3v178Q@mail.gmail.com>
2026-10-23 12:57 ` syzbot [this message]
     [not found] <CAO+rqLihzHZx5kUUdR7mcC=yApCUP_20OEh7KZOQhHY5_+KLYQ@mail.gmail.com>
2026-10-22 17:26 ` [syzbot] [netfilter?] WARNING in nf_flow_table_extend_ct_timeout syzbot
2026-09-15 22:34 syzbot
2026-10-22 16:44 ` syzbot
2026-10-22 17:02   ` mixalhs
2026-10-22 17: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=6adb599e.3f6e6ada.1e998b.0027.GAE@google.com \
    --to=syzbot+521f7e7e2b974abde99a@syzkaller.appspotmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mike.michalo@gmail.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.