linux-kernel - Re: [PATCH v3] iio: core: Prevent invalid memory access when there is no parent

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: <20230722175332.3ac83cc8@jic23-huawei>
Date:   Sat, 22 Jul 2023 17:53:32 +0100
From:   Jonathan Cameron <jic23@...nel.org>
To:     Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
Cc:     Milan Zamazal <mzamazal@...hat.com>, linux-iio@...r.kernel.org,
        linux-kernel@...r.kernel.org, Lars-Peter Clausen <lars@...afoo.de>,
        Nuno Sá <noname.nuno@...il.com>
Subject: Re: [PATCH v3] iio: core: Prevent invalid memory access when there
 is no parent

On Wed, 19 Jul 2023 18:27:45 +0300
Andy Shevchenko <andriy.shevchenko@...ux.intel.com> wrote:

> On Wed, Jul 19, 2023 at 10:32:08AM +0200, Milan Zamazal wrote:
> 
> > Changes in v3:
> >  - The call trace in the commit message reduced to the minimum lines
> >    needed to explain the problem.  
> 
> Precisely, that deserves my tag which I already had given :-)
> Thank you!
> 
Applied to the fixes-togreg branch of iio.git.

In theory every device should have a parent, but this fix is more
minimal than adding one for the dummy device (which we should still do
- even if it's a virtual device of some type that we create just for this
purpose).

That reminds me, I was in process of fixing this for perf drivers and
forgot to finish it off :)

Jonathan