search for: async_run_entry_fn

No problemos with x86_64, however on i686 kworker/u16:57: page allocation failure: order:0, mode:0x284000 CPU: 0 PID: 1425 Comm: kworker/u16:57 Not tainted 3.18.0-0.rc5.git0.1.fc22.i686+debug #1 Workqueue: events_unbound async_run_entry_fn Call Trace: [<c0b2b55a>] dump_stack+0x48/0x60 [<c056f3d4>] warn_alloc_failed+0xd4/0x110 [<c0571ade>] __alloc_pages_nodemask+0x81e/0xc30 [<c04e4b65>] ? clockevents_program_event+0x45/0x150 [<c05b81c8>] new_slab+0x258/0x3a0 [<c05b9490>] __slab_alloc.constprop...

...Without this patch: > > WARNING: CPU: 2 PID: 26 > at [..]/kernel/dma/mapping.c:251 > dma_alloc_attrs+0x8e/0xd0 Modules linked in: CPU: 2 PID: 26 Comm: > kworker/u6:1 Not tainted 5.1.0-rc3-00023-g1ec89ec #596 Hardware name: > IBM 2964 NC9 712 (KVM/Linux) Workqueue: events_unbound async_run_entry_fn > Krnl PSW : 0704c00180000000 000000000021b18e (dma_alloc_attrs+0x8e/0xd0) > R:0 T:1 IO:1 EX:1 Key:0 M:1 W:0 P:0 AS:3 CC:0 PM:0 RI:0 EA:3 > Krnl GPRS: 0000000000000000 0000000000000000 0000000000000000 > 0000000000001406 000003e00040f838 0000000000002dc0 0000000000000100 >...

...(E) scsi_dh_emc(E) scsi_dh_alua(E) scsi_mod(E) autofs4(E) > [ 321.473966] CPU: 1 PID: 4786 Comm: kworker/u8:17 Tainted: G W E 4.12.0.gccd5d1b-master #186 > [ 321.473968] Hardware name: MEDIONPC MS-7502/MS-7502, BIOS 6.00 PG 12/26/2007 > [ 321.473972] Workqueue: events_unbound async_run_entry_fn > [ 321.473974] task: ffff8801daf93d40 task.stack: ffffc90003edc000 > [ 321.473990] RIP: 0010:drm_calc_vbltimestamp_from_scanoutpos+0x14f/0x330 [drm] > [ 321.473992] RSP: 0018:ffffc90003edfb00 EFLAGS: 00010082 > [ 321.473994] RAX: ffffffffa03e6100 RBX: ffff880211140000 RCX: 00000000...

...ops_suspend at ffffffffa047e77d [nouveau] #21 [ffffc900039f7d50] pci_pm_suspend at ffffffff813b1ff0 #22 [ffffc900039f7d80] dpm_run_callback at ffffffff814c4dbd #23 [ffffc900039f7db8] __device_suspend at ffffffff814c5a61 #24 [ffffc900039f7e30] async_suspend at ffffffff814c5cfa #25 [ffffc900039f7e48] async_run_entry_fn at ffffffff81091683 #26 [ffffc900039f7e70] process_one_work at ffffffff810882bc #27 [ffffc900039f7eb0] worker_thread at ffffffff8108854a #28 [ffffc900039f7f10] kthread at ffffffff8108e387 #29 [ffffc900039f7f50] ret_from_fork at ffffffff8168fa85 crash> gdb list *drm_calc_vbltimestamp_from_scanout...

...E) scsi_dh_rdac(E) scsi_dh_emc(E) scsi_dh_alua(E) scsi_mod(E) autofs4(E) [ 321.473966] CPU: 1 PID: 4786 Comm: kworker/u8:17 Tainted: G W E 4.12.0.gccd5d1b-master #186 [ 321.473968] Hardware name: MEDIONPC MS-7502/MS-7502, BIOS 6.00 PG 12/26/2007 [ 321.473972] Workqueue: events_unbound async_run_entry_fn [ 321.473974] task: ffff8801daf93d40 task.stack: ffffc90003edc000 [ 321.473990] RIP: 0010:drm_calc_vbltimestamp_from_scanoutpos+0x14f/0x330 [drm] [ 321.473992] RSP: 0018:ffffc90003edfb00 EFLAGS: 00010082 [ 321.473994] RAX: ffffffffa03e6100 RBX: ffff880211140000 RCX: 0000000000000001 [ 321.4739...

