Received-SPF: pass (google.com: domain of linux-kernel+bounces-56308-linux.lists.archive=gmail.com@vger.kernel.org designates 2604:1380:45e3:2400::1 as permitted sender) client-ip=2604:1380:45e3:2400::1;
Message-ID: <1f46035e-d21d-4033-a43a-3fbb2ae89f7f@leemhuis.info>
Date: Wed, 7 Feb 2024 11:22:58 +0100
Precedence: bulk
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Subject: Re: [PATCH 6.6 000/326] 6.6.16-rc2 review
Content-Language: en-US, de-DE
To: Greg KH <gregkh@linuxfoundation.org>,
 Linux regressions mailing list <regressions@lists.linux.dev>
Cc: linux-kernel@vger.kernel.org
References: <CAH37n11s_8qjBaDrao3PKct4FriCWNXHWBBHe-ddMYHSw4wK0Q@mail.gmail.com>
 <e4305f3d-ede8-44fc-8bd4-eae899284f56@leemhuis.info>
 <2024020758-judo-stardom-80f5@gregkh>
From: "Linux regression tracking (Thorsten Leemhuis)"
 <regressions@leemhuis.info>
Reply-To: Linux regressions mailing list <regressions@lists.linux.dev>
In-Reply-To: <2024020758-judo-stardom-80f5@gregkh>
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit

On 07.02.24 11:09, Greg KH wrote:
> 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...)

Thx, but don't worry, I know. It's just that the patch didn't make any
progress in the last few days, that's why I decided to now add it to the
tracking.

As I just noticed I apparently did so with the wrong commit-id, which I
just picked from the proposed fix without verifying. :-/ Will fix this
up for regzbot and tell Jozsef.

#regzbot 97f7cf1cd80eee
#regzbot monitor
https://lore.kernel.org/all/20240204152642.1394588-1-kadlec@netfilter.org/

Thx again. Ciao, Thorsten