search for: sysfs_add_one

On 11/04/2013 07:10 AM, Fengguang Wu wrote: > Hi Jens, > > I'm not very sure about this bisect, but anyway it'd be good to inform > you of a possible problem on commit > > commit 3a02db083a78c9f3c9b69305ab513f9422d91b08 > Author: Jens Axboe <axboe at kernel.dk> > Date: Fri May 24 20:22:33 2013 +0200 > > virtio_blk: blk-mq support > >

Hi Jens, On Mon, Nov 04, 2013 at 03:58:41PM -0700, Jens Axboe wrote: > On 11/04/2013 07:10 AM, Fengguang Wu wrote: > > Hi Jens, > > > > I'm not very sure about this bisect, but anyway it'd be good to inform > > you of a possible problem on commit > > > > commit 3a02db083a78c9f3c9b69305ab513f9422d91b08 > > Author: Jens Axboe <axboe at

Hi Jens, On Mon, Nov 04, 2013 at 03:58:41PM -0700, Jens Axboe wrote: > On 11/04/2013 07:10 AM, Fengguang Wu wrote: > > Hi Jens, > > > > I'm not very sure about this bisect, but anyway it'd be good to inform > > you of a possible problem on commit > > > > commit 3a02db083a78c9f3c9b69305ab513f9422d91b08 > > Author: Jens Axboe <axboe at

...s the unplugged one This resulted in hot-plug being unsuccessful, as a port with the same name already exists (even though it was unplugged). This behaviour resulted in a warning message like this one: -------------------8<--------------------------------------- WARNING: at fs/sysfs/dir.c:512 sysfs_add_one+0xc9/0x130() (Not tainted) Hardware name: KVM sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:04.0/virtio0/virtio-ports/vport0p1' Call Trace: [<ffffffff8106b607>] ? warn_slowpath_common+0x87/0xc0 [<ffffffff8106b6f6>] ? warn_slowpath_fmt+0x46/0x50 [<ff...

