From: Simon Horman <horms@kernel.org>
To: Christophe JAILLET <christophe.jaillet@wanadoo.fr>
Cc: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Lennart Franzen <lennart@lfdomain.com>,
Alexandru Tachici <alexandru.tachici@analog.com>,
linux-kernel@vger.kernel.org, kernel-janitors@vger.kernel.org,
netdev@vger.kernel.org
Subject: Re: [PATCH net] net: ethernet: adi: adin1110: Fix some error handling path in adin1110_read_fifo()
Date: Mon, 7 Oct 2024 16:45:05 +0100 [thread overview]
Message-ID: <20241007154505.GG32733@kernel.org> (raw)
In-Reply-To: <2669052d-752f-416a-9d5e-a03848f30904@wanadoo.fr>
On Fri, Oct 04, 2024 at 03:15:39PM +0200, Christophe JAILLET wrote:
> Le 04/10/2024 à 13:37, Simon Horman a écrit :
> > On Thu, Oct 03, 2024 at 08:53:15PM +0200, Christophe JAILLET wrote:
> > > If 'frame_size' is too small or if 'round_len' is an error code, it is
> > > likely that an error code should be returned to the caller.
> > >
> > > Actually, 'ret' is likely to be 0, so if one of these sanity checks fails,
> > > 'success' is returned.
> >
> > Hi Christophe,
> >
> > I think we can say "'ret' will be 0".
>
> Agreed.
>
> ret = adin1110_read_reg()
> --> spi_sync_transfer()
> --> spi_sync()
>
> which explicitly documents "zero on success, else a negative error code."
>
> > At least that is what my brief investigation tells me.
> >
> > >
> > > Return -EINVAL instead.
> >
>
> If the patch is considered as correct, can you confirm that -EINVAL is the
> correct error code to use? If not, which one would be preferred?
-EINVAL seems reasonable to me.
> > Please include some information on how this was found and tested.
> > e.g.
> >
> > Found by inspection / Found using widget-ng.
>
> I would say: found by luck! :)
>
> The explanation below will be of no help in the commit message and won't be
> added. I just give you all the gory details because you asked for it ;-)
>
> (and after reading bellow, you can call me crazy!)
:)
next prev parent reply other threads:[~2024-10-07 15:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-03 18:53 [PATCH net] net: ethernet: adi: adin1110: Fix some error handling path in adin1110_read_fifo() Christophe JAILLET
2024-10-04 11:37 ` Simon Horman
2024-10-04 13:15 ` Christophe JAILLET
2024-10-07 15:45 ` Simon Horman [this message]
2024-10-04 11:47 ` Dan Carpenter
2024-10-04 13:27 ` Christophe JAILLET
2024-10-04 18:09 ` Jakub Kicinski
2024-10-07 15:46 ` Simon Horman
2024-10-07 17:35 ` Julia Lawall
2024-10-08 0:10 ` patchwork-bot+netdevbpf
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20241007154505.GG32733@kernel.org \
--to=horms@kernel.org \
--cc=alexandru.tachici@analog.com \
--cc=christophe.jaillet@wanadoo.fr \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=kuba@kernel.org \
--cc=lennart@lfdomain.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).