linux-kernel - Re: [PATCH v1 1/1] i2c: robotfuzz-osif: Propagate parent device to I2C core

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <YhIelZFe/HtjVX/8@smile.fi.intel.com>
Date:   Sun, 20 Feb 2022 12:57:25 +0200
From:   Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To:     Wolfram Sang <wsa@...nel.org>, Johan Hovold <johan@...nel.org>,
        linux-i2c@...r.kernel.org, linux-kernel@...r.kernel.org,
        syzbot+0591ccf54ee05344e4eb@...kaller.appspotmail.com
Subject: Re: [PATCH v1 1/1] i2c: robotfuzz-osif: Propagate parent device to
 I2C core

On Fri, Feb 18, 2022 at 03:22:19PM +0100, Wolfram Sang wrote:
> 
> > +	struct device *dev = &interface->dev;
> 
> This now creates a mixture of 'dev' and '&interface->dev'...
> 
> > +	priv->adapter.dev.parent = dev;
> 
> I propose to use &interface->dev here in this patch and convert to dev
> in a later patch?

Why not?
Will do for next version (next week).

-- 
With Best Regards,
Andy Shevchenko