linux-kernel - Re: [PATCH v1] driver core: Update device link status correctly for SYNC_STATE

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]

Date:   Tue, 26 May 2020 11:08:12 -0700
From:   Saravana Kannan <saravanak@...gle.com>
To:     Michael Walle <michael@...le.cc>
Cc:     Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
        "Rafael J. Wysocki" <rafael@...nel.org>,
        Android Kernel Team <kernel-team@...roid.com>,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        LKML <linux-kernel@...r.kernel.org>,
        stable <stable@...r.kernel.org>
Subject: Re: [PATCH v1] driver core: Update device link status correctly for
 SYNC_STATE_ONLY links

On Tue, May 26, 2020 at 4:04 AM Michael Walle <michael@...le.cc> wrote:
>
> Hi Saravana,
>
> Am 2020-05-26 09:07, schrieb Saravana Kannan:
> >> Greg,
> >>
> >> I think this is the issue Michael ran into. I'd like him to test the
> >> fix
> >> before it's pulled in.
> >>
> >> Michael,
> >>
> >> If you can test this on the branch you saw the issue in and give a
> >> Tested-by if it works, that'd be great.
>
> Unfortunately, now I'm triggering another WARN_ON() in
> device_links_driver_bound():
>    WARN_ON(link->status != DL_STATE_DORMANT);
>
> I've attached two bootlog one based on linux-next-20200525 with this
> patch applied and another one where your previous debug printfs are
> applied, too.
>
> Let me know, if you need any other debug outputs.

Can you make the same debug changes I did for the other WARN and get
me the logs?

Thanks,
Saravana