lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 11 Aug 2021 14:47:24 +0300 From: Vladimir Oltean <olteanv@...il.com> To: Wong Vee Khee <vee.khee.wong@...ux.intel.com> Cc: Jose Abreu <Jose.Abreu@...opsys.com>, Andrew Lunn <andrew@...n.ch>, Heiner Kallweit <hkallweit1@...il.com>, Russell King <linux@...linux.org.uk>, "David S . Miller" <davem@...emloft.net>, Jakub Kicinski <kuba@...nel.org>, netdev@...r.kernel.org, linux-kernel@...r.kernel.org, Vladimir Oltean <vladimir.oltean@....com> Subject: Re: [PATCH net-next 1/1] net: pcs: xpcs: fix error handling on failed to allocate memory On Tue, Aug 10, 2021 at 04:58:12PM +0800, Wong Vee Khee wrote: > Drivers such as sja1105 and stmmac that call xpcs_create() expects an > error returned by the pcs-xpcs module, but this was not the case on > failed to allocate memory. > > Fixed this by returning an -ENOMEM instead of a NULL pointer. > > Cc: Vladimir Oltean <vladimir.oltean@....com> > Signed-off-by: Wong Vee Khee <vee.khee.wong@...ux.intel.com> > --- > drivers/net/pcs/pcs-xpcs.c | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/drivers/net/pcs/pcs-xpcs.c b/drivers/net/pcs/pcs-xpcs.c > index 63fda3fc40aa..4bd61339823c 100644 > --- a/drivers/net/pcs/pcs-xpcs.c > +++ b/drivers/net/pcs/pcs-xpcs.c > @@ -1089,7 +1089,7 @@ struct dw_xpcs *xpcs_create(struct mdio_device *mdiodev, > > xpcs = kzalloc(sizeof(*xpcs), GFP_KERNEL); > if (!xpcs) > - return NULL; > + return ERR_PTR(-ENOMEM); > > xpcs->mdiodev = mdiodev; > > -- > 2.25.1 > I know I changed my mind, but seeing that Intel's Alder Lake S patches are likely going to stall for a while due to ungoing design discussions: https://patchwork.kernel.org/project/netdevbpf/patch/20210809102229.933748-2-vee.khee.wong@linux.intel.com/ the net -> net-next merge might not be so far in the future after all. So could this patch be applied to the "net" tree after all? According to the cadence of the last 2 net -> net-next merges, which were on Jul 31 and Aug 5, the next one should be soon-ish. The patch is fine: Reviewed-by: Vladimir Oltean <vladimir.oltean@....com> Fixes: 3ad1d171548e ("net: dsa: sja1105: migrate to xpcs for SGMII")
Powered by blists - more mailing lists