From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 88771] New: No API to synchronize against SCSI bus scanning
Date: Sun, 23 Nov 2014 16:56:23 +0000 [thread overview]
Message-ID: <bug-88771-11613@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=88771
Bug ID: 88771
Summary: No API to synchronize against SCSI bus scanning
Product: IO/Storage
Version: 2.5
Kernel Version: 3.2.0
Hardware: All
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: SCSI
Assignee: linux-scsi@vger.kernel.org
Reporter: Simon.Richter@hogyros.de
Regression: No
With the rightful demise of the scsi_wait_scan module, there is no interface
left to find out whether any host adapter is currently scanning and synchronize
against it.
With a kernel that has asynchronous scanning disabled, modular SCSI drivers and
udev, this can be worked around by "udevadm settle", however that is not a
generic solution.
Would it make sense to provide a sysfs object that an userspace program could
use to synchronize against the end of SCSI scans?
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2014-11-23 16:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 16:56 bugzilla-daemon [this message]
2014-12-08 19:52 ` [Bug 88771] No API to synchronize against SCSI bus scanning bugzilla-daemon
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=bug-88771-11613@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-scsi@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 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.