- 04 Nov, 2004 19 commits
-
-
bk://kernel.bkbits.net/gregkh/linux/driver-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://kernel.bkbits.net/gregkh/linux/usb-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Maneesh Soni authored
On Thu, Nov 04, 2004 at 12:52:38PM -0800, Greg KH wrote: > Hi, > > I get the following BUG in the sysfs code when I do: > - plug in a usb-serial device. > - open the port with 'cat /dev/ttyUSB0' > - unplug the device. > - stop the 'cat' process with control-C > > This used to work just fine before your big sysfs changes. There is a similar problem reported by s390 people where we see parent kobject (directory) going away before child kobject (sub-directory). It seems kobject code is able to handle this, but not the sysfs. What could be happening that in sysfs_remove_dir() of parent directory, we try to remove its contents. It works well with the regular files as it is the final removal for sysfs_dirent corresponding to the files. But in case of sub-directory we are doing an extra sysfs_put(). Once while removing parent and the other one being the one from when sysfs_remove_dir() is called for the child. The following patch worked for the s390 people, I hope same will work in this case also. o Do not remove sysfs_dirents corresponding to the sub-directory in sysfs_remove_dir(). They will be removed in the sysfs_remove_dir() call for the specific sub-directory. Signed-off-by: Maneesh Soni <maneesh@in.ibm.com> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Andrew Morton authored
The spin_unlock() in rotate_reclaimable_page() is not a sufficient memory barrier. Signed-off-by: Andrew Morton <akpm@osdl.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Linus Torvalds authored
"clear_buffer_locked()" is just a nicer name for a clear-bit, and on x86 (and others) we don't need any expensive memory barriers after that.
-
Greg Kroah-Hartman authored
into kroah.com:/home/greg/linux/BK/driver-2.6
-
Greg Kroah-Hartman authored
into kroah.com:/home/greg/linux/BK/usb-2.6
-
Martin Waitz authored
kfifo_alloc tries to round up the buffer size to the next power of two. But it accidently uses the original size when calling kfifo_init, which will BUG. Acked-by: Stelian Pop <stelian@popies.net> Signed-off-by: Martin Waitz <tali@admingilde.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Pete Zaitcev authored
This is a relatively small changeset, to address small nagging problems. Andrew pointed me at the double registration specifically, so I had to do something about it. At least now Fabio's box won't collapse if he configures UB by mistake. Also, a few people complained that the help text was misleading. I have not done anything about the oops on disconnect which happens to Martin Schlemmer. It's next. After that I can get to Peter Jones' CD burning patch and doing resets. - Fix double kobject registration and eventual oops on unplug if a device is not cooperating. - Add a reference to usb-storage into the configuration help. - Just upping timeouts fixes my ZIP drive. - Max out the diag (trace) file size. - Set capacity to zero in case the media is absent. It works in 2.4.10-rc1. Either Al fixed the block layer, or the whole thing was a bug in ub.c (and sd.c) and a big misunderstanding. Signed-off-by: Pete Zaitcev <zaitcev@redhat.com> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Robert Love authored
Attached patch adds a MAINTAINER entry for the kernel event layer. Signed-Off-By: Robert Love <rml@novell.com> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Robert Love authored
Looks like kobject_uevent_init is executed before netlink_proto_init and consequently always fails. Not cool. Attached patch switches the initialization over from core_initcall (init level 1) to postcore_initcall (init level 2). Netlink's initialization is done in core_initcall, so this should fix the problem. We should be fine waiting until postcore_initcall. Also a couple white space changes mixed in, because I am anal. Signed-Off-By: Robert Love <rml@novell.com> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Greg Kroah-Hartman authored
Thanks to Serge Hallyn <serue@us.ibm.com> for pointing this out. Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Linus Torvalds authored
This clarifies more of the x86 caller/callee stack ownership issues by making the exception and interrupt handler assembler interfaces use register calling conventions. System calls still use the stack. Tested with "crashme" on UP/SMP.
-
Tejun Heo authored
df_05_device_add_ref_fix.patch In device_add(), @dev wan't put'd properly when it has zero length bus_id (error path). Fixed. Signed-off-by: Tejun Heo <tj@home-tj.org> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Tejun Heo authored
df_04_kobject_add_ref_fix.patch In kobject_add(), @kobj wasn't put'd properly on error path. This patch fixes it. Signed-off-by: Tejun Heo <tj@home-tj.org> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Tejun Heo authored
df_03_sysfs_release_fix.patch Some attributes are allocated dynamically (e.g. module and device parameters) and are usually deallocated when the assoicated kobject is released. So, it's not safe to access attr after putting the kobject. Signed-off-by: Tejun Heo <tj@home-tj.org> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Tejun Heo authored
df_02_bus_rescan_devcies_fix.patch bus_rescan_devices() eventually calls device_attach() and thus requires write locking the corresponding bus. The original code just called bus_for_each_dev() which only read locks the bus. This patch separates __bus_for_each_dev() and __bus_for_each_drv(), which don't do locking themselves, out from the original functions and call them with read lock in the original functions and with write lock in bus_rescan_devices(). Signed-off-by: Tejun Heo <tj@home-tj.org> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Tejun Heo authored
df_01_driver_attach_comment_fix.patch bus_match() was renamed to driver_probe_device() but the comment for device_attach() wasn't updated. This patch updates it. Signed-off-by: Tejun Heo <tj@home-tj.org> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Kay Sievers authored
Add the sysfs path of the physical device to the hotplug event of class and block devices. This should solve the userspace issue not to know if the device is a virtual one and the "device" symlink will never be created, but we sit there and wait for it to show up not knowing when we should give up. Also the bus name is added to the hotplug event, so we don't need to reverse lookup in the /sys/bus/* directory which bus our physical device belongs to. This is e.g. the value matched against the BUS= key, that may be used in an udev rule. This is a PCI network card: ACTION=add SUBSYSTEM=net DEVPATH=/class/net/eth0 PHYSDEVPATH=/devices/pci0000:00/0000:00:1e.0/0000:02:01.0 PHYSDEVBUS=pci INTERFACE=eth0 SEQNUM=827 PATH=/sbin:/bin:/usr/sbin:/usr/bin HOME=/ This is a IDE CDROM: ACTION=add SUBSYSTEM=block DEVPATH=/block/hdc PHYSDEVPATH=/devices/pci0000:00/0000:00:1f.1/ide1/1.0 PHYSDEVBUS=ide SEQNUM=1017 PATH=/sbin:/bin:/usr/sbin:/usr/bin HOME=/ This is an USB-stick partition: ACTION=add SUBSYSTEM=block DEVPATH=/block/sda/sda1 PHYSDEVPATH=/devices/pci0000:00/0000:00:1d.1/usb3/3-1/3-1:1.0/host1/target1:0:0/1:0:0:0 PHYSDEVBUS=scsi SEQNUM=1032 PATH=/sbin:/bin:/usr/sbin:/usr/bin HOME=/ Signed-off-by: Kay Sievers <kay.sievers@vrfy.org> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
- 03 Nov, 2004 21 commits
-
-
Jens Axboe authored
We need to open the gap between congestion on/off a little bit, or we risk burning many cycles continually putting processes on a wait queue only to wake them up again immediately. This was observed with CFQ at least, which showed way excessive sys time. Patch is from Arjan. Signed-off-by: Jens Axboe <axboe@suse.de> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
Jens Axboe authored
Patch is from Daniel Drake <dsd@gentoo.org> Signed-off-by: Jens Axboe <axboe@suse.de> Signed-off-by: Daniel Drake <dsd@gentoo.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
bk://kernel.bkbits.net/davem/net-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
David S. Miller authored
Signed-off-by: David S. Miller <davem@davemloft.net>
-
Paul Mackerras authored
Using idr_get_new_above in init_new_context lets us get rid of an awkward init function which wasn't running early enough in boot anyway. Signed-off-by: Nathan Lynch <nathanl@austin.ibm.com> Signed-off-by: Paul Mackerras <paulus@samba.org> Signed-off-by: Linus Torvalds <torvalds@osdl.org>
-
http://lia64.bkbits.net/linux-ia64-release-2.6.10Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
bk://kernel.bkbits.net/davem/net-2.6Linus Torvalds authored
into ppc970.osdl.org:/home/torvalds/v2.6/linux
-
Andries E. Brouwer authored
The routine ext2_readdir() will, when reading a directory page returns an error, try the next page, without reporting the error to user space. That is bad, and the patch below changes that. In my case the filesystem was damaged, and ext2_readdir wanted to read 60000+ pages and wrote as many error messages to syslog ("attempt to access beyond end"), not what one wants. [no doubt a similar patch is appropriate for ext3]
-
Matt Domsch authored
This preserves 2.4.x behavior. Signed-off-by: David S. Miller <davem@davemloft.net>
-
Greg Kroah-Hartman authored
Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Lonnie Mendez authored
This patch adds the cypress_m8 usb-serial driver for the Delorme Earthmate usb gps and the Cypress hid->com rs232 adapter to the kernel tree. Signed-off-by: Lonnie Mendez <lmendez19@austin.rr.com> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Jonathan McDowell authored
The patch below adds support for the KC2190 usb-to-usb networking device; the version I have reports itself as: Bus 001 Device 003: ID 050f:0190 KC Technology, Inc. I was under the impression that support for this had been added a long time ago, but searching through old kernel versions all I could find was a comment about the chip, with no support. Patch is against 2.6.9 but is pretty minimal. I don't have a Windows box around to test interoperability with that driver, but the patch appears to make it work perfectly between 2 Linux boxes. Signed-off-by: Jonathan McDowell <noodles@earth.li> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Herbert Xu authored
It is updated outside of locks, so... Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: David S. Miller <davem@davemloft.net>
-
David Brownell authored
On OMAP-1510 the 48MHz DPLL used by USB is now set up earlier in the boot process. On Innovator, both host ports work by default. (Although USB2 conflicts with ttyS2, which you might prefer.) Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
David Brownell authored
This patch updates the serial gadget driver: - The bulk is Al Borcher's version 2.0 updates: * Use the new utilities to build config descriptors from tables. * Add CDC ACM support, which brings lots of goodness including interop with Windows. * Work better given PXA 25x hardware automagic. - I have a few minor tweaks. * Match the recent tty API change: from_user is gone!! * Define new product ID for the CDC ACM version, so Windows registry won't get confused by the non-ACM version. * Add OTG descriptor * Allocates packet buffers more efficiently on platforms like OMAP: use kmalloc not the dma-coherent allocator. Al has some docs on how to talk to Windows this, including an INF file. Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
David Brownell authored
This has minor patches to the ethernet, file_storage, and zero gadget drivers. - Use longer "manufacturer" strings; CONFIG_LOCALVERSION would overflow. - Remove compile warning on file_storage with non-net2280 - Oops fix in ethernet gadget, on boards that don't report VBUS Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
David Brownell authored
This is the second of the patches from Dale Farnsworth to support OHCI implementations that use big-endian byte sex for registers ... all register accesses changed, that's why it's so large. (It also includes part of an update from his third patch, so that it compiles/runs by itself.) This patch adds support to the OHCI code for big-endian controllers, maintaining the existing little-endian support. This is done using the following transforms: ohci_readl(p) --> ohci_readl(ohci, p) writel(v, p) --> ohci_writel(ohci, v, p) cpu_to_le16(v) --> cpu_to_hc16(ohci, v) cpu_to_le16p(v) --> cpu_to_hc16p(ohci, v) cpu_to_le32(v) --> cpu_to_hc32(ohci, v) cpu_to_le32p(v) --> cpu_to_hc32p(ohci, v) le16_to_cpu(v) --> hc16_to_cpu(ohci, v) le16_to_cpup(v) --> hc16_to_cpup(ohci, v) le32_to_cpu(v) --> hc32_to_cpu(ohci, v) le32_to_cpup(v) --> hc32_to_cpup(ohci, v) OHCI_FRAME_NO(ohci->hcca) --> ohci_frame_no(ohci) There's no runtime penalty except for systems configured to handle both byteorders at the same time. Signed-off-by: Dale Farnsworth <dale@farnsworth.org> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
David Brownell authored
This is the first of several patches from Dale Farnsworth, laying groundwork for a patch that supports OHCI on more chips (IBM STB04xxx and FreeScale MPC52xx). Replace pre-byteswapped constants for in-memory data structures in ohci.h with cpu-native constants, to help support "big-endian OHCI" hardware. Signed-off-by: Dale Farnsworth <dale@farnsworth.org> Signed-off-by: David Brownell <dbrownell@users.sourceforge.net> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Herbert Xu authored
Collaborative work between David S. Miller and Herbert Xu. Signed-off-by: Herbert Xu <herbert@gondor.apana.org.au> Signed-off-by: David S. Miller <davem@davemloft.net>
-
Alan Stern authored
On Fri, 29 Oct 2004, David Brownell wrote: > Could you add a comment there that the HCD is > now _required_ to return a pointer that usbcore > can pass to kfree? Since that's a layering > violation (in anticipation of later changes to > make it not be one!), it's surprising ... and > in any case, the memory lifecycle is no longer > described just by the calls in this header! That's a reasonable request, and here's an extra patch to add the comment. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-
Alan Stern authored
This patch removes the hcd release code from the final host controller driver, dummy-hcd. Please apply. Signed-off-by: Alan Stern <stern@rowland.harvard.edu> Signed-off-by: Greg Kroah-Hartman <greg@kroah.com>
-