netdev - Re: [PATCH 1/2] net: dsa: ksz9477: add I2C managed mode support

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CAMhs-H8zB9vkPxhVwjGDTqazYoUMc1UKzN4=p54kB2YyEBjZRA@mail.gmail.com>
Date:   Mon, 17 Dec 2018 21:46:15 +0100
From:   Sergio Paracuellos <sergio.paracuellos@...il.com>
To:     Dan Carpenter <dan.carpenter@...cle.com>
Cc:     Woojung.Huh@...rochip.com, Andrew Lunn <andrew@...n.ch>,
        Florian Fainelli <f.fainelli@...il.com>,
        vivien.didelot@...oirfairelinux.com, netdev@...r.kernel.org,
        driverdev-devel@...uxdriverproject.org,
        UNGLinuxDriver@...rochip.com,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>, davem@...emloft.net
Subject: Re: [PATCH 1/2] net: dsa: ksz9477: add I2C managed mode support

On Mon, Dec 17, 2018 at 8:11 PM Dan Carpenter <dan.carpenter@...cle.com> wrote:
>
> On Mon, Dec 17, 2018 at 07:22:51PM +0100, Sergio Paracuellos wrote:
> > > > +static int ksz_i2c_write(struct ksz_device *dev, u32 reg, u8 *val,
> > > > +                      unsigned int len)
> > > > +{
> > > > +     struct i2c_client *client = dev->priv;
> > > > +     unsigned int cnt = len;
> > > > +     int i = 0;
> > > > +     u8 txb[4];
> > > > +
> > > > +     do {
> > > > +             txb[i++] = (u8)(*val >> (8 * (cnt - 1)));
> > >                                               ^^^^^^^
> > >
> > > Can "cnt" be zero from ksz_i2c_set()?  If so this loop will corrupt
> > > memory.
> >
> > This get and set interface seems to be introduced recently but it is
> > not being used yet, so
> > in this moment the answer is not. For me, there is no sense in call
> > 'set' with no len. Should
> > I add a check for zero len and return EINVAL just in case?
> >
>
> Yes, please.

Done. v3 with this change already sent.

>
> > > > +static int ksz_i2c_probe(struct i2c_client *client,
> > > > +                      const struct i2c_device_id *id)
> > > > +{
> > > > +     struct ksz_device *dev;
> > > > +     int ret;
> > > > +
> > > > +     dev = ksz_switch_alloc(&client->dev, &ksz_i2c_ops, client);
> > > > +     if (!dev)
> > > > +             return -ENOMEM;
> > > > +
> > > > +     if (client->dev.platform_data)
> > > > +             dev->pdata = client->dev.platform_data;
> > > > +
> > > > +     i2c_set_clientdata(client, dev);
> > > > +
> > > > +     ret = ksz9477_switch_register(dev);
> > > > +     if (ret) {
> > > > +             dev_err(&client->dev, "registering switch (ret: %d)\n", ret);
> > >
> > >
> > > free dev on this error path?
> >
> > Internally all of this are using devm_* funcions, so I think is there
> > is no need to free anything. Also, the
> > spi managed driver for this does nothing also about this.
>
> You're right.  My bad.  I should have looked at this.
>
> regards,
> dan carpenter
>

Best regards,
    Sergio Paracuellos