From: Dan Carpenter <error27@gmail.com>
To: Sakari Ailus <sakari.ailus@linux.intel.com>
Cc: Aleksandr Burakov <a.burakov@rosalinux.ru>,
Bingbu Cao <bingbu.cao@intel.com>,
Tianshu Qiu <tian.shu.qiu@intel.com>,
linux-media@vger.kernel.org, linux-staging@lists.linux.dev,
linux-kernel@vger.kernel.org, lvc-project@linuxtesting.org
Subject: Re: [PATCH] staging: media: ipu3: buffer overflow fix in imgu_map_node
Date: Wed, 4 Jan 2023 16:33:07 +0300 [thread overview]
Message-ID: <Y7WAExw/lQg4cd1E@kadam> (raw)
In-Reply-To: <Y7LfAR4QdIzp81yW@paasikivi.fi.intel.com>
On Mon, Jan 02, 2023 at 01:41:21PM +0000, Sakari Ailus wrote:
> > diff --git a/drivers/staging/media/ipu3/ipu3.c b/drivers/staging/media/ipu3/ipu3.c
> > index 0c453b37f8c4..cb09eb3cc227 100644
> > --- a/drivers/staging/media/ipu3/ipu3.c
> > +++ b/drivers/staging/media/ipu3/ipu3.c
> > @@ -60,8 +60,10 @@ unsigned int imgu_map_node(struct imgu_device *imgu, unsigned int css_queue)
> > for (i = 0; i < IMGU_NODE_NUM; i++)
> > if (imgu_node_map[i].css_queue == css_queue)
> > break;
> > -
> > - return i;
> > + if (i < IMGU_NODE_NUM)
> > + return i;
> > + else
> > + return (IMGU_NODE_NUM - 1);
> > }
> >
> > /**************** Dummy buffers ****************/
>
> Thanks for the patch. It would require a bug elsewhere in the driver for
> this to happen. If some handling for this case is added, it shouldn't be
> hiding the issue.
>
> One easy way could be to add WARN_ON() for this, and return some value (as
> you do). Zero would do equally well.
>
> I.e.
>
> return WARN_ON(i >= IMGU_NODE_NUM) ? 0 : i;
>
I sent basically the same response but somehow my email never went
through... I'm using mutt with gmail Oauth2 and msmtp and so my
weekly(?) login has expired then something silently eats my outgoing
emails.
In this case the emails that I sent directly before and after went
through so it seems like my login wasn't expired or everything would
have been eaten.
This Oauth2 transition has just been so frustrating. Am I the only
person having trouble with it?
regards,
dan carpenter
prev parent reply other threads:[~2023-01-04 13:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-23 12:30 [PATCH] staging: media: ipu3: buffer overflow fix in imgu_map_node Aleksandr Burakov
2023-01-02 13:41 ` Sakari Ailus
2023-01-04 13:33 ` Dan Carpenter [this message]
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=Y7WAExw/lQg4cd1E@kadam \
--to=error27@gmail.com \
--cc=a.burakov@rosalinux.ru \
--cc=bingbu.cao@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=lvc-project@linuxtesting.org \
--cc=sakari.ailus@linux.intel.com \
--cc=tian.shu.qiu@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