[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230209150733.GA17303@breakpoint.cc>
Date: Thu, 9 Feb 2023 16:07:33 +0100
From: Florian Westphal <fw@...len.de>
To: Igor Artemiev <Igor.A.Artemiev@...t.ru>
Cc: Pablo Neira Ayuso <pablo@...filter.org>,
Jozsef Kadlecsik <kadlec@...filter.org>,
Florian Westphal <fw@...len.de>,
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
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.
Powered by blists - more mailing lists