linux-kernel - Re: [PATCH v5 2/3] counter: 104-quad-8: Add lock guards

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: <20200614144615.3d3dbbee@archlinux>
Date:   Sun, 14 Jun 2020 14:46:15 +0100
From:   Jonathan Cameron <jic23@...nel.org>
To:     Syed Nayyar Waris <syednwaris@...il.com>
Cc:     William Breathitt Gray <vilhelm.gray@...il.com>,
        linux-iio@...r.kernel.org,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH v5 2/3] counter: 104-quad-8: Add lock guards -
 differential encoder

On Sun, 7 Jun 2020 10:52:57 +0530
Syed Nayyar Waris <syednwaris@...il.com> wrote:

> On Wed, Mar 18, 2020 at 7:48 AM William Breathitt Gray
> <vilhelm.gray@...il.com> wrote:
> >
> > On Mon, Mar 16, 2020 at 06:20:06PM +0530, Syed Nayyar Waris wrote:  
> > > Add lock protection from race conditions to 104-quad-8 counter driver
> > > for differential encoder status code changes. Mutex lock calls used for
> > > protection.
> > >
> > > Signed-off-by: Syed Nayyar Waris <syednwaris@...il.com>
> > > ---
> > > Changes in v5:
> > >  - Change spin lock calls to mutex lock calls.
> > >  - Modify the title description.  
> >
> > Looks like the Fixes tags were dropped in these last two patches. I
> > suppose they aren't really necessary though since these features haven't
> > yet made it out of the IIO tree, so no need to backport these fixes.
> >
> > Signed-off-by: William Breathitt Gray <vilhelm.gray@...il.com>  
> 
> Adding the 'Fixes' tag:
> 
> Fixes: bbef69e088c3 ("counter: 104-quad-8: Support Differential
> Encoder Cable Status")
That doesn't seem to be the correct hash upstream though it exists in my
local tree. I'm not sure quite what happened here (and don't care enough
to try and figure it out), so I've fixed to match the upstream hash.

Applied to the fixes-togreg branch of iio.git.

Thanks,

Jonathan

> 
> Regards
> Syed Nayyar Waris