linux-kernel - Re: [RFC PATCH v1] iio: trigger: move trig->owner init to trigger allocate() stage

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: <20220718112446.lucl7omialqri7yv@CAB-WSD-L081021.sigma.sbrf.ru>
Date:   Mon, 18 Jul 2022 11:23:59 +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>
Subject: Re: [RFC PATCH v1] iio: trigger: move trig->owner init to trigger
 allocate() stage

Hello Jonathan,

On Sat, Jul 16, 2022 at 04:25:56PM +0100, Jonathan Cameron wrote:
> On Wed, 13 Jul 2022 17:04:36 +0100
> Jonathan Cameron <jic23@...nel.org> wrote:
> 
> > On Fri, 1 Jul 2022 11:59:59 +0000
> > Dmitry Rokosov <DDRokosov@...rdevices.ru> wrote:
> > 
> > > Hello Jonathan,
> > > 
> > > This patch has been on the mailing list for one month already, but no
> > > comments from other IIO reviewers. What do you think we should do with it?
> > > Is it a helpful change or not?  
> > 
> > Given I'm way behind and timing in cycle, I'm probably going to kick this
> > back to start of the next cycle. Sorry for delay,
> Applied to the togreg branch of iio.git.
> 
> I'm unlikely to do another pull request this cycle unless there is a delay in
> the release for some reason (and probably not even if there is), so this
> is queued up for next cycle.  As such it'll sit exposed only in the testing
> branch until I rebase on rc1.
> 
> Thanks,
> 
> Jonathan
> 

Thank you for the patch applied.
I have one question about the previous already applied patchset

https://lore.kernel.org/all/20220607183907.20017-1-ddrokosov@sberdevices.ru/

I see this patchset already merged to linux-next more than a month ago.
But it's still not available in the linux stable branch. Could you please
explain what's the problem with this one? Was some bug found during
linux-next testing stage? Should I fix something?

Appreciate any help to understand what's I missing.

-- 
Thank you,
Dmitry