linux.git/drivers/usb/core/devio.c, branch v2.6.29-rc2

USB: fix minor nit in usbfs checking

2009-01-07T18:00:13+00:00

One minor nit did show up, though.  The patch below
seems to make more sense than the code does without it.

Signed-off-by: Mark Lord 
Signed-off-by: Greg Kroah-Hartman

USB: Remove restrictions on signal numbers in devio.c

2009-01-07T17:59:51+00:00

Just over a year ago (!) I had this brief exchange with Alan Stern:

>> It seems that the signal that can be used with USBDEVFS_DISCSIGNAL and 
>> in usbdevfs_urb.signr is limited to the real-time signals SIGRTMIN to 
>> SIGRTMAX. What's the rationale for this restriction? I believe that a 
>> process can kill() itself with any signal number, can't it? I was 
>> planning to use SIGIO for usbdevfs_urb.signr and SIGTERM (uncaught) for 
>> USBDEVFS_DISCSIGNAL. I don't think I'll have a problem with using 
>> SIGRTMIN+n instead, but I'm curious to know if there's some subtle 
>> problem with the non-real-time signals that I should be aware of.
>
> I don't know of any reason for this restriction.

Since no-one else could think of a reason either, I offer the following 
patch which allows any signal to be used with USBDEVFS_DISCSIGNAL and 
usbdevfs_urb.signr.

Signed-off-by: Phil Endecott 
Cc: Alan Stern 
Signed-off-by: Greg Kroah-Hartman

CRED: Wrap current->cred and a few other accessors

2008-11-13T23:39:18+00:00

Wrap current->cred and a few other accessors to hide their actual
implementation.

Signed-off-by: David Howells 
Acked-by: James Morris 
Acked-by: Serge Hallyn 
Signed-off-by: James Morris

CRED: Wrap task credential accesses in the USB driver

2008-11-13T23:38:43+00:00

Wrap access to task credentials so that they can be separated more easily from
the task_struct during the introduction of COW creds.

Change most current->(|e|s|fs)[ug]id to current_(|e|s|fs)[ug]id().

Change some task->e?[ug]id to task_e?[ug]id().  In some places it makes more
sense to use RCU directly rather than a convenient wrapper; these will be
addressed by later patches.

Signed-off-by: David Howells 
Reviewed-by: James Morris 
Acked-by: Serge Hallyn 
Cc: Greg Kroah-Hartman 
Cc: linux-usb@vger.kernel.org
Signed-off-by: James Morris

USB: remove err() macro from usb core code

2008-10-17T21:41:11+00:00

USB should not be having it's own printk macros, so remove err() and
use the system-wide standard of dev_err() wherever possible.  In the
few places that will not work out, use a basic printk().

Signed-off-by: Greg Kroah-Hartman

USB: remove warn() macro from usb drivers

2008-10-17T21:41:09+00:00

USB should not be having it's own printk macros, so remove warn() and
use the system-wide standard of dev_warn() wherever possible.  In the
few places that will not work out, use a basic printk().

Signed-off-by: Greg Kroah-Hartman

USB: snoop processes opening usbfs device files

2008-10-17T21:41:03+00:00

This patch (as1148) adds a new "snoop" message to usbfs when a device
file is opened, identifying the process responsible.  This comes in
extremely handy when trying to determine which program is doing some
unwanted USB access.

Signed-off-by: Alan Stern 
Signed-off-by: Greg Kroah-Hartman

device create: usb: convert device_create_drvdata to device_create

2008-10-16T16:24:45+00:00

Now that device_create() has been audited, rename things back to the
original call to be sane.

Signed-off-by: Greg Kroah-Hartman

device create: usb: convert device_create to device_create_drvdata

2008-07-22T04:54:46+00:00

device_create() is race-prone, so use the race-free
device_create_drvdata() instead as device_create() is going away.

Signed-off-by: Greg Kroah-Hartman

sysfs: add /sys/dev/{char,block} to lookup sysfs path by major:minor

2008-07-22T04:54:40+00:00

Why?:
There are occasions where userspace would like to access sysfs
attributes for a device but it may not know how sysfs has named the
device or the path.  For example what is the sysfs path for
/dev/disk/by-id/ata-ST3160827AS_5MT004CK?  With this change a call to
stat(2) returns the major:minor then userspace can see that
/sys/dev/block/8:32 links to /sys/block/sdc.

What are the alternatives?:
1/ Add an ioctl to return the path: Doable, but sysfs is meant to reduce
   the need to proliferate ioctl interfaces into the kernel, so this
   seems counter productive.

2/ Use udev to create these symlinks: Also doable, but it adds a
   udev dependency to utilities that might be running in a limited
   environment like an initramfs.

3/ Do a full-tree search of sysfs.

[kay.sievers@vrfy.org: fix duplicate registrations]
[kay.sievers@vrfy.org: cleanup suggestions]

Cc: Neil Brown 
Cc: Tejun Heo 
Acked-by: Kay Sievers 
Reviewed-by: SL Baur 
Acked-by: Kay Sievers 
Acked-by: Mark Lord 
Acked-by: H. Peter Anvin 
Signed-off-by: Dan Williams 
Signed-off-by: Greg Kroah-Hartman