Bug 1325447 - Snapshot merge may block further dm usage
Summary: Snapshot merge may block further dm usage
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: kernel
Version: rawhide
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mike Snitzer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-08 20:40 UTC by Zdenek Kabelac
Modified: 2016-05-10 09:22 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-05-06 19:32:12 UTC
Type: Bug


Attachments (Terms of Use)
process list with frozen 'ptraced' udev (552.99 KB, text/plain)
2016-05-10 09:22 UTC, Zdenek Kabelac
no flags Details

Description Zdenek Kabelac 2016-04-08 20:40:12 UTC
Description of problem:

lvm2 test suite test case  tests/shell/snapshot-merge.sh  can cause hang of dm subsystem.

Known info -  when hang occures - these are 2 dm interacting running tasks:

systemd-udevd   D ffff8800362ab888     0  9634    475 0x00000004
 ffff8800362ab888 00ffffffffffffff ffff880075428000 ffff88007543d7c0
 ffff8800362ac000 ffffffff00000000 ffff880073104c00 ffff880073104c18
 fffffffe00000001 ffff8800362ab8a0 ffffffff817d1985 ffff88007543d7c0
Call Trace:
 [<ffffffff817d1985>] schedule+0x35/0x80
 [<ffffffff817d453b>] rwsem_down_write_failed+0x1fb/0x320
 [<ffffffff811bcb3d>] ? mempool_alloc_slab+0x1d/0x30
 [<ffffffff813ebaf7>] call_rwsem_down_write_failed+0x17/0x30
 [<ffffffff817d3c3d>] down_write+0x2d/0x40
 [<ffffffff8165c29c>] snapshot_map+0x5c/0x3f0
 [<ffffffff81649f3d>] __map_bio+0x3d/0x110
 [<ffffffff8164bc69>] __split_and_process_bio+0x289/0x400
 [<ffffffff8164be49>] dm_make_request+0x69/0xc0
 [<ffffffff813ad724>] generic_make_request+0xf4/0x1d0
 [<ffffffff813ad876>] submit_bio+0x76/0x160
 [<ffffffff811cbd5a>] ? lru_cache_add+0x3a/0x80
 [<ffffffff8128c570>] mpage_readpages+0x1a0/0x1f0
 [<ffffffff812851e0>] ? I_BDEV+0x20/0x20
 [<ffffffff812851e0>] ? I_BDEV+0x20/0x20
 [<ffffffff812174ac>] ? alloc_pages_current+0x8c/0x110
 [<ffffffff81285c0d>] blkdev_readpages+0x1d/0x20
 [<ffffffff811c972b>] __do_page_cache_readahead+0x1cb/0x2a0
 [<ffffffff811c9b8a>] force_page_cache_readahead+0xaa/0x100
 [<ffffffff811c9c1f>] page_cache_sync_readahead+0x3f/0x50
 [<ffffffff811bb7fd>] generic_file_read_iter+0x64d/0x930
 [<ffffffff81286045>] blkdev_read_iter+0x35/0x40
 [<ffffffff81248e4b>] __vfs_read+0xcb/0x110
 [<ffffffff81249de6>] vfs_read+0x86/0x130
 [<ffffffff8124b2d5>] SyS_read+0x55/0xc0
 [<ffffffff817d59f2>] entry_SYSCALL_64_fastpath+0x1a/0xa4

lvm             D ffff880075d0faf0     0  9672   9651 0x00000000
 ffff880075d0faf0 0000000000000000 ffff880077110000 ffff880075c29d40
 ffff880075d10000 ffff88007a5b0f70 ffff880075d0fb88 ffffffff817d2170
 ffff880075d0fb70 ffff880075d0fb08 ffffffff817d1985 0000000000000002
