[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <AM4PR0501MB276924D7AD83B349AA2A6A0BC5E30@AM4PR0501MB2769.eurprd05.prod.outlook.com>
Date: Tue, 25 Jun 2019 09:04:55 +0000
From: Ran Rozenstein <ranro@...lanox.com>
To: Tariq Toukan <tariqt@...lanox.com>,
Florian Westphal <fw@...len.de>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>
CC: Maor Gottlieb <maorg@...lanox.com>,
"edumazet@...gle.com" <edumazet@...gle.com>
Subject: RE: [PATCH net-next 0/2] net: ipv4: remove erroneous advancement of
list pointer
> -----Original Message-----
> From: Tariq Toukan
> Sent: Monday, June 17, 2019 19:16
> To: Florian Westphal <fw@...len.de>; netdev@...r.kernel.org
> Cc: Ran Rozenstein <ranro@...lanox.com>; Maor Gottlieb
> <maorg@...lanox.com>; edumazet@...gle.com
> Subject: Re: [PATCH net-next 0/2] net: ipv4: remove erroneous
> advancement of list pointer
>
>
>
> On 6/17/2019 5:02 PM, Florian Westphal wrote:
> > Tariq reported a soft lockup on net-next that Mellanox was able to
> > bisect to 2638eb8b50cf ("net: ipv4: provide __rcu annotation for ifa_list").
> >
> > While reviewing above patch I found a regression when addresses have a
> > lifetime specified.
> >
> > Second patch extends rtnetlink.sh to trigger crash (without first
> > patch applied).
> >
>
> Thanks Florian.
>
> Ran, can you please test?
Tested, still reproduce.
Powered by blists - more mailing lists