From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Guido Kiener <Guido.Kiener@rohde-schwarz.com>
Cc: Dmitry Vyukov <dvyukov@google.com>,
syzbot <syzbot+e2eae5639e7203360018@syzkaller.appspotmail.com>,
"dpenkler@gmail.com" <dpenkler@gmail.com>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
USB list <linux-usb@vger.kernel.org>,
"bp@alien8.de" <bp@alien8.de>,
"dwmw@amazon.co.uk" <dwmw@amazon.co.uk>,
"hpa@zytor.com" <hpa@zytor.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"luto@kernel.org" <luto@kernel.org>,
"mingo@redhat.com" <mingo@redhat.com>,
"syzkaller-bugs@googlegroups.com"
<syzkaller-bugs@googlegroups.com>,
"tglx@linutronix.de" <tglx@linutronix.de>,
"x86@kernel.org" <x86@kernel.org>
Subject: Re: Re: [syzbot] INFO: rcu detected stall in tx
Date: Tue, 20 Apr 2021 09:48:54 +0200 [thread overview]
Message-ID: <YH6HZjbrRibJgFyh@kroah.com> (raw)
In-Reply-To: <d1e8e0608903431e8199d9804fecca36@rohde-schwarz.com>
On Mon, Apr 19, 2021 at 08:56:19PM +0000, Guido Kiener wrote:
> Hi all,
>
> The error is in usbtmc_interrupt(struct urb *urb) since five years. The status code EPROTO is not handled correctly.
> It's not a showstopper, but we should fix it and check the status code according to usbtmc_read_bulk_cb() or
> usb_skeleton.c.
> @Dave: Do you have time? Otherwise I can do it.
> @Greg: Is it urgent?
No idea, but patches for known problems are always good to get completed
as soon as possible :)
thanks,
greg k-h
next prev parent reply other threads:[~2021-04-20 7:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 20:56 Guido Kiener
2021-04-20 7:48 ` Greg Kroah-Hartman [this message]
2021-05-03 21:56 Guido Kiener
2021-05-04 15:13 ` Alan Stern
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=YH6HZjbrRibJgFyh@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=Guido.Kiener@rohde-schwarz.com \
--cc=bp@alien8.de \
--cc=dpenkler@gmail.com \
--cc=dvyukov@google.com \
--cc=dwmw@amazon.co.uk \
--cc=hpa@zytor.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=luto@kernel.org \
--cc=mingo@redhat.com \
--cc=syzbot+e2eae5639e7203360018@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=x86@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
all inboxes | Powered by JetHome®