Call Trace:
 [<ffffffff817d2170>] ? out_of_line_wait_on_atomic_t+0xf0/0xf0
 [<ffffffff817d1985>] schedule+0x35/0x80
 [<ffffffff817d2181>] bit_wait+0x11/0x60
 [<ffffffff817d1d7b>] __wait_on_bit+0x5b/0x90
 [<ffffffff817d2170>] ? out_of_line_wait_on_atomic_t+0xf0/0xf0
 [<ffffffff817d1e32>] out_of_line_wait_on_bit+0x82/0xb0
 [<ffffffff810eb580>] ? wake_atomic_t_function+0x60/0x60
 [<ffffffff8165aed4>] stop_merge+0x44/0x60
 [<ffffffff8165af02>] snapshot_merge_presuspend+0x12/0x20
 [<ffffffff81650107>] dm_table_presuspend_targets+0x47/0x60
 [<ffffffff8164b42e>] __dm_suspend+0xbe/0x1e0
 [<ffffffff811b93d0>] ? find_lock_entry+0x30/0xe0
 [<ffffffff81652680>] ? table_load+0x350/0x350
 [<ffffffff8164d752>] dm_suspend+0xc2/0xe0
 [<ffffffff8165280a>] dev_suspend+0x18a/0x240
 [<ffffffff81653076>] ctl_ioctl+0x226/0x4e0
 [<ffffffff81653343>] dm_ctl_ioctl+0x13/0x20
 [<ffffffff8125e0a3>] do_vfs_ioctl+0xa3/0x5d0
 [<ffffffff8124c901>] ? __sb_end_write+0x21/0x30
 [<ffffffff81249fdc>] ? vfs_write+0x14c/0x190
 [<ffffffff8125e649>] SyS_ioctl+0x79/0x90
 [<ffffffff817d59f2>] entry_SYSCALL_64_fastpath+0x1a/0xa4


trying to read dm status hangs -

# dmsetup  status
LVMTEST8858vg-LV1-real: 0 101376 linear 
LVMTEST8858vg-LV1_snap-cow: 0 19456 linear 
LVMTEST8858vg-LV1: 0 101376 snapshot-merge 904/19456 16
LVMTEST8858pv1: 0 204800 linear 
LVMTEST8858vg-LV1_snap: 0 101376 error

--

dmsetup         D ffff88001d98bad8     0  6605      1 0x00000004
 ffff88001d98bad8 0000000000000002 ffff880002acd7c0 ffff8800646b3a80
 ffff88001d98c000 ffffffff00000000 ffff880036c00e00 ffff880036c00e18
 fffffffe00000001 ffff88001d98baf0 ffffffff817d1985 ffff8800646b3a80
Call Trace:
 [<ffffffff817d1985>] schedule+0x35/0x80
 [<ffffffff817d453b>] rwsem_down_write_failed+0x1fb/0x320
 [<ffffffff811c3ca8>] ? __alloc_pages_nodemask+0x1b8/0xca0
 [<ffffffff813ebaf7>] call_rwsem_down_write_failed+0x17/0x30
 [<ffffffff817d3c3d>] down_write+0x2d/0x40
 [<ffffffff81659d14>] snapshot_status+0x84/0x1a0
 [<ffffffff81652211>] retrieve_status+0xa1/0x1c0
 [<ffffffff816533a0>] ? dm_get_live_or_inactive_table.isra.3+0x30/0x30
 [<ffffffff81653403>] table_status+0x63/0xa0
 [<ffffffff81653076>] ctl_ioctl+0x226/0x4e0
 [<ffffffff81653343>] dm_ctl_ioctl+0x13/0x20
 [<ffffffff8125e0a3>] do_vfs_ioctl+0xa3/0x5d0
 [<ffffffff81249fcc>] ? vfs_write+0x13c/0x190
 [<ffffffff8125e649>] SyS_ioctl+0x79/0x90
 [<ffffffff817d59f2>] entry_SYSCALL_64_fastpath+0x1a/0xa4

-- dmstate table state --
LVMTEST8858vg-LV1-real: 0 101376 linear 253:2 2048
LVMTEST8858vg-LV1_snap-cow: 0 19456 linear 253:2 103424
LVMTEST8858vg-LV1: 0 101376 snapshot-merge 253:4 253:5 P 8
LVMTEST8858pv1: 0 204800 linear 7:0 2048
LVMTEST8858vg-LV1_snap: 0 101376 error 
LVMTEST8858vg-LV1_snap_1: 0 101376 snapshot 253:4 253:7 P 8
LVMTEST8858vg-LV1_snap_1-cow: 0 21504 linear 253:2 122880

-- inactive preloaded tables --
LVMTEST8858vg-LV1: 0 101376 snapshot-origin 253:4
LVMTEST8858vg-LV1_snap: 0 19456 linear 253:2 103424

