linux-kernel - Re: [PATCH STABLE v4.19.15] gpiolib: fix line event timestamps for nested irqs

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: <CAMpxmJWAT2-Fr-fxBW+DcmrrUyNyJ8rtpSvLhD74GP1DcE30rQ@mail.gmail.com>
Date:   Wed, 16 Jan 2019 17:18:14 +0100
From:   Bartosz Golaszewski <bgolaszewski@...libre.com>
To:     Greg KH <greg@...ah.com>
Cc:     Bartosz Golaszewski <brgl@...ev.pl>,
        Sasha Levin <sashal@...nel.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        linux-gpio <linux-gpio@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>,
        "Stable # 4 . 20+" <stable@...r.kernel.org>
Subject: Re: [PATCH STABLE v4.19.15] gpiolib: fix line event timestamps for
 nested irqs

śr., 16 sty 2019 o 17:02 Greg KH <greg@...ah.com> napisał(a):
>
> On Wed, Jan 16, 2019 at 04:35:57PM +0100, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski <bgolaszewski@...libre.com>
> >
> > Nested interrupts run inside the calling thread's context and the top
> > half handler is never called which means that we never read the
> > timestamp.
> >
> > This issue came up when trying to read line events from a gpiochip
> > using regmap_irq_chip for interrupts.
> >
> > Fix it by reading the timestamp from the irq thread function if it's
> > still 0 by the time the second handler is called.
> >
> > Fixes: d58f2bf261fd ("gpio: Timestamp events in hardirq handler")
> > Cc: stable@...r.kernel.org
> > Signed-off-by: Bartosz Golaszewski <bgolaszewski@...libre.com>
> > ---
> > Hi Sasha,
> >
> > this is a backport for v4.19.y series. The original patch didn't apply
> > due to a conflict.
>
> What is the git commit id for this patch in Linus's tree?
>

I'm not sure if you mean Linus Torvalds or Linus Walleij (through whom
my GPIO patches go) but neither has picked this one up yet. I'm not
sure why it got processed for stable already, I thought it must go
into Linus Torvalds' master branch first.

Anyway, in my GPIO branch its commit id is
8d694dcdbbdcfe4f27a52bcc6f2ce733ba5ec53c and it should get merged into
Linus Walleij's tree soon. I have already sent a PR.

Best regards,
Bartosz Golaszewski