...s the unplugged one This resulted in hot-plug being unsuccessful, as a port with the same name already exists (even though it was unplugged). This behaviour resulted in a warning message like this one: -------------------8<--------------------------------------- WARNING: at fs/sysfs/dir.c:512 sysfs_add_one+0xc9/0x130() (Not tainted) Hardware name: KVM sysfs: cannot create duplicate filename '/devices/pci0000:00/0000:00:04.0/virtio0/virtio-ports/vport0p1' Call Trace: [<ffffffff8106b607>] ? warn_slowpath_common+0x87/0xc0 [<ffffffff8106b6f6>] ? warn_slowpath_fmt+0x46/0x50 [<ff...

...sulted in hot-plug being unsuccessful, as a port with the same > name already exists (even though it was unplugged). > > This behaviour resulted in a warning message like this one: > > -------------------8<--------------------------------------- > WARNING: at fs/sysfs/dir.c:512 sysfs_add_one+0xc9/0x130() (Not tainted) > Hardware name: KVM > sysfs: cannot create duplicate filename > '/devices/pci0000:00/0000:00:04.0/virtio0/virtio-ports/vport0p1' > > Call Trace: > [<ffffffff8106b607>] ? warn_slowpath_common+0x87/0xc0 > [<ffffffff8106b6f6>] ? wa...

...sulted in hot-plug being unsuccessful, as a port with the same > name already exists (even though it was unplugged). > > This behaviour resulted in a warning message like this one: > > -------------------8<--------------------------------------- > WARNING: at fs/sysfs/dir.c:512 sysfs_add_one+0xc9/0x130() (Not tainted) > Hardware name: KVM > sysfs: cannot create duplicate filename > '/devices/pci0000:00/0000:00:04.0/virtio0/virtio-ports/vport0p1' > > Call Trace: > [<ffffffff8106b607>] ? warn_slowpath_common+0x87/0xc0 > [<ffffffff8106b6f6>] ? wa...

Hello, This series fixes a few races with port unplug and the various file operations: read(), write(), close() and poll(). There still might be more races lurking, but testing this series looks good to at least solve the easily-triggerable ones. I've run the virtio-serial testsuite and a few open/close/unplug tests, and haven't seen any badness. I've marked these patches for

Hello, This series fixes a few races with port unplug and the various file operations: read(), write(), close() and poll(). There still might be more races lurking, but testing this series looks good to at least solve the easily-triggerable ones. I've run the virtio-serial testsuite and a few open/close/unplug tests, and haven't seen any badness. I've marked these patches for

...1 | | | page_allocation_failure:order:,mode | 2 | | | Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 3 | | | WARNING:CPU:PID:at_fs/sysfs/dir.c:sysfs_add_one() | 0 | 2 | | WARNING:CPU:PID:at_lib/kobject.c:kobject_add_internal() | 0 | 2 | | BUG:unable_to_handle_kernel_paging_request_at | 0 | 2...

...1 | | | page_allocation_failure:order:,mode | 2 | | | Kernel_panic-not_syncing:Out_of_memory_and_no_killable_processes | 3 | | | WARNING:CPU:PID:at_fs/sysfs/dir.c:sysfs_add_one() | 0 | 2 | | WARNING:CPU:PID:at_lib/kobject.c:kobject_add_internal() | 0 | 2 | | BUG:unable_to_handle_kernel_paging_request_at | 0 | 2...

Hello, This series fixes a few bugs and races with port unplug and the various file operations: read(), write() and close(). I started coding up an alternative locking mechanism based on the discussion earlier in this series, but some of what we already have has to remain, and the new code is sufficiently different, so I'd rather it bakes for a while, and I ensure there are no regressions

Hello, This series fixes a few bugs and races with port unplug and the various file operations: read(), write() and close(). I started coding up an alternative locking mechanism based on the discussion earlier in this series, but some of what we already have has to remain, and the new code is sufficiently different, so I'd rather it bakes for a while, and I ensure there are no regressions

...86/boot/bzImage /boot/vmlinux-2.6.32 # egrep "MEGARAID" .config CONFIG_MEGARAID_NEWGEN=y CONFIG_MEGARAID_MM=y CONFIG_MEGARAID_MAILBOX=y # CONFIG_MEGARAID_LEGACY is not set # CONFIG_MEGARAID_SAS is not set After reboot receive the following error message (part): do_page_fault sysfs_add_one error_code+0x66 setup_IO_APIC_irq_extra 2. so i add acpi=off (test #6) (this workaround works on laptop) kernel /boot/xen-4.gz dom0_mem=384000 console=vga acpi=off module /boot/vmlinux-2.6.32 root=/dev/sda3 ro console=tty0 -> received errormessage: megaraid Couldn''t r...

Hello, This series fixes a few bugs and races with port unplug and the various file operations: read(), write(), close() and poll(). There still might be more races lurking, but testing this series looks good to at least solve the easily-triggerable ones. I've run the virtio-serial testsuite and a few open/close/unplug tests, and haven't seen any badness. I've marked these patches

Hello, This series fixes a few bugs and races with port unplug and the various file operations: read(), write(), close() and poll(). There still might be more races lurking, but testing this series looks good to at least solve the easily-triggerable ones. I've run the virtio-serial testsuite and a few open/close/unplug tests, and haven't seen any badness. I've marked these patches

Hello, I''m currently trying to understand some problems I had in the past with mixing look-back with blktap(2) for HV and PV domains. I''m stuck reading the source code, so I''d like to get some help from the list. Interrupt me if I got something fundamentally wrong in my understanding so far: 1. With pure-HV the domU gets an emulated IDE (or whatever) disk. The

...<ffffffff811e2342>] ? proc_mkdir_mode+0x42/0x60 May 20 19:30:51 wildfire kernel: [<ffffffff811e2376>] ? proc_mkdir+0x16/0x20 May 20 19:30:51 wildfire kernel: [<ffffffffa0043d03>] ? acpi_video_bus_add+0x239/0xff2 [video] May 20 19:30:51 wildfire kernel: [<ffffffff811ed96c>] ? sysfs_add_one+0x2c/0x130 May 20 19:30:51 wildfire kernel: [<ffffffff811ede98>] ? sysfs_do_create_link+0xd8/0x170 May 20 19:30:51 wildfire kernel: [<ffffffff812c8c8c>] ? acpi_device_probe+0x50/0x122 May 20 19:30:51 wildfire kernel: [<ffffffff81346b70>] ? driver_probe_device+0xa0/0x2a0 May 20 19:...

Greetings, I got the below dmesg and the first bad commit is commit cf39c8e5352b4fb9efedfe7e9acb566a85ed847c Merge: 3398d25 23b7eaf Author: Linus Torvalds <torvalds@linux-foundation.org> Date: Wed Sep 4 17:45:39 2013 -0700 Merge tag ''stable/for-linus-3.12-rc0-tag'' of git://git.kernel.org/pub/scm/linux/kernel/git/xen/tip Pull Xen updates from Konrad