[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y4N9IAlQVsdyIJ9Q@lunn.ch>
Date: Sun, 27 Nov 2022 16:07:12 +0100
From: Andrew Lunn <andrew@...n.ch>
To: Vincent MAILHOL <mailhol.vincent@...adoo.fr>
Cc: linux-can@...r.kernel.org, Marc Kleine-Budde <mkl@...gutronix.de>,
linux-kernel@...r.kernel.org,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
netdev@...r.kernel.org, linux-usb@...r.kernel.org,
Saeed Mahameed <saeed@...nel.org>,
Jiri Pirko <jiri@...dia.com>,
Lukas Magel <lukas.magel@...teo.net>
Subject: Re: [PATCH v4 3/6] can: etas_es58x: export product information
through devlink_ops::info_get()
> I checked, none of gcc and clang would trigger a warning even for a
> 'make W=12'. More generally speaking, I made sure that my driver is
> free of any W=12.
That is good enough for me.
> I do not care any more as long as it does not result in
> undefined behaviour.
Agreed. Hopefully sscanf cannot go completely wrong and go off the end
of the buffer. That i would care about. Bit i guess the USB fuzzers
would of hit such problems already.
Andrew
Powered by blists - more mailing lists