From: Saravana Kannan <saravanak@google.com>
To: Michael Walle <michael@walle.cc>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
"Rafael J. Wysocki" <rafael@kernel.org>,
Android Kernel Team <kernel-team@android.com>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
LKML <linux-kernel@vger.kernel.org>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH v1] driver core: Update device link status correctly for SYNC_STATE_ONLY links
Date: Tue, 26 May 2020 11:08:12 -0700 [thread overview]
Message-ID: <CAGETcx_iHs5xsXq81k4YRzrFxs2j01u3HzfnSNU9Vxs8ZTGGuA@mail.gmail.com> (raw)
In-Reply-To: <dac3da8b373f131e53e18083f6fac5b0@walle.cc>
On Tue, May 26, 2020 at 4:04 AM Michael Walle <michael@walle.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
next prev parent reply other threads:[~2020-05-26 18:08 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-16 8:07 [PATCH v1] driver core: Fix memory leak when adding SYNC_STATE_ONLY device links Saravana Kannan
2020-05-18 7:48 ` Saravana Kannan
2020-05-18 8:03 ` Greg Kroah-Hartman
2020-05-18 19:47 ` Saravana Kannan
2020-05-19 3:00 ` [PATCH v2] driver core: Fix SYNC_STATE_ONLY device link implementation Saravana Kannan
2020-05-19 5:48 ` Greg Kroah-Hartman
2020-05-19 6:30 ` [PATCH v3] " Saravana Kannan
2020-05-19 10:47 ` Rafael J. Wysocki
2020-05-22 18:41 ` Michael Walle
2020-05-22 22:21 ` Saravana Kannan
2020-05-22 22:47 ` Michael Walle
2020-05-25 11:31 ` Michael Walle
2020-05-25 18:39 ` Saravana Kannan
2020-05-25 19:04 ` Michael Walle
2020-05-25 21:24 ` Saravana Kannan
2020-05-25 21:38 ` Michael Walle
2020-05-26 7:05 ` [PATCH v1] driver core: Update device link status correctly for SYNC_STATE_ONLY links Saravana Kannan
2020-05-26 7:07 ` Saravana Kannan
2020-05-26 11:04 ` Michael Walle
2020-05-26 18:08 ` Saravana Kannan [this message]
2020-05-26 8:28 ` Rafael J. Wysocki
2020-05-26 19:43 ` [PATCH v2] " Saravana Kannan
2020-05-26 21:13 ` Michael Walle
2020-05-26 21:45 ` Saravana Kannan
2020-05-26 21:53 ` Michael Walle
2020-05-26 22:00 ` Saravana Kannan
2020-05-26 22:09 ` [PATCH v3] " Saravana Kannan
2020-05-27 8:26 ` Rafael J. Wysocki
2020-05-28 16:09 ` Saravana Kannan
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=CAGETcx_iHs5xsXq81k4YRzrFxs2j01u3HzfnSNU9Vxs8ZTGGuA@mail.gmail.com \
--to=saravanak@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=kernel-team@android.com \
--cc=linux-kernel@vger.kernel.org \
--cc=michael@walle.cc \
--cc=rafael.j.wysocki@intel.com \
--cc=rafael@kernel.org \
--cc=stable@vger.kernel.org \
/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).