kernel/linux.git/drivers/block/ub.c, branch linux-2.6.18.y

[PATCH] devfs: Remove the gendisk devfs_name field as it's no longer needed

2006-06-26T19:25:08+00:00

And remove the now unneeded number field. Also fixes all drivers that set these fields. Signed-off-by: Greg Kroah-Hartman

[PATCH] devfs: Remove the devfs_fs_kernel.h file from the tree

2006-06-26T19:25:08+00:00

Also fixes up all files that #include it. Signed-off-by: Greg Kroah-Hartman

[PATCH] devfs: Remove devfs_remove() function from the kernel tree

2006-06-26T19:25:07+00:00

Removes the devfs_remove() function and all callers of it. Signed-off-by: Greg Kroah-Hartman

[PATCH] devfs: Remove devfs_mk_dir() function from the kernel tree

2006-06-26T19:25:06+00:00

Removes the devfs_mk_dir() function and all callers of it. Signed-off-by: Greg Kroah-Hartman

[PATCH] ub: random cleanups

2006-06-21T22:04:14+00:00

Remove some silly messages and cast in stone "temporary" messages which we keep around. Also, I am hesitant to remove the initialization retries without having the hardware to test (anyone who was at KS04 has a spare?) Signed-off-by: Pete Zaitcev Signed-off-by: Greg Kroah-Hartman

[PATCH] ub: atomic add_disk

2006-06-21T22:04:14+00:00

I am taling about this: "if (disk->flags & GENHD_FL_UP) del_gendisk(disk);" If del_gendisk() undoes add_disk() like viro just said, why is it conditional? huh? add_disk() sets the damn flag So, I should not need to check ever so the above is "if I've called add_disk(), call gendisk()" which might be what you want, of course but usually you know if you'd done add_disk() on that puppy anyway In ub, nobody upstream should ever see half-constructed disks before they were passed to add_disk. To that end, only add the struct lun to the list on the path of no return. With that fix in place, we do not need to test GENHD_FL_UP. Signed-off-by: Pete Zaitcev Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: clean out an unnecessary NULL check from ub

2006-06-21T22:04:09+00:00

Remove the check for NULL which makes no sense. Suggested by Al. Signed-off-by: Pete Zaitcev Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: ub oops in block_uevent

2006-05-09T06:43:55+00:00

In kernel 2.6.16, if a mounted storage device is removed, an oops happens because ub supplies an interface device (and kobject) to the block layer, but neglects to pin it. And apparently, the block layer expects its users to pin device structures. The code in ub was broken this way for years. But the bug was exposed only by 2.6.16 when it started to call block_uevent on close, which traverses device structures (kobjects actually). Signed-off-by: Pete Zaitcev Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: ub 03 drop stall clearing

2006-03-20T22:50:00+00:00

Matt mentioned that a very old ZIP-100 actually does need this, but I am yet to see anyone who actually has one still working and uses ub with it. He/she must be a retrocomputing geek, who can easily bias it to usb-storage with libusual, if needed. Meanwhile, common folks have trouble with poorly designed USB keys and some el-cheapo European music players. I think we better drop this for now. Signed-off-by: Pete Zaitcev Signed-off-by: Greg Kroah-Hartman

[PATCH] USB: ub 02 remove diag

2006-03-20T22:50:00+00:00

Remove the "diag" file from the sysfs. The usbmon is good enough these days so I do not need this feature anymore. Also, sysfs is a pain. Al Viro caught a race in this, which I thought too bothersome to fix. Signed-off-by: Pete Zaitcev Signed-off-by: Greg Kroah-Hartman