From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Minas Harutyunyan <Minas.Harutyunyan@synopsys.com>
Cc: "linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
Felipe Balbi <balbi@kernel.org>, Jack Pham <jackp@codeaurora.org>,
Peter Chen <peter.chen@kernel.org>
Subject: Re: [PATCH] usb: dwc3: Fix debugfs creation flow
Date: Thu, 17 Jun 2021 13:01:53 +0200 [thread overview]
Message-ID: <YMsrofH0AVUUMH7y@kroah.com> (raw)
In-Reply-To: <0ba79afb-2b34-6e01-9ec3-622a3591ba5b@synopsys.com>
On Thu, Jun 17, 2021 at 09:14:37AM +0000, Minas Harutyunyan wrote:
> Hi Greg,
>
> On 6/17/2021 11:33 AM, Greg Kroah-Hartman wrote:
> > On Thu, Jun 17, 2021 at 07:11:33AM +0000, Minas Harutyunyan wrote:
> >> Hi Greg,
> >>
> >> On 6/17/2021 10:10 AM, Greg Kroah-Hartman wrote:
> >>> On Wed, Jun 16, 2021 at 10:56:02PM -0700, Minas Harutyunyan wrote:
> >>>> Creation EP's debugfs called earlier than debugfs folder for dwc3
> >>>> device created. As result EP's debugfs are created in '/sys/kernel/debug'
> >>>> instead of '/sys/kernel/debug/usb/dwc3.1.auto'.
> >>>>
> >>>> Moved dwc3_debugfs_init() function call before calling
> >>>> dwc3_core_init_mode() to allow create dwc3 debugfs parent before
> >>>> creating EP's debugfs's.
> >>>>
> >>>> Fixes: 8562d5bfc0fc ("USB: dwc3: remove debugfs root dentry storage")
> >>>> Signed-off-by: Minas Harutyunyan <hminas@synopsys.com>
> >>>> ---
> >>>> drivers/usb/dwc3/core.c | 3 ++-
> >>>> 1 file changed, 2 insertions(+), 1 deletion(-)
> >>>>
> >>>> diff --git a/drivers/usb/dwc3/core.c b/drivers/usb/dwc3/core.c
> >>>> index e0a8e796c158..ba74ad7f6995 100644
> >>>> --- a/drivers/usb/dwc3/core.c
> >>>> +++ b/drivers/usb/dwc3/core.c
> >>>> @@ -1620,17 +1620,18 @@ static int dwc3_probe(struct platform_device *pdev)
> >>>> }
> >>>>
> >>>> dwc3_check_params(dwc);
> >>>> + dwc3_debugfs_init(dwc);
> >>>>
> >>>> ret = dwc3_core_init_mode(dwc);
> >>>> if (ret)
> >>>> goto err5;
> >>>>
> >>>> - dwc3_debugfs_init(dwc);
> >>>> pm_runtime_put(dev);
> >>>>
> >>>> return 0;
> >>>>
> >>>> err5:
> >>>> + dwc3_debugfs_exit(dwc);
> >>>> dwc3_event_buffers_cleanup(dwc);
> >>>>
> >>>> usb_phy_shutdown(dwc->usb2_phy);
> >>>>
> >>>> base-commit: 1da8116eb0c5dfc05cfb89896239badb18c4daf3
> >>>
> >>> I thought we fixed this already in usb-next and usb-linus, right? Where
> >>> are you seeing this problem happening?
> >>
> >> I faced this issue on 5.13.0-rc6. Patch "USB: dwc3: remove debugfs root
> >> dentry storage" introduced this issue, because of debugfs_lookup()
> >> function. I don't see any fix in usb-next.
> >
> > 4bf584a03eec ("usb: dwc3: core: fix kernel panic when do reboot") in
> > linux-next "should" solve this issue. Or it was supposed to. I
> > thought. I'm getting confused about this problem these days...
>
> No, 4bf584a03eec ("usb: dwc3: core: fix kernel panic when do reboot")
> fix another thing.
> >
> > The commit you reference above in the fixes line is NOT in 5.13-rc6, so
> > how can this commit fix a problem in 5.13-rc6?
>
> I see that commit in your "usb-next" below "Merge tag 'v5.13-rc6'":
>
> https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git/log/?qt=grep&q=&h=usb-next
Yes, but that is NOT in 5.13-rc6, so your above comment does not make
sense to me.
So, to be specific, what commit causes this problem, that this patch
fixes?
thanks,
greg k-h
next prev parent reply other threads:[~2021-06-17 11:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-17 5:56 [PATCH] usb: dwc3: Fix debugfs creation flow Minas Harutyunyan
2021-06-17 6:10 ` Greg Kroah-Hartman
2021-06-17 7:11 ` Minas Harutyunyan
2021-06-17 7:33 ` Greg Kroah-Hartman
2021-06-17 9:14 ` Minas Harutyunyan
2021-06-17 11:01 ` Greg Kroah-Hartman [this message]
2021-06-17 16:20 ` Minas Harutyunyan
2021-06-17 6:31 ` Jack Pham
2021-06-17 7:24 ` Minas Harutyunyan
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=YMsrofH0AVUUMH7y@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Minas.Harutyunyan@synopsys.com \
--cc=balbi@kernel.org \
--cc=jackp@codeaurora.org \
--cc=linux-usb@vger.kernel.org \
--cc=peter.chen@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).