[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240708113300.3544d36d@kernel.org>
Date: Mon, 8 Jul 2024 11:33:00 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Kory Maincent <kory.maincent@...tlin.com>
Cc: "David S. Miller" <davem@...emloft.net>, Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>, Donald Hunter
<donald.hunter@...il.com>, Oleksij Rempel <o.rempel@...gutronix.de>,
Jonathan Corbet <corbet@....net>, Thomas Petazzoni
<thomas.petazzoni@...tlin.com>, linux-kernel@...r.kernel.org,
netdev@...r.kernel.org, Dent Project <dentproject@...uxfoundation.org>,
kernel@...gutronix.de, linux-doc@...r.kernel.org
Subject: Re: [PATCH net-next v6 5/7] net: ethtool: Add new power limit get
and set features
On Mon, 8 Jul 2024 11:38:46 +0200 Kory Maincent wrote:
> > This smells of null-deref if user only passes one of the attributes.
> > But the fix should probably be in ethnl_set_pse_validate() so it won't
> > conflict (I'm speculating that it will need to go to net).
>
> Mmh, indeed if the netlink PSE type attribute is different with the supported
> PSE type we might have an issue here.
>
> I am wondering, if I fix it in net won't it conflict with net-next now that
> this series is merged?
Don't worry I understand the code well enough to resolve any conflicts
(famous last words?). And if we fix as part of ethnl_set_pse_validate()
then there's no conflict, AFAICT.
Powered by blists - more mailing lists