[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <beff971d-caee-449a-868e-aa9214137ddc@lunn.ch>
Date: Wed, 22 Jan 2025 21:15:50 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Thomas Weißschuh <linux@...ssschuh.net>
Cc: Richard Cochran <richardcochran@...il.com>,
Andrew Lunn <andrew+netdev@...n.ch>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Jakub Kicinski <kuba@...nel.org>, Paolo Abeni <pabeni@...hat.com>,
John Stultz <john.stultz@...aro.org>, Arnd Bergmann <arnd@...db.de>,
netdev@...r.kernel.org, linux-kernel@...r.kernel.org,
stable@...r.kernel.org
Subject: Re: [PATCH net] ptp: Ensure info->enable callback is always set
On Wed, Jan 22, 2025 at 07:39:31PM +0100, Thomas Weißschuh wrote:
> The ioctl and sysfs handlers unconditionally call the ->enable callback.
> Not all drivers implement that callback, leading to NULL dereferences.
> Example of affected drivers: ptp_s390.c, ptp_vclock.c and ptp_mock.c.
> + if (!ptp->info->enable)
> + ptp->info->enable = ptp_enable;
Is it possible that a driver has defined info as a const, and placed
it into read only memory? It is generally good practice to make
structures of ops read only to prevent some forms of attack.
Andrew
Powered by blists - more mailing lists