From: Sudeep Holla <sudeep.holla@arm.com>
To: Cristian Marussi <cristian.marussi@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
kernel test robot <lkp@intel.com>,
Sudeep Holla <sudeep.holla@arm.com>,
Dan Carpenter <dan.carpenter@oracle.com>
Subject: Re: [PATCH] firmware: arm_scmi: Fix possible scmi_linux_errmap buffer overflow
Date: Wed, 7 Jul 2021 18:54:13 +0100 [thread overview]
Message-ID: <20210707175400.xq6maswfi2dpbau3@bogus> (raw)
In-Reply-To: <20210707140625.GI17807@e120937-lin>
On Wed, Jul 07, 2021 at 03:06:25PM +0100, Cristian Marussi wrote:
> On Wed, Jul 07, 2021 at 02:50:28PM +0100, Sudeep Holla wrote:
> > The scmi_linux_errmap buffer access index is supposed to depend on the
> > array size to prevent element out of bounds access. It uses SCMI_ERR_MAX
> > to check bounds but that can mismatch with the array size. It also
> > changes the success into -EIO though scmi_linux_errmap is never used in
> > case of success, it is expected to work for success case too.
> >
> > It is slightly confusing code as the negative of the error code
> > is used as index to the buffer. Fix it by negating it at the start and
> > make it more readable.
> >
> > Reported-by: kernel test robot <lkp@intel.com>
> > Reported-by: Dan Carpenter <dan.carpenter@oracle.com>
> > Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> > ---
> > drivers/firmware/arm_scmi/driver.c | 6 ++++--
> > 1 file changed, 4 insertions(+), 2 deletions(-)
> >
> > (Based on https://lore.kernel.org/r/20210707134739.1869481-1-sudeep.holla@arm.com)
> >
> > diff --git a/drivers/firmware/arm_scmi/driver.c b/drivers/firmware/arm_scmi/driver.c
> > index 66e5e694be7d..2a5c1b3658c4 100644
> > --- a/drivers/firmware/arm_scmi/driver.c
> > +++ b/drivers/firmware/arm_scmi/driver.c
> > @@ -166,8 +166,10 @@ static const int scmi_linux_errmap[] = {
> >
> > static inline int scmi_to_linux_errno(int errno)
> > {
> > - if (errno < SCMI_SUCCESS && errno > SCMI_ERR_MAX)
> > - return scmi_linux_errmap[-errno];
> > + int err_idx = -errno;
> > +
> > + if (err_idx >= SCMI_SUCCESS && err_idx < ARRAY_SIZE(scmi_linux_errmap))
> > + return scmi_linux_errmap[err_idx];
> > return -EIO;
> > }
> >
> Hi,
>
> Looks good to me; now SCMI_ERR_MAX is not referenced anymore by anyone
> but I suppose is good practice to still keep it as an end-marker for
> scmi_error_codes enum.
>
Good point, I will drop it as there are no users. It can be added later
if needed.
> Reviewed-by: Cristian Marussi <cristian.marussi@arm.com>
>
Thanks !
--
Regards,
Sudeep
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2021-07-07 17:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-07 13:50 [PATCH] firmware: arm_scmi: Fix possible scmi_linux_errmap buffer overflow Sudeep Holla
2021-07-07 14:06 ` Cristian Marussi
2021-07-07 17:54 ` Sudeep Holla [this message]
2021-07-14 16:36 ` Sudeep Holla
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=20210707175400.xq6maswfi2dpbau3@bogus \
--to=sudeep.holla@arm.com \
--cc=cristian.marussi@arm.com \
--cc=dan.carpenter@oracle.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=lkp@intel.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