-- info -c --
LVMTEST8858vg-LV1-real       253   4 L--w    3    1      0 LVM-wi2PgVLOpgEf6dRaAWNjgq0WHcY28Z8XWxpKNhiAw8cBP4cXcbPsnBktUbZsl6vw-real
LVMTEST8858vg-LV1_snap-cow   253   5 L--w    1    1      0 LVM-wi2PgVLOpgEf6dRaAWNjgq0WHcY28Z8XQoTmM8Vvub6eTvmlE7vHXKHllJSJJI91-cow 
LVMTEST8858vg-LV1            253   3 LI-w    0    1      0 LVM-wi2PgVLOpgEf6dRaAWNjgq0WHcY28Z8XWxpKNhiAw8cBP4cXcbPsnBktUbZsl6vw     
LVMTEST8858pv1               253   2 L--w    5    1      0 TEST-LVMTEST8858pv1                                                      
LVMTEST8858vg-LV1_snap       253   6 LI-w    0    1      0 LVM-wi2PgVLOpgEf6dRaAWNjgq0WHcY28Z8XQoTmM8Vvub6eTvmlE7vHXKHllJSJJI91     
LVMTEST8858vg-LV1_snap_1     253   8 L--w    1    1      0 LVM-wi2PgVLOpgEf6dRaAWNjgq0WHcY28Z8XWalz5DrE6wnBcoTPpMMGbkTOVoDt3bYz     
LVMTEST8858vg-LV1_snap_1-cow 253   7 L--w    1    1      0 LVM-wi2PgVLOpgEf6dRaAWNjgq0WHcY28Z8XWalz5DrE6wnBcoTPpMMGbkTOVoDt3bYz-cow 


from the context the current estimation about what's going on -
the merge might be already finished?? and  lvm tried to change
table (replacing  snapshot-merge  -> snapshot-origin)
and  'snapshot' target being temporarily an error target is
scanned for reading by udev.

Possible related commit 385277bfb57faac44e92497104ba542cdd82d5fe
Should be probably retested with reverted commit ??
Further analysis needed.


Version-Release number of selected component (if applicable):
kernel 4.6.0-0.rc0.git17.2.fc25.x86_64

How reproducible:


Steps to Reproduce:
1. looping  'make check_local T=snapshot-merge.sh'  lvm2 test case
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Zdenek Kabelac 2016-04-09 10:04:41 UTC
Update:

Upgrading rawhide BB machine to kernel: 4.6.0-0.rc2.git3.2.fc25.x86_64
makes the test pass many iterations.
Rebooting with kernel 4.6.0-0.rc0.git17.2.fc25.x86_64 needs just at most few minutes to hit the issue.

So it could be possible the bug is now already fixed.
(Or the race is much harder to hit.)

Comment 2 Zdenek Kabelac 2016-04-09 10:09:53 UTC
Update 2:

It's always good idea to wait just one a few more minutes,
I guess 'send-button' was needed to trigger it ;)

So the race and block is still there with 4.6.0-0.rc2.git3.2.fc25.x86_64

The test case should be 'decrypted' so it's more easily testable...

Comment 3 Zdenek Kabelac 2016-04-15 14:45:09 UTC
So there was discovered a 'race' case in  suspend / resume case when snapshot-merge is going to be started.

This likely may have resulted in wrong routing of I/O in running dm targets.

So while the original problem in kernel likely is still there, the fixed
lvm2 logic for old snapshot merge code does seem to avoid hitting this race.

Related lvm2 commit:
https://www.redhat.com/archives/lvm-devel/2016-April/msg00058.html

Comment 4 Mike Snitzer 2016-05-06 19:19:40 UTC
I'm seeing a ton of these warnings but the test passes (with a very old lvm2 tree, head being commit 192a83de):

[ 4187.833562] ------------[ cut here ]------------
[ 4187.838727] WARNING: CPU: 6 PID: 5725 at lib/list_debug.c:36 __list_add+0x8a/0xc0
[ 4187.847104] list_add double add: new=ffff8803161efb68, prev=ffff8803191a8380, next=ffff8803161efb68.
[ 4187.857300] Modules linked in: ext4 jbd2 mbcache dm_snapshot(O) dm_bufio(O) loop iscsi_tcp libiscsi_tcp libiscsi scsi_transport_iscsi coretemp kvm_intel kvm irqbypass crct10dif_pclmul crc32_pclmul ghash_clmulni_intel iTCO_wdt iomemory_vsl(POE) aesni_intel iTCO_vendor_support i7core_edac sg glue_helper ipmi_si lrw gf128mul edac_core ablk_helper ipmi_msghandler i2c_i801 lpc_ich cryptd shpchp pcspkr acpi_power_meter mfd_core acpi_cpufreq ip_tables xfs libcrc32c sr_mod sd_mod cdrom mgag200 drm_kms_helper syscopyarea sysfillrect sysimgblt fb_sys_fops ttm ata_generic pata_acpi ixgbe igb ata_piix mdio drm ptp i2c_algo_bit libata megaraid_sas crc32c_intel pps_core i2c_core skd dca dm_mod
[ 4187.925340] CPU: 6 PID: 5725 Comm: lvm Tainted: P        W IOE   4.6.0-rc6.snitm+ #162
[ 4187.934176] Hardware name: FUJITSU                          PRIMERGY RX300 S6             /D2619, BIOS 6.00 Rev. 1.10.2619.N1           05/24/2011
[ 4187.948829]  0000000000000286 00000000ca7738aa ffff880311333b68 ffffffff8133020f
[ 4187.957119]  ffff880311333bb8 0000000000000000 ffff880311333ba8 ffffffff81080ba1
[ 4187.965412]  00000024b9c43820 ffff8803161efb68 ffff8803161efb68 ffff8803191a8380
[ 4187.973705] Call Trace:
[ 4187.976435]  [<ffffffff8133020f>] dump_stack+0x63/0x84
[ 4187.982170]  [<ffffffff81080ba1>] __warn+0xd1/0xf0
[ 4187.987515]  [<ffffffff81080c1f>] warn_slowpath_fmt+0x5f/0x80
[ 4187.993929]  [<ffffffff81242a30>] ? bdev_test+0x20/0x20
[ 4187.999760]  [<ffffffff8134c79a>] __list_add+0x8a/0xc0
[ 4188.005494]  [<ffffffff81243d18>] bd_acquire+0xc8/0xd0
[ 4188.011228]  [<ffffffff81244b99>] blkdev_open+0x39/0x70
[ 4188.017060]  [<ffffffff81205d97>] do_dentry_open+0x227/0x320
[ 4188.023375]  [<ffffffff81244b60>] ? blkdev_get_by_dev+0x50/0x50
[ 4188.029981]  [<ffffffff812071c7>] vfs_open+0x57/0x60
[ 4188.035521]  [<ffffffff81216b6a>] path_openat+0x1ba/0x1340
[ 4188.041641]  [<ffffffff81218113>] ? putname+0x53/0x60
[ 4188.047278]  [<ffffffff812185af>] ? filename_lookup+0xef/0x190
[ 4188.053786]  [<ffffffff81219161>] do_filp_open+0x91/0x100
[ 4188.059812]  [<ffffffff8122fce0>] ? simple_attr_release+0x20/0x20
[ 4188.066613]  [<ffffffff81226996>] ? __alloc_fd+0x46/0x180
[ 4188.072638]  [<ffffffff81207524>] do_sys_open+0x124/0x210
[ 4188.078665]  [<ffffffff81124c1b>] ? __audit_syscall_exit+0x1db/0x260
[ 4188.085756]  [<ffffffff8120762e>] SyS_open+0x1e/0x20
[ 4188.091297]  [<ffffffff81003c12>] do_syscall_64+0x62/0x110
[ 4188.097420]  [<ffffffff816955a1>] entry_SYSCALL64_slow_path+0x25/0x25
[ 4188.104617] ---[ end trace 2e19a3f81f712942 ]---

I'll retry with latest lvm2.

Comment 5 Mike Snitzer 2016-05-06 19:32:12 UTC
I checked out lvm2.git commit 6954de22e2281876506c0db1c98972242de977fb^ and successfully ran the test 30 times in a loop against linux-dm.git's 'dm-4.7' branch (which is based on 4.6-rc6) and cannot hit any hangs like were reported in comment#0.

Closing WORKSFORME, if this rears its ugly head again please reopen.

Comment 6 Alasdair Kergon 2016-05-06 20:07:48 UTC
(In reply to Mike Snitzer from comment #5)
> I checked out lvm2.git commit 6954de22e2281876506c0db1c98972242de977fb^ and
> successfully ran the test 30 times in a loop against linux-dm.git's 'dm-4.7'
> branch (which is based on 4.6-rc6) and cannot hit any hangs like were
> reported in comment#0.

Because we changed lvm2 to avoid this issue.

The question is whether a version prior to that fix still crashes with the latest kernels.

Comment 7 Alasdair Kergon 2016-05-06 20:10:13 UTC
(The summary in the lvm2 commit was in effect that the race has been narrowed substantially but not entirely eliminated.)

Comment 8 Mike Snitzer 2016-05-09 15:21:54 UTC
(In reply to Alasdair Kergon from comment #6)
> (In reply to Mike Snitzer from comment #5)
> > I checked out lvm2.git commit 6954de22e2281876506c0db1c98972242de977fb^ and
> > successfully ran the test 30 times in a loop against linux-dm.git's 'dm-4.7'
> > branch (which is based on 4.6-rc6) and cannot hit any hangs like were
> > reported in comment#0.
> 
> Because we changed lvm2 to avoid this issue.
> 
> The question is whether a version prior to that fix still crashes with the
> latest kernels.

I checked out and tested lvm2 that did _not_ have the fix.  The "^" at the end of the commit id means the commit just prior to 6954de22e2281876506c0db1c98972242de977fb (which is the commit comment#3 referred to).

Comment 9 Zdenek Kabelac 2016-05-10 09:22:10 UTC
So I've played for some time with this:

With 4.6-rc6 I'm not able to hit this issue:
The best I've seen were these 2 kernel messages:

device-mapper: snapshots: Cancelling snapshot handover.
device-mapper: snapshots: Snapshot is invalid: can't merge

----


With these kernels:

4.6.0-0.rc6.git2.1.fc25.x86_64+debug
4.6.0-0.rc4.git0.1.fc25.x86_64+debug 

I've not seen any 'lockdep' errors - but neither been able to trigger the fault as report originally.


However I've been able to hit weird  'ptrace' issue with non-debug 4.6.0-0.rc6.git2.1.

just running in the loop in one terminal:

lvcreate -s -n snap -l60%FREE $vg/$lv1
mkfs.ext3 "$DM_DEV_DIR/$vg/$lv1"
lvconvert --merge $vg/snap

and in other window:

strace -f -p pidof systemd-udevd


After some while - udev stopped responding and ptraced process was not recoverable.  This of course lead to non-respoding 'cookie' processing,
so lvm2 stopped - but there was not 'freeze' - since  'dmsetup udevcomplete_all' simply finished command processing.  Yet udevd remained 'dead'
(Full log attached in case someone fill see something more there)


 systemd-udevd   t ffff880074e1fd98     0   473      1 0x00000083
  ffff880074e1fd98 00ff880036e89ff8 ffff8800770e1d40 ffff8800749cba80
  ffff880074e20000 ffff8800749cba80 ffff8800749cba80 0000000000000000
  ffff8800749cba80 ffff880074e1fdb0 ffffffff817d93b5 ffff8800749cba80
 Call Trace:
  [<ffffffff817d93b5>] schedule+0x35/0x80
  [<ffffffff810b5517>] ptrace_stop+0x167/0x2a0
  [<ffffffff810b56e8>] ptrace_do_notify+0x98/0xc0
  [<ffffffff810b6b4b>] ptrace_notify+0x5b/0x80
  [<ffffffff81003a91>] syscall_trace_enter_phase2+0x81/0x1d0
  [<ffffffff81003c35>] syscall_trace_enter+0x55/0x60
  [<ffffffff81003e23>] do_syscall_64+0xf3/0x110
  [<ffffffff817dd521>] entry_SYSCALL64_slow_path+0x25/0x25
 dmsetup         t ffff88007518fd20     0 29100  29099 0x00000003
  ffff88007518fd20 00ff88007518fd40 ffff880074a18000 ffff8800367e8000
  ffff880075190000 ffff8800367e8000 ffff8800367e8000 0000000000000000
  ffff8800367e8000 ffff88007518fd38 ffffffff817d93b5 ffff8800367e8000
 Call Trace:
  [<ffffffff817d93b5>] schedule+0x35/0x80
  [<ffffffff810b5517>] ptrace_stop+0x167/0x2a0
  [<ffffffff810b56e8>] ptrace_do_notify+0x98/0xc0
  [<ffffffff810b6b4b>] ptrace_notify+0x5b/0x80
  [<ffffffff81003595>] tracehook_report_syscall_exit+0x45/0xd0
  [<ffffffff8124f044>] ? SYSC_newfstat+0x34/0x60
  [<ffffffff81003674>] syscall_slow_exit_work+0x54/0xd0
  [<ffffffff81003dfb>] do_syscall_64+0xcb/0x110
  [<ffffffff817dd521>] entry_SYSCALL64_slow_path+0x25/0x25
 dmsetup         t ffff88007565fd20     0 29101  29097 0x00000003
  ffff88007565fd20 00ff88007565fda0 ffff880074a18000 ffff880074b83a80
  ffff880075660000 ffff880074b83a80 ffff880074b83a80 0000000000000000
  ffff880074b83a80 ffff88007565fd38 ffffffff817d93b5 ffff880074b83a80
 Call Trace:
  [<ffffffff817d93b5>] schedule+0x35/0x80
  [<ffffffff810b5517>] ptrace_stop+0x167/0x2a0
  [<ffffffff810b56e8>] ptrace_do_notify+0x98/0xc0
  [<ffffffff810b6b4b>] ptrace_notify+0x5b/0x80
  [<ffffffff81003595>] tracehook_report_syscall_exit+0x45/0xd0
  [<ffffffff81267e6f>] ? __alloc_fd+0x3f/0x170
  [<ffffffff81259a24>] ? putname+0x54/0x60
  [<ffffffff81248635>] ? do_sys_open+0x1a5/0x220
  [<ffffffff81003674>] syscall_slow_exit_work+0x54/0xd0
  [<ffffffff81003dfb>] do_syscall_64+0xcb/0x110
  [<ffffffff817dd521>] entry_SYSCALL64_slow_path+0x25/0x25
 systemd-udevd   t ffff880075893d20     0 29102    473 0x00000003
  ffff880075893d20 00ff880075893d40 ffff880076a4ba80 ffff880074a18000
  ffff880075894000 ffff880074a18000 ffff880074a18000 0000000000000000
  ffff880074a18000 ffff880075893d38 ffffffff817d93b5 ffff880074a18000
 Call Trace:
  [<ffffffff817d93b5>] schedule+0x35/0x80
  [<ffffffff810b5517>] ptrace_stop+0x167/0x2a0
  [<ffffffff810b56e8>] ptrace_do_notify+0x98/0xc0
  [<ffffffff810b6b4b>] ptrace_notify+0x5b/0x80
  [<ffffffff81003595>] tracehook_report_syscall_exit+0x45/0xd0
  [<ffffffff8124bd5b>] ? alloc_file+0x1b/0xa0
  [<ffffffff81268013>] ? __fd_install+0x33/0xe0
  [<ffffffff81293bb9>] ? anon_inode_getfile+0xd9/0x160
  [<ffffffff81267e6f>] ? __alloc_fd+0x3f/0x170
  [<ffffffff81003674>] syscall_slow_exit_work+0x54/0xd0
  [<ffffffff81003dfb>] do_syscall_64+0xcb/0x110
  [<ffffffff817dd521>] entry_SYSCALL64_slow_path+0x25/0x25
 systemd-udevd   t ffff88006a633d20     0 29103  29102 0x00000003
  ffff88006a633d20 00ff88006a633d40 ffff880077110000 ffff880076a4ba80
  ffff88006a634000 ffff880076a4ba80 ffff880076a4ba80 0000000000000000
  ffff880076a4ba80 ffff88006a633d38 ffffffff817d93b5 ffff880076a4ba80
 Call Trace:
  [<ffffffff817d93b5>] schedule+0x35/0x80
  [<ffffffff810b5517>] ptrace_stop+0x167/0x2a0
  [<ffffffff810b56e8>] ptrace_do_notify+0x98/0xc0
  [<ffffffff810b6b4b>] ptrace_notify+0x5b/0x80
  [<ffffffff81003595>] tracehook_report_syscall_exit+0x45/0xd0
  [<ffffffff810b6b4b>] ? ptrace_notify+0x5b/0x80
  [<ffffffff812468a6>] ? filp_close+0x56/0x80
  [<ffffffff81003674>] syscall_slow_exit_work+0x54/0xd0
  [<ffffffff81003dfb>] do_syscall_64+0xcb/0x110
  [<ffffffff817dd521>] entry_SYSCALL64_slow_path+0x25/0x25

Comment 10 Zdenek Kabelac 2016-05-10 09:22:56 UTC
Created attachment 1155630 [details]
process list with frozen 'ptraced' udev


Note You need to log in before you can comment on or make changes to this bug.