public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6.6 000/326] 6.6.16-rc2 review
Date: Wed, 7 Feb 2024 10:09:34 +0000	[thread overview]
Message-ID: <2024020758-judo-stardom-80f5@gregkh> (raw)
In-Reply-To: <e4305f3d-ede8-44fc-8bd4-eae899284f56@leemhuis.info>

On Wed, Feb 07, 2024 at 08:04:49AM +0100, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 04.02.24 05:43, Стас Ничипорович wrote:
> > After trying again to create the ipset with timeout option I get a kernel panic
> > # ipset create throttled-ips hash:ip family inet hashsize 1024 maxelem
> > 100000 timeout 600 bucketsize 12 initval 0x22b96e3a
> > ipset v7.20: Set cannot be created: set with the same name already exists
> 
> To be sure the issue doesn't fall through the cracks unnoticed, I'm
> adding it to regzbot, the Linux kernel regression tracking bot:
> 
> #regzbot ^introduced fdb8e12cc2cc
> #regzbot title netfilter: WARNING when using ipset with timeout option
> #regzbot fix: netfilter: ipset: Missing gc cancellations fixed
> #regzbot ignore-activity

Note, this did not get applied to the stable kernels, so it's an issue
in Linus's tree only, with a proposed fix already posted (and might be
in linux-next already, haven't checked...)

thanks,

greg k-h

  reply	other threads:[~2024-02-07 10:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-04  4:43 [PATCH 6.6 000/326] 6.6.16-rc2 review Стас Ничипорович
2024-02-04 12:49 ` Greg KH
2024-02-04 13:15   ` Стас Ничипорович
2024-02-04 14:13     ` Greg KH
2024-02-04 22:08       ` Стас Ничипорович
2024-02-05  1:25         ` Greg KH
2024-02-05  1:26           ` Greg KH
2024-02-07  7:04 ` Linux regression tracking (Thorsten Leemhuis)
2024-02-07 10:09   ` Greg KH [this message]
2024-02-07 10:22     ` Linux regression tracking (Thorsten Leemhuis)
  -- strict thread matches above, loose matches on Subject: below --
2024-02-03 17:52 Greg Kroah-Hartman
2024-02-03 19:51 ` SeongJae Park
2024-02-03 21:57 ` Florian Fainelli
2024-02-03 22:58 ` Takeshi Ogasawara
2024-02-04  6:51 ` Bagas Sanjaya
2024-02-04 17:04 ` Naresh Kamboju
2024-02-04 19:13 ` Justin Forbes
2024-02-04 21:27 ` Ron Economos
2024-02-05  9:46 ` Shreeya Patel
2024-02-05 13:18 ` Jon Hunter
2024-02-05 16:40 ` Allen

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=2024020758-judo-stardom-80f5@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=regressions@lists.linux.dev \
    /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