...47e77d [nouveau] > #21 [ffffc900039f7d50] pci_pm_suspend at ffffffff813b1ff0 > #22 [ffffc900039f7d80] dpm_run_callback at ffffffff814c4dbd > #23 [ffffc900039f7db8] __device_suspend at ffffffff814c5a61 > #24 [ffffc900039f7e30] async_suspend at ffffffff814c5cfa > #25 [ffffc900039f7e48] async_run_entry_fn at ffffffff81091683 > #26 [ffffc900039f7e70] process_one_work at ffffffff810882bc > #27 [ffffc900039f7eb0] worker_thread at ffffffff8108854a > #28 [ffffc900039f7f10] kthread at ffffffff8108e387 > #29 [ffffc900039f7f50] ret_from_fork at ffffffff8168fa85 > crash> gdb list *drm_calc_...

...[<ffffffff814c86b1>] register_framebuffer+0x251/0x330 [ 18.984160] [<ffffffff8158fa9f>] drm_fb_helper_initial_config+0x25f/0x3f0 [ 18.984199] [<ffffffffa0106b48>] intel_fbdev_initial_config+0x18/0x30 [i915] [ 18.984201] [<ffffffff810adfd8>] async_run_entry_fn+0x48/0x150 [ 18.984203] [<ffffffff810a3947>] process_one_work+0x1e7/0x750 [ 18.984205] [<ffffffff810a3efb>] worker_thread+0x4b/0x4f0 [ 18.984207] [<ffffffff810aad4f>] kthread+0xef/0x110 [ 18.984208] [<ffffffff819a85ef>] ret_from_fork+0x1f/...

https://bugs.freedesktop.org/show_bug.cgi?id=103689 Bug ID: 103689 Summary: there is an exploitable page fault that can be reliably triggered from the chromium sandbox can possibly lead to remote attackers causing a denial of service condition or possibly running system code. Product: xorg

...b1>] register_framebuffer+0x251/0x330 >> [ 18.984160] [<ffffffff8158fa9f>] drm_fb_helper_initial_config+0x25f/0x3f0 >> [ 18.984199] [<ffffffffa0106b48>] intel_fbdev_initial_config+0x18/0x30 [i915] >> [ 18.984201] [<ffffffff810adfd8>] async_run_entry_fn+0x48/0x150 >> [ 18.984203] [<ffffffff810a3947>] process_one_work+0x1e7/0x750 >> [ 18.984205] [<ffffffff810a3efb>] worker_thread+0x4b/0x4f0 >> [ 18.984207] [<ffffffff810aad4f>] kthread+0xef/0x110 >> [ 18.984208] [<fffff...

...ffffff814c86b1>] register_framebuffer+0x251/0x330 > [ 18.984160] [<ffffffff8158fa9f>] drm_fb_helper_initial_config+0x25f/0x3f0 > [ 18.984199] [<ffffffffa0106b48>] intel_fbdev_initial_config+0x18/0x30 [i915] > [ 18.984201] [<ffffffff810adfd8>] async_run_entry_fn+0x48/0x150 > [ 18.984203] [<ffffffff810a3947>] process_one_work+0x1e7/0x750 > [ 18.984205] [<ffffffff810a3efb>] worker_thread+0x4b/0x4f0 > [ 18.984207] [<ffffffff810aad4f>] kthread+0xef/0x110 > [ 18.984208] [<ffffffff819a85ef>]...

...r_framebuffer+0x251/0x330 > >> [ 18.984160] [<ffffffff8158fa9f>] drm_fb_helper_initial_config+0x25f/0x3f0 > >> [ 18.984199] [<ffffffffa0106b48>] intel_fbdev_initial_config+0x18/0x30 [i915] > >> [ 18.984201] [<ffffffff810adfd8>] async_run_entry_fn+0x48/0x150 > >> [ 18.984203] [<ffffffff810a3947>] process_one_work+0x1e7/0x750 > >> [ 18.984205] [<ffffffff810a3efb>] worker_thread+0x4b/0x4f0 > >> [ 18.984207] [<ffffffff810aad4f>] kthread+0xef/0x110 > >> [ 18.98420...

This patch series aims to move the logical block size checking to the block code. This was inspired by missing check for valid logical block size in virtio-blk which causes the kernel to crash in a weird way later on when it is invalid. I added blk_is_valid_logical_block_size which returns true iff the block size is one of supported sizes. I added this check to virtio-blk, and also converted

This patch series aims to move the logical block size checking to the block code. This was inspired by missing check for valid logical block size in virtio-blk which causes the kernel to crash in a weird way later on when it is invalid. I added blk_is_valid_logical_block_size which returns true iff the block size is one of supported sizes. I added this check to virtio-blk, and also converted