search for: fget_light

...ignal+245/432] __dequeue_signal+0xf5/0x1b0 [dequeue_signal+53/160] dequeue_signal+0x35/0xa0 [get_signal_to_deliver+599/848] get_signal_to_deliver+0x257/0x350 [do_signal+103/288] do_signal+0x67/0x120 [dnotify_parent+58/176] dnotify_parent+0x3a/0xb0 [vfs_read+210/304] vfs_read+0xd2/0x130 [fget_light+130/144] fget_light+0x82/0x90 [sys_read+126/128] sys_read+0x7e/0x80 [do_notify_resume+55/60] do_notify_resume+0x37/0x3c [work_notifysig+19/24] work_notifysig+0x13/0x18 scheduling while atomic [schedule+1682/1696] schedule+0x692/0x6a0 [wake_up_state+24/32] wake_up_state+0x18/0x20 [wait_...

...do_sync_write+0x9c/0xd0 > Jan 6 20:06:23 eser kernel: [19365.563014] [<c02d6b15>] ? > rw_verify_area+0x65/0x100 > Jan 6 20:06:23 eser kernel: [19365.563014] [<c02d6e7a>] ? > vfs_write+0x9a/0x160 > Jan 6 20:06:23 eser kernel: [19365.563014] [<c02d8211>] ? > fget_light+0x91/0xb0 > Jan 6 20:06:23 eser kernel: [19365.563014] [<c02d6690>] ? > do_sync_write+0x0/0xd0 > Jan 6 20:06:23 eser kernel: [19365.563014] [<c02d714d>] ? sys_write+0x3d/0x70 > Jan 6 20:06:23 eser kernel: [19365.563014] [<c0202e18>] ? > sysenter_do_call+0x12/0...

...5] [<ffffffff81121996>] do_sync_write+0xcb/0x108 [ 1998.478275] [<ffffffff810f33a4>] ? might_fault+0x5c/0xac [ 1998.478275] [<ffffffff8107ed01>] ? lock_is_held+0x8d/0x98 [ 1998.478275] [<ffffffff8112200f>] vfs_write+0xaf/0x102 [ 1998.478275] [<ffffffff8112347e>] ? fget_light+0x3a/0xa1 [ 1998.478275] [<ffffffff81122222>] sys_write+0x4d/0x74 [ 1998.478275] [<ffffffff8146fec2>] system_call_fastpath+0x16/0x1b [ 2160.937580] INFO: task xfs_io:22734 blocked for more than 120 seconds. [ 2160.953899] "echo 0 > /proc/sys/kernel/hung_task_timeout_secs&quot...

Hi Ian, Today i fired up an old VM with a bittorrent client, trying to download some torrents. I seem to be hitting the unlikely case of "xennet: skb rides the rocket: xx slots" and this results in some dropped packets in domU, I don''t see any warnings in dom0. I have added some extra info, but i don''t have enough knowledge if this could/should be prevented from

https://bugs.freedesktop.org/show_bug.cgi?id=34430 Summary: nouveau driver does not return VGA connector status breaking upower Product: xorg Version: unspecified Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau

...t;ffffffff81094fd7>] ? mark_held_locks+0x52/0x70 [ 2417.747542] [<ffffffff810faaaa>] ? kmem_cache_free+0xb6/0x195 [ 2417.747545] [<ffffffff8110c51d>] vfs_ioctl+0x2d/0xa1 [ 2417.747548] [<ffffffff8110ca69>] do_vfs_ioctl+0x454/0x48d [ 2417.747551] [<ffffffff810ff4db>] ? fget_light+0xd6/0x289 [ 2417.747554] [<ffffffff8110cae4>] sys_ioctl+0x42/0x65 [ 2417.747557] [<ffffffff8102fdab>] system_call_fastpath+0x16/0x1b Deadlock scenario looks like this: CPU1 CPU2 nouveau code calls some drm_mm.c function which takes mm->unuse...

An user reported that he has hit an annoying deadlock while playing with ceph based on btrfs. Current updating device tree requires space from METADATA chunk, so we -may- need to do a recursive chunk allocation when adding/updating dev extent, that is where the deadlock comes from. If we use SYSTEM metadata to update device tree, we can avoid the recursive stuff. Reported-by: Jim Schutt

...l_chain+0x16/0x20 [<ffffffff81263196>] fb_blank+0x36/0xc0 [<ffffffff81263fa7>] do_fb_ioctl+0x2f7/0x5f0 [<ffffffff810e8d1a>] ? mmap_region+0x1aa/0x620 [<ffffffff812646e1>] fb_ioctl+0x41/0x50 [<ffffffff811209d7>] do_vfs_ioctl+0x97/0x580 [<ffffffff8112c49a>] ? fget_light+0x3da/0x4d0 [<ffffffff8155ad7b>] ? sysret_check+0x1b/0x56 [<ffffffff81120f0b>] sys_ioctl+0x4b/0x90 [<ffffffff8122c03e>] ? trace_hardirqs_on_thunk+0x3a/0x3f [<ffffffff8155ad56>] system_call_fastpath+0x1a/0x1f [drm] Enabling RC6 states: RC6 on, RC6p on, RC6pp off --- [2]...

Hello, I've been consistently attempting to make the setup mentioned in the subject work on the following hardware: Xeon E3 1275 (v1, Sandy Bridge) Asus P8B WS (Firmware: 0904 and 2009) 16 GB RAM Sapphire Radeon HD 7950 OC (Firmware: 015.013.000.010.000705) Linux 3.4.1 dom0, x86-64, pvops. Xen 4.1.2 (+ security patch) and 4.1.3-rc1. Old qemu-dm setup. (not new mainline qemu) Windows 7 64-bit

http://bugs.freedesktop.org/show_bug.cgi?id=26521 Summary: Bug in kernel module - ttm_bo_pci_offset Product: xorg Version: 7.4 Platform: x86-64 (AMD64) OS/Version: Linux (All) Status: NEW Severity: normal Priority: medium Component: Driver/nouveau AssignedTo: nouveau at lists.freedesktop.org

(The list appears to have eaten my previous attempt to send this. Apologies if you receive multiple copies.) The attached patches allow you to use paravirtualised network and block interfaces from fully virtualised domains, based on Intel''s patches from a few months ago. These are significantly faster than the equivalent ioemu devices, sometimes by more than an order of magnitude.

Hello, This patch series adds an initial implementation of restriper (it''s a clever name for relocation framework that allows to do selective profile changing and selective balancing with some goodies like pausing/resuming and reporting progress to the user. Profile changing is global (per-FS) so far, per-subvolume profiles require some discussion and can be implemented in future.