linux-kernel - Re: WARNING: ODEBUG bug in vudc

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <CACT4Y+abRq25axHrxNczh7sVw2RjYJB8y7JOBmyMmVF5xJ+Y1w@mail.gmail.com>
Date:   Mon, 11 Mar 2019 15:16:58 +0100
From:   Dmitry Vyukov <dvyukov@...gle.com>
To:     Shuah Khan <shuah@...nel.org>
Cc:     Valentina Manea <valentina.manea.m@...il.com>,
        Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        USB list <linux-usb@...r.kernel.org>,
        LKML <linux-kernel@...r.kernel.org>
Subject: Re: WARNING: ODEBUG bug in vudc_probe

On Fri, Sep 7, 2018 at 6:25 PM Dmitry Vyukov <dvyukov@...gle.com> wrote:
>
> On Fri, Sep 7, 2018 at 6:20 PM, Shuah Khan <shuah@...nel.org> wrote:
> > On 09/07/2018 10:14 AM, Dmitry Vyukov wrote:
> >> On Fri, Sep 7, 2018 at 6:03 PM, Shuah Khan <shuah@...nel.org> wrote:
> >>> Hi Dmitry,
> >>>
> >>> On 09/07/2018 04:54 AM, Dmitry Vyukov wrote:
> >>>> Hi,
> >>>>
> >>>> I am getting the following error while booting kernel on upstream
> >>>> commit a49a9dcce802b3651013f659813df1361d306172, config is attached.
> >>>> Seems there is some kind of resource leak.
> >>>>
> >>>> Thanks
> >>>
> >>> Odd. This commit has nothing to do with vudc.
> >>
> >> This is not the guilty commit, I just described state of my tree.
> >>
> >
> > Can you send me the full dmesg?
>
> Here it is:
>
> https://gist.githubusercontent.com/dvyukov/e9dec59fb23da9cedd8ab07a7d8c78ae/raw/3ee13c7a1f406c9927ca3b16db262f2c78e84536/gistfile1.txt

Hello,

The boot seems to be fixed now, but what commit fixed it?

This bug makes all kernels starting from 4.14 unbootable for the
purposes of bisection. If we figure out what was the bug and what
fixed it, we can think of possible ways of unbreaking kernel boot.

Thanks