All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 12207] block reads/writes > 122880 bytes to USB tape drive gives EBUSY
Date: Sat, 11 Apr 2009 14:26:01 GMT	[thread overview]
Message-ID: <200904111426.n3BEQ1bl032734@demeter.kernel.org> (raw)
In-Reply-To: <bug-12207-11613@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=12207





--- Comment #32 from Alan Stern <stern@rowland.harvard.edu>  2009-04-11 14:26:00 ---
> Yes, SCSI uses the (Linux) block layer and the attributes do exist within 
> the kernel. They just are not visible in sysfs for character devices. Last 
> night I read the code to find out why. Your analysis is correct but it 
> only shows that the kobject exists. The kobject is added to sysfs using 
> kobject_add() in blk_register_queue() called by add_disk(), which is only 
> called by disk drivers.

You are right.

And this makes me feel better -- I had thought that usb-storage's 
max_sectors attribute was redundant.  Now I know that for some 
SCSI-over-USB devices, the information is not accessible anywhere else.

> Whether character devices should add the kobject somewhere in sysfs is 
> getting beyond the original topic in this bugzilla entry. This is a more 
> general problem because there is no /sys/char directory. My current 
> opinion is that it would be nice to see these attributes somewhere, but 
> probably not worth the trouble.

Until somebody asks for them, we're okay.  However it shouldn't be very
hard to write a function like blk_register_queue() that accepts a
non-disk device as parent.  (And likewise for blk_unregister_queue, of
course.)

Alan Stern

-- 
Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

  parent reply	other threads:[~2009-04-11 14:26 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-12 21:41 [Bug 12207] New: block reads/writes > 122880 bytes to USB tape drive gives EBUSY bugme-daemon
2008-12-22 17:44 ` [Bug 12207] " bugme-daemon
2008-12-22 18:08 ` bugme-daemon
2008-12-22 18:09 ` bugme-daemon
2008-12-22 18:09 ` bugme-daemon
2008-12-23  7:30 ` bugme-daemon
2008-12-23 12:31   ` Oliver Neukum
2008-12-23 12:32 ` bugme-daemon
2008-12-23 13:56 ` bugme-daemon
2008-12-23 13:59 ` bugme-daemon
2008-12-23 14:47   ` Boaz Harrosh
2008-12-23 14:55   ` James Bottomley
2008-12-23 15:33     ` James Bottomley
2008-12-23 14:42 ` bugme-daemon
2008-12-23 14:46 ` bugme-daemon
2008-12-23 14:48 ` bugme-daemon
2008-12-23 14:54 ` bugme-daemon
2008-12-23 14:56 ` bugme-daemon
2008-12-23 15:33 ` bugme-daemon
2008-12-23 16:18 ` bugme-daemon
2008-12-23 16:30   ` Kai Makisara
2008-12-23 16:42     ` James Bottomley
2008-12-23 16:30 ` bugme-daemon
2008-12-23 16:42 ` bugme-daemon
2008-12-24  2:56 ` bugme-daemon
2008-12-24  4:19   ` FUJITA Tomonori
2008-12-24  4:19 ` bugme-daemon
2008-12-30 19:39 ` bugme-daemon
2009-02-05 21:12 ` bugme-daemon
2009-02-05 21:48 ` bugme-daemon
2009-03-09 20:48 ` bugme-daemon
2009-03-09 20:55 ` bugme-daemon
2009-03-22 20:52 ` bugme-daemon
2009-03-26 19:35 ` bugzilla-daemon
2009-04-07 10:43 ` bugzilla-daemon
2009-04-09 21:08 ` bugzilla-daemon
2009-04-10  9:48 ` bugzilla-daemon
2009-04-10 15:19 ` bugzilla-daemon
2009-04-10 19:29 ` bugzilla-daemon
2009-04-11  2:38 ` bugzilla-daemon
2009-04-11  6:12 ` bugzilla-daemon
2009-04-11 14:26 ` bugzilla-daemon [this message]
2009-04-15  9:55 ` bugzilla-daemon
2009-04-15 15:42 ` 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=200904111426.n3BEQ1bl032734@demeter.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.