[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6152n4q7-1ssr-521p-786s-71q4q9731370@vanv.qr>
Date: Thu, 9 Feb 2023 17:09:58 +0100 (CET)
From: Jan Engelhardt <jengelh@...i.de>
To: Florian Westphal <fw@...len.de>
cc: Igor Artemiev <Igor.A.Artemiev@...t.ru>,
Pablo Neira Ayuso <pablo@...filter.org>,
Jozsef Kadlecsik <kadlec@...filter.org>,
netfilter-devel@...r.kernel.org, coreteam@...filter.org,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
lvc-project@...uxtesting.org
Subject: Re: [lvc-project] [PATCH] netfilter: xt_recent: Fix attempt to update
removed entry
On Thursday 2023-02-09 16:07, Florian Westphal wrote:
>Igor Artemiev <Igor.A.Artemiev@...t.ru> wrote:
>> When both --remove and --update flag are specified, there's a code
>> path at which the entry to be updated is removed beforehand,
>> that leads to kernel crash. Update entry, if --remove flag
>> don't specified.
>>
>> Found by Linux Verification Center (linuxtesting.org) with SVACE.
>
>How did you manage to do this? --update and --remove are supposed
>to be mutually exclusive.
I suppose the exclusivity is only checked at the iptables command-line
and neverwhere else.
Powered by blists - more mailing lists