Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <d62431af-5ce4-3d8f-542f-df8e7a7faaf1@leemhuis.info>
 <CAHRSSEw5CBnCpXcowKKG5KzOoazecC6jDn+4_fd0Gp3+e9Yixw@mail.gmail.com> <f42e91ae-a22d-b664-003a-e1698dc021aa@leemhuis.info>
In-Reply-To: <f42e91ae-a22d-b664-003a-e1698dc021aa@leemhuis.info>
From:   Todd Kjos <tkjos@google.com>
Date:   Wed, 4 May 2022 08:17:16 -0700
Message-ID: <CAHRSSEyVc0pNwp23Tu2SH3ti0aKfTw+XRrHTuSkMjoCe7huHyA@mail.gmail.com>
Subject: Re: Regression in BinderFS: Kernel bug at binder.c:2352
To:     Thorsten Leemhuis <regressions@leemhuis.info>
Cc:     "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        "quackdoctech@gmail.com" <quackdoctech@gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Precedence: bulk

On Wed, May 4, 2022 at 3:47 AM Thorsten Leemhuis
<regressions@leemhuis.info> wrote:
>
>
>
> On 08.04.22 17:28, Todd Kjos wrote:
> > On Fri, Apr 8, 2022 at 3:27 AM Thorsten Leemhuis
> > <regressions@leemhuis.info> wrote:
> >>
> >> Hi, this is your Linux kernel regression tracker.
> >>
> >> Todd, seems there is a regression that is caused by one of your Linux
> >> kernel changes:
> >
> > Yes, it was reported a few days ago by the ChromeOS team. Already
> > looking into it.
>
> What happen to this? It looks like it has fallen through the cracks. Or
> was progress made and it just didn't link to the ticket or mention the
> reporter?

It was found and fixed independently by Alessandro Astone in
https://lore.kernel.org/lkml/20220415120015.52684-2-ales.astone@gmail.com/

>
> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>
> P.S.: As the Linux kernel's regression tracker I deal with a lot of
> reports and sometimes miss something important when writing mails like
> this. If that's the case here, don't hesitate to tell me in a public
> reply, it's in everyone's interest to set the public record straight.
>
> #regzbot poke
>
> >> I noticed a regression report in bugzilla.kernel.org that afaics nobod=
y
> >> acted upon since it was reported about a week ago, that's why I decide=
d
> >> to forward it to the lists and all people that seemed to be relevant
> >> here. To quote from https://bugzilla.kernel.org/show_bug.cgi?id=3D2157=
95 :
> >>
> >>>  quackdoctech@gmail.com 2022-04-02 19:56:29 UTC
> >>>
> >>> Created attachment 300686 [details]
> >>> Dmesg output cut to error
> >>>
> >>> Apologies if this should have been reported under Drivers where the s=
ource is, selftests has it listed under filesystems so I chose here. Using =
Waydroid which is android run via LXC, on android 10 the bug comes when try=
ing to use video playback. I know of issues on android 11 but have not yet =
had the chance to get the logs from it. the issue does not occur in Linux k=
ernel 5.16 series. but does occur on linux 5.17. the issue is confirmed on =
both Arch's linux-zen 5.17.1.zen1-1 kernel as well as some users reporting =
a fedora kernel with the issue.
> >>>
> >>> [reply] [=E2=88=92] Comment 1 quackdoctech@gmail.com 2022-04-03 19:38=
:37 UTC
> >>>
> >>> I've narrowed down the issue to this patch series.
> >>>
> >>> https://lore.kernel.org/all/20211130185152.437403-1-tkjos@google.com/
> >>>
> >>
> >> Could somebody take a look into this? Or was this discussed somewhere
> >> else already? Or even fixed?
> >>
> >> Anyway, to get this tracked:
> >>
> >> #regzbot introduced: v5.16..v5.17
> >> #regzbot from: quackdoctech@gmail.com <quackdoctech@gmail.com>
> >> #regzbot title: BinderFS: Kernel bug at binder.c:2352
> >> #regzbot link: https://bugzilla.kernel.org/show_bug.cgi?id=3D215795
> >>
> >> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' ha=
t)
> >>
> >> P.S.: As the Linux kernel's regression tracker I'm getting a lot of
> >> reports on my table. I can only look briefly into most of them and lac=
k
> >> knowledge about most of the areas they concern. I thus unfortunately
> >> will sometimes get things wrong or miss something important. I hope
> >> that's not the case here; if you think it is, don't hesitate to tell m=
e
> >> in a public reply, it's in everyone's interest to set the public recor=
d
> >> straight.
> >>
> >> --
> >> Additional information about regzbot:
> >>
> >> If you want to know more about regzbot, check out its web-interface, t=
he
> >> getting start guide, and the references documentation:
> >>
> >> https://linux-regtracking.leemhuis.info/regzbot/
> >> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/getting_started.md
> >> https://gitlab.com/knurd42/regzbot/-/blob/main/docs/reference.md
> >>
> >> The last two documents will explain how you can interact with regzbot
> >> yourself if your want to.
> >>
> >> Hint for reporters: when reporting a regression it's in your interest =
to
> >> CC the regression list and tell regzbot about the issue, as that ensur=
es
> >> the regression makes it onto the radar of the Linux kernel's regressio=
n
> >> tracker -- that's in your interest, as it ensures your report won't fa=
ll
> >> through the cracks unnoticed.
> >>
> >> Hint for developers: you normally don't need to care about regzbot onc=
e
> >> it's involved. Fix the issue as you normally would, just remember to
> >> include 'Link:' tag in the patch descriptions pointing to all reports
> >> about the issue. This has been expected from developers even before
> >> regzbot showed up for reasons explained in
> >> 'Documentation/process/submitting-patches.rst' and
> >> 'Documentation/process/5.Posting.rst'.
> >
> >