[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20230125005333.dmphl4vuwnh66moa@skbuf>
Date: Wed, 25 Jan 2023 02:53:33 +0200
From: Vladimir Oltean <vladimir.oltean@....com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>,
Michal Kubecek <mkubecek@...e.cz>
Subject: Re: [PATCH net-next] net: ethtool: fix NULL pointer dereference in
stats_prepare_data()
On Tue, Jan 24, 2023 at 04:52:23PM -0800, Jakub Kicinski wrote:
> On Wed, 25 Jan 2023 02:45:17 +0200 Vladimir Oltean wrote:
> > > Choose one:
> > > - you disagree with my comment on the report
> > > - you don't think that we should mix the immediate fix with the
> > > structural change
> > > - you agree but "don't have the time" to fix this properly
> >
> > Yeah, sorry, I shouldn't have left your question unanswered ("should we make
> > a fake struct genl_info * to pass here?") - but I don't think I'm qualified
> > enough to have an opinion, either. Whereas the immediate fix is neutral
> > enough to not be controversial, or so I thought.
> >
> > The problem is not so much "the time to fix this properly", but rather,
> > I'm not even sure how to trigger the ethtool dumpit() code...
>
> Ack, makes sense. I just wanted to make sure you weren't disagreeing.
Since we're talking about it, do you know how to exercise that code?
Powered by blists - more mailing lists