From: Mike Christie <mchristi@redhat.com>
To: hamish.martin@alliedtelesis.co.nz,
chris.packham@alliedtelesis.co.nz,
Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: uio regression in 4.18-rc1 due to "uio: Prevent device destruction while fds are open"
Date: Wed, 20 Jun 2018 11:06:11 -0500 [thread overview]
Message-ID: <5B2A7B73.5090000@redhat.com> (raw)
Hi Hamish,
I am hitting a regression with your patch:
commit a93e7b331568227500186a465fee3c2cb5dffd1f
Author: Hamish Martin <hamish.martin@alliedtelesis.co.nz>
Date: Mon May 14 13:32:23 2018 +1200
uio: Prevent device destruction while fds are open
The problem is the addition of spin_lock_irqsave in uio_write. This
leads to hitting uio_write -> copy_from_user -> _copy_from_user ->
might_fault and the logs filling up with sleeping warnings.
I also noticed some uio drivers allocate memory, sleep, grab mutexes
from callouts like open() and release and uio is now doing
spin_lock_irqsave while calling them.
Note target_core_user's irqcontrol looks buggy and was just doing more
work than it should in that callout. I can fix that driver.
next reply other threads:[~2018-06-20 16:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 16:06 Mike Christie [this message]
2018-06-20 22:00 ` Hamish Martin
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=5B2A7B73.5090000@redhat.com \
--to=mchristi@redhat.com \
--cc=chris.packham@alliedtelesis.co.nz \
--cc=gregkh@linuxfoundation.org \
--cc=hamish.martin@alliedtelesis.co.nz \
--cc=linux-kernel@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
Powered by JetHome