[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20191208175602.GA1844@latitude>
Date: Sun, 8 Dec 2019 18:56:02 +0100
From: Johannes Hirte <johannes.hirte@...enkhaos.de>
To: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: David Howells <dhowells@...hat.com>,
Rasmus Villemoes <linux@...musvillemoes.dk>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Peter Zijlstra <peterz@...radead.org>,
Nicolas Dichtel <nicolas.dichtel@...nd.com>, raven@...maw.net,
Christian Brauner <christian@...uner.io>,
keyrings@...r.kernel.org, linux-usb@...r.kernel.org,
linux-block <linux-block@...r.kernel.org>,
LSM List <linux-security-module@...r.kernel.org>,
linux-fsdevel <linux-fsdevel@...r.kernel.org>,
Linux API <linux-api@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [RFC PATCH 04/10] pipe: Use head and tail pointers for the ring,
not cursor and length [ver #2]
On 2019 Dez 06, Linus Torvalds wrote:
> On Fri, Dec 6, 2019 at 4:00 PM Johannes Hirte
> <johannes.hirte@...enkhaos.de> wrote:
> >
> > Tested with 5.4.0-11505-g347f56fb3890 and still the same wrong behavior.
>
> Ok, we'll continue looking.
>
> That said, your version string is strange.
>
> Commit 347f56fb3890 should be "v5.4.0-13174-g347f56fb3890", the fact
> that you have "11505" confuses me.
>
> The hash is what matters, but I wonder what is going on that you have
> the commit count in that version string so wrong.
>
> Linus
Yes, something got messed up here. After last pull, git describe says:
drm-next-2019-12-06-11662-g9455d25f4e3b
whereas with a fresh cloned repo I get:
v5.4-13331-g9455d25f4e3b
I assume the later is right. With this version the bug seems to be
fixed, regardless of the commit count. Tested with different websites
and firefox works as expected again.
--
Regards,
Johannes Hirte
Powered by blists - more mailing lists