linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Todd Kjos <tkjos@google.com>
Cc: "regressions@lists.linux.dev" <regressions@lists.linux.dev>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"quackdoctech@gmail.com" <quackdoctech@gmail.com>
Subject: Re: Regression in BinderFS: Kernel bug at binder.c:2352
Date: Thu, 5 May 2022 09:51:04 +0200	[thread overview]
Message-ID: <f11fd704-7024-3b93-3ae5-0a102f6358c3@leemhuis.info> (raw)
In-Reply-To: <CAHRSSEyVc0pNwp23Tu2SH3ti0aKfTw+XRrHTuSkMjoCe7huHyA@mail.gmail.com>



On 04.05.22 17:17, Todd Kjos wrote:
> 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/

Ahh, great, many thx for the answer.

#regzbot fixed-by: 2d1746e3fda0c361

Ciao, Thorsten

>>
>> 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 nobody
>>>> acted upon since it was reported about a week ago, that's why I decided
>>>> 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=215795 :
>>>>
>>>>>  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 source 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 trying 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 kernel 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] [−] 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=215795
>>>>
>>>> Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
>>>>
>>>> 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 lack
>>>> 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 me
>>>> in a public reply, it's in everyone's interest to set the public record
>>>> straight.
>>>>
>>>> --
>>>> Additional information about regzbot:
>>>>
>>>> If you want to know more about regzbot, check out its web-interface, the
>>>> 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 ensures
>>>> the regression makes it onto the radar of the Linux kernel's regression
>>>> tracker -- that's in your interest, as it ensures your report won't fall
>>>> through the cracks unnoticed.
>>>>
>>>> Hint for developers: you normally don't need to care about regzbot once
>>>> 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'.
>>>
>>>
> 

      reply	other threads:[~2022-05-05  7:51 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 10:27 Regression in BinderFS: Kernel bug at binder.c:2352 Thorsten Leemhuis
2022-04-08 15:28 ` Todd Kjos
2022-05-04 10:47   ` Thorsten Leemhuis
2022-05-04 15:17     ` Todd Kjos
2022-05-05  7:51       ` Thorsten Leemhuis [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f11fd704-7024-3b93-3ae5-0a102f6358c3@leemhuis.info \
    --to=regressions@leemhuis.info \
    --cc=linux-kernel@vger.kernel.org \
    --cc=quackdoctech@gmail.com \
    --cc=regressions@lists.linux.dev \
    --cc=tkjos@google.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).