linux-kernel - Re: [PATCH v3] iio: trigger: warn about non-registered iio trigger getting attempt

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20220622175206.ddyyex7bezzh4rd4@CAB-WSD-L081021.sigma.sbrf.ru>
Date:   Wed, 22 Jun 2022 17:51:56 +0000
From:   Dmitry Rokosov <DDRokosov@...rdevices.ru>
To:     Jonathan Cameron <jic23@...nel.org>
CC:     "robh+dt@...nel.org" <robh+dt@...nel.org>,
        "lars@...afoo.de" <lars@...afoo.de>,
        "andy.shevchenko@...il.com" <andy.shevchenko@...il.com>,
        "noname.nuno@...il.com" <noname.nuno@...il.com>,
        "linux-iio@...r.kernel.org" <linux-iio@...r.kernel.org>,
        kernel <kernel@...rdevices.ru>,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "rockosov@...il.com" <rockosov@...il.com>
Subject: Re: [PATCH v3] iio: trigger: warn about non-registered iio trigger
 getting attempt

Jonathan,

On Sat, Jun 18, 2022 at 02:27:03PM +0100, Jonathan Cameron wrote:
> On Thu, 16 Jun 2022 09:13:00 +0000
> Dmitry Rokosov <DDRokosov@...rdevices.ru> wrote:
> 
> > Hello Jonathan,
> > 
> > I notice the patchset from 
> > https://lore.kernel.org/all/20220524181150.9240-1-ddrokosov@sberdevices.ru/
> > is not merged to stable yet.
> > I think if this WARN() patch is okay for you, maybe it's better to merge
> > it together with the previous one. It will notify developers about this
> > problem as you suggested before, and the previous patchset resolves the issue
> > in the all IIO drivers.
> > 
> > What do you think about it?
> 
> It would be a stretch to take a defensive measure like this into stable,
> so I'll just queue this up for the next merge window.  We might have
> some exciting intermediate times where anyone actually using the togreg
> branch directly will get drivers that will spit out the warning.
> That should only be people active on the list though who will find
> this quickly enough and understand what is gong on.
> 
> I'm fine with this and it's been on list long enough for anyone else to comment.
> It'll be in a branch I'm happy to rebase for at few days anyway if there
> are any last minute comments or tags.
> 
> Applied to the togreg branch of iio.git and pushed out as testing.
> 
> Hopefully I'll get a pull request out for the fixes-togreg branch
> sometime this weekend.

Thanks a lot for such detailed clarification! I'm seeing this warn
patchset in the linux-next already.

-- 
Thank you,
Dmitry