public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: [PATCH 1/2] stdio: Introduce stdio_valid()
Date: Wed, 27 Jan 2021 15:13:23 -0500	[thread overview]
Message-ID: <20210127201323.GP7530@bill-the-cat> (raw)
In-Reply-To: <d043a2e06434fe745d06b802610d88ffb3e7b21b.camel@suse.de>

On Mon, Jan 25, 2021 at 05:34:05PM +0100, Nicolas Saenz Julienne wrote:
> On Sat, 2021-01-23 at 19:03 -0700, Simon Glass wrote:
> > Hi Nicolas,
> > 
> > On Wed, 20 Jan 2021 at 07:05, Nicolas Saenz Julienne
> > <nsaenzjulienne@suse.de> wrote:
> > > 
> > > stdio_valid() will confirm that a struct stdio_dev pointer is indeed
> > > valid.
> > > 
> > > Signed-off-by: Nicolas Saenz Julienne <nsaenzjulienne@suse.de>
> > > ---
> > > ?common/stdio.c      | 11 +++++++++++
> > > ?include/stdio_dev.h |  1 +
> > > ?2 files changed, 12 insertions(+)
> > > 
> > > diff --git a/common/stdio.c b/common/stdio.c
> > > index abf9b1e915..69b7d2692d 100644
> > > --- a/common/stdio.c
> > > +++ b/common/stdio.c
> > > @@ -157,6 +157,17 @@ static int stdio_probe_device(const char *name, enum uclass_id id,
> > > ????????return 0;
> > > ?}
> > > 
> > > +bool stdio_valid(struct stdio_dev *dev)
> > > +{
> > > +       struct stdio_dev *sdev;
> > > +
> > > +       list_for_each_entry(sdev, &devs.list, list)
> > > +               if (sdev == dev)
> > > +                       return true;
> > > +
> > > +       return false;
> > > +}
> > > +
> > > ?struct stdio_dev *stdio_get_by_name(const char *name)
> > > ?{
> > > ????????struct list_head *pos;
> > > diff --git a/include/stdio_dev.h b/include/stdio_dev.h
> > > index 48871a6a22..f341439b03 100644
> > > --- a/include/stdio_dev.h
> > > +++ b/include/stdio_dev.h
> > > @@ -97,6 +97,7 @@ int stdio_deregister_dev(struct stdio_dev *dev, int force);
> > > ?struct list_head *stdio_get_list(void);
> > > ?struct stdio_dev *stdio_get_by_name(const char *name);
> > > ?struct stdio_dev *stdio_clone(struct stdio_dev *dev);
> > > +bool stdio_valid(struct stdio_dev *dev);
> > 
> > Please add a full function comment and explain what valid means.
> 
> As discussed with Andy, this is a workaround that doesn't address the
> underlying issue. If it's good enough for the time being I'll be happy to send
> a v2.
> 
> I'll leave a comment stating that it's something to fix.

Please do, thanks.

-- 
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20210127/c3fe2f1e/attachment.sig>

  reply	other threads:[~2021-01-27 20:13 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-20 14:04 [PATCH 0/2] Console/stdio use after free Nicolas Saenz Julienne
2021-01-20 14:04 ` [PATCH 1/2] stdio: Introduce stdio_valid() Nicolas Saenz Julienne
2021-01-24  2:03   ` Simon Glass
2021-01-25 16:34     ` Nicolas Saenz Julienne
2021-01-27 20:13       ` Tom Rini [this message]
2021-01-20 14:04 ` [PATCH 2/2] console: Don't start/stop console if stdio device invalid Nicolas Saenz Julienne
2021-01-24  2:03   ` Simon Glass
2021-01-20 14:18 ` [PATCH 0/2] Console/stdio use after free Simon Glass
2021-01-20 14:44   ` Nicolas Saenz Julienne
2021-01-20 14:59     ` Simon Glass
2021-01-20 18:59   ` Pratyush Yadav
2021-01-20 19:54     ` Simon Glass
2021-01-20 15:57 ` Andy Shevchenko
2021-01-25 16:31   ` Nicolas Saenz Julienne

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=20210127201323.GP7530@bill-the-cat \
    --to=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    /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