From: Oliver Neukum <oneukum@suse.com>
To: "Sebastian Andrzej Siewior" <bigeasy@linutronix.de>,
"Bjørn Mork" <bjorn@mork.no>
Cc: Robert Foss <robert.foss@collabora.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Alan Stern <stern@rowland.harvard.edu>,
linux-usb@vger.kernel.org
Subject: USB: cdc-wdm: don't enable interrupts in USB-giveback
Date: Wed, 13 Jun 2018 10:30:18 +0200 [thread overview]
Message-ID: <1528878618.28212.17.camel@suse.com> (raw)
On Di, 2018-06-12 at 21:57 +0200, Sebastian Andrzej Siewior wrote:
> > Yes, the atomic case should be rare. It will only happen on errors, and
> > IIUC that's only to work around issues caused by reporting errors back
> > to userspace without actually wanting to err out anyway.
>
> Yup. The missing part is if this was done to workaround a specific
> userland application or most/all of them.
Yes, If possible we should not regress in that regard.
> > I believe it would be better to decide one an error policy and stick to
> > that. Then you could just simplify away that whole mess, by either
> > ignoring the error and continue or bailing out and die.
>
> "Bailing out and die" would be a revert of commit c1da59dad0eb
> ("cdc-wdm: Clear read pipeline in case of error")?
> And ignoring the error would be "not updating rerr" in
> wdm_in_callback().
> I don't care either way. I can do whatever works for you/users best.
It seems to me that the core of the problem is handling an error
in irq context potentially. How about shifting it to a work queue?
Regards
Oliver
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-06-13 8:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-13 8:30 Oliver Neukum [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-06-12 19:57 USB: cdc-wdm: don't enable interrupts in USB-giveback Sebastian Andrzej Siewior
2018-06-12 18:28 Bjørn Mork
2018-06-12 17:48 Sebastian Andrzej Siewior
2018-06-12 16:43 Alan Stern
2018-06-12 16:31 Sebastian Andrzej Siewior
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=1528878618.28212.17.camel@suse.com \
--to=oneukum@suse.com \
--cc=bigeasy@linutronix.de \
--cc=bjorn@mork.no \
--cc=gregkh@linuxfoundation.org \
--cc=linux-usb@vger.kernel.org \
--cc=robert.foss@collabora.com \
--cc=stern@rowland.harvard.edu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.