[PATCH 3.18 38/93] ALSA: pcm: Use dma_bytes as size parameter in dma_mmap_coherent()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Roese commit 9066ae7ff5d89c0b5daa271e2d573540097a94fa upstream. When trying to use the driver (e.g. aplay *.wav), the 4MiB DMA buffer will get mmapp'ed in 16KiB chunks.

[PATCH 3.18 38/93] ALSA: pcm: Use dma_bytes as size parameter in dma_mmap_coherent()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Stefan Roese commit 9066ae7ff5d89c0b5daa271e2d573540097a94fa upstream. When trying to use the driver (e.g. aplay *.wav), the 4MiB DMA buffer will get mmapp'ed in 16KiB chunks. But this fails

[PATCH 3.18 40/93] perf/hwbp: Simplify the perf-hwbp code, fix documentation

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit f67b15037a7a50c57f72e69a6d59941ad90a0f0f upstream. Annoyingly, modify_user_hw_breakpoint() unnecessarily complicates the modification of a

[PATCH 3.18 40/93] perf/hwbp: Simplify the perf-hwbp code, fix documentation

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit f67b15037a7a50c57f72e69a6d59941ad90a0f0f upstream. Annoyingly, modify_user_hw_breakpoint() unnecessarily complicates the modification of a breakpoint - simplify it and

[PATCH 3.18 39/93] ALSA: pcm: potential uninitialized return values

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 5607dddbfca774fb38bffadcb077fe03aa4ac5c6 upstream. Smatch complains that "tmp" can be uninitialized if we do a zero size write. Fixes:

[PATCH 3.18 39/93] ALSA: pcm: potential uninitialized return values

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 5607dddbfca774fb38bffadcb077fe03aa4ac5c6 upstream. Smatch complains that "tmp" can be uninitialized if we do a zero size write. Fixes: 02a5d6925cd3 ("ALSA: pcm: Avoid

[PATCH 3.18 15/93] staging: ncpfs: memory corruption in ncp_read_kernel()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 4c41aa24baa4ed338241d05494f2c595c885af8f upstream. If the server is malicious then *bytes_read could be larger than the size of the "target"

[PATCH 3.18 15/93] staging: ncpfs: memory corruption in ncp_read_kernel()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Dan Carpenter commit 4c41aa24baa4ed338241d05494f2c595c885af8f upstream. If the server is malicious then *bytes_read could be larger than the size of the "target" buffer. It would lead to

[PATCH 3.18 43/93] usb: gadget: change len to size_t on alloc_ep_req()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Felipe F. Tonello commit 69bb99738b5c6d56d2b1a75db9cbb4d187453c1a upstream. Length of buffers should be of type size_t whenever possible. Altough recommended, this

[PATCH 3.18 43/93] usb: gadget: change len to size_t on alloc_ep_req()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Felipe F. Tonello commit 69bb99738b5c6d56d2b1a75db9cbb4d187453c1a upstream. Length of buffers should be of type size_t whenever possible. Altough recommended, this change has no real

[PATCH 3.18 45/93] usb: gadget: align buffer size when allocating for OUT endpoint

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Felipe F. Tonello commit e0466156ee2e944fb47a3fa00932c3698a6d2c67 upstream. Using usb_ep_align() makes sure that the buffer size for OUT endpoints is always aligned

[PATCH 3.18 45/93] usb: gadget: align buffer size when allocating for OUT endpoint

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Felipe F. Tonello commit e0466156ee2e944fb47a3fa00932c3698a6d2c67 upstream. Using usb_ep_align() makes sure that the buffer size for OUT endpoints is always aligned with wMaxPacketSize (512

[PATCH 3.18 44/93] usb: gadget: fix usb_ep_align_maybe endianness and new usb_ep_align

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Felipe F. Tonello commit 16b114a6d7973cf027e4c2b23eae1076eaf98c25 upstream. USB spec specifies wMaxPacketSize to be little endian (as other properties), so when using

[PATCH 3.18 44/93] usb: gadget: fix usb_ep_align_maybe endianness and new usb_ep_align

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Felipe F. Tonello commit 16b114a6d7973cf027e4c2b23eae1076eaf98c25 upstream. USB spec specifies wMaxPacketSize to be little endian (as other properties), so when using this variable in the

[PATCH 3.18 16/93] can: cc770: Fix stalls on rt-linux, remove redundant IRQ ack

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andri Yngvason commit f4353daf4905c0099fd25fa742e2ffd4a4bab26a upstream. This has been reported to cause stalls on rt-linux. Suggested-by: Richard Weinberger

[PATCH 3.18 16/93] can: cc770: Fix stalls on rt-linux, remove redundant IRQ ack

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andri Yngvason commit f4353daf4905c0099fd25fa742e2ffd4a4bab26a upstream. This has been reported to cause stalls on rt-linux. Suggested-by: Richard Weinberger Tested-by: Richard Weinberger

[PATCH 3.18 18/93] can: cc770: Fix use after free in cc770_tx_interrupt()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andri Yngvason commit 9ffd7503944ec7c0ef41c3245d1306c221aef2be upstream. This fixes use after free introduced by the last cc770 patch. Signed-off-by: Andri Yngvason

[PATCH 3.18 18/93] can: cc770: Fix use after free in cc770_tx_interrupt()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Andri Yngvason commit 9ffd7503944ec7c0ef41c3245d1306c221aef2be upstream. This fixes use after free introduced by the last cc770 patch. Signed-off-by: Andri Yngvason Fixes: 746201235b3f

[PATCH 3.18 20/93] kvm/x86: fix icebp instruction handling

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 32d43cd391bacb5f0814c2624399a5dad3501d09 upstream. The undocumented 'icebp' instruction (aka 'int1') works pretty much like 'int3' in the

[PATCH 3.18 20/93] kvm/x86: fix icebp instruction handling

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit 32d43cd391bacb5f0814c2624399a5dad3501d09 upstream. The undocumented 'icebp' instruction (aka 'int1') works pretty much like 'int3' in the absense of in-circuit probing

Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850

My boot issue happens right after the BIOS when the initrd should be loaded and then no grub (v2.0) menu appears. It seems I could fix it for me disabling Host Notify + Interrupts with options i2c_i801 disable_features=0x30 and then rebuilding initrd. The touchpad is still working. Still testing

Re: [PATCH v2] i2c: i801: blacklist Host Notify on HP EliteBook G3 850

My boot issue happens right after the BIOS when the initrd should be loaded and then no grub (v2.0) menu appears. It seems I could fix it for me disabling Host Notify + Interrupts with options i2c_i801 disable_features=0x30 and then rebuilding initrd. The touchpad is still working. Still testing

[PATCH 3.18 19/93] tty: vt: fix up tabstops properly

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit f1869a890cdedb92a3fab969db5d0fd982850273 upstream. Tabs on a console with long lines do not wrap properly, so correctly account for the

[PATCH 3.18 19/93] tty: vt: fix up tabstops properly

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Linus Torvalds commit f1869a890cdedb92a3fab969db5d0fd982850273 upstream. Tabs on a console with long lines do not wrap properly, so correctly account for the line length when computing the

[PATCH 3.18 12/93] drm: udl: Properly check framebuffer mmap offsets

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit 3b82a4db8eaccce735dffd50b4d4e1578099b8e8 upstream. The memmap options sent to the udl framebuffer driver were not being checked for all

[PATCH 3.18 12/93] drm: udl: Properly check framebuffer mmap offsets

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman commit 3b82a4db8eaccce735dffd50b4d4e1578099b8e8 upstream. The memmap options sent to the udl framebuffer driver were not being checked for all sets of possible crazy

[PATCH 3.18 21/93] scsi: sg: dont return bogus Sg_requests

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn commit 48ae8484e9fc324b4968d33c585e54bc98e44d61 upstream. If the list search in sg_get_rq_mark() fails to find a valid request, we return a bogus

[PATCH 3.18 21/93] scsi: sg: dont return bogus Sg_requests

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johannes Thumshirn commit 48ae8484e9fc324b4968d33c585e54bc98e44d61 upstream. If the list search in sg_get_rq_mark() fails to find a valid request, we return a bogus element. This then can

Re: [PATCH] dts: remove cris & metag dts hard link file

On Fri, Apr 6, 2018 at 3:14 PM, Liu, Changcheng wrote: > arch cris & metag have been removed from supported archs. > The dts hard link files should also be removed, or the ctags > tool will give warning. > > execute"ctags -R", output: > ctags: Warning: cannot open source

Re: [PATCH] dts: remove cris & metag dts hard link file

On Fri, Apr 6, 2018 at 3:14 PM, Liu, Changcheng wrote: > arch cris & metag have been removed from supported archs. > The dts hard link files should also be removed, or the ctags > tool will give warning. > > execute"ctags -R", output: > ctags: Warning: cannot open source file >

[PATCH 3.18 47/93] Revert "led: core: Fix brightness setting when setting delay_off=0"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings This reverts commit 20f6d9c2af33da892a0e03ffd6249c7ab81edfb7, which was commit 2b83ff96f51d0b039c4561b9f95c824d7bddb85c upstream. The bug that it

[PATCH 3.18 47/93] Revert "led: core: Fix brightness setting when setting delay_off=0"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings This reverts commit 20f6d9c2af33da892a0e03ffd6249c7ab81edfb7, which was commit 2b83ff96f51d0b039c4561b9f95c824d7bddb85c upstream. The bug that it should fix was only introduced

[PATCH 3.18 56/93] scsi: virtio_scsi: always read VPD pages for multiqueue too

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit a680f1d463aeaeb00d22af257a56e111967c2f18 upstream. Multi-queue virtio-scsi uses a different scsi_host_template struct. Add the .device_alloc field

[PATCH 3.18 56/93] scsi: virtio_scsi: always read VPD pages for multiqueue too

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Paolo Bonzini commit a680f1d463aeaeb00d22af257a56e111967c2f18 upstream. Multi-queue virtio-scsi uses a different scsi_host_template struct. Add the .device_alloc field there, too. Fixes:

[PATCH 3.18 58/93] [media] vb2: V4L2_BUF_FLAG_DONE is set after DQBUF

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Ribalda commit 3171cc2b4eb9831ab4df1d80d0410a945b8bc84e upstream. According to the doc, V4L2_BUF_FLAG_DONE is cleared after DQBUF: V4L2_BUF_FLAG_DONE

[PATCH 3.18 58/93] [media] vb2: V4L2_BUF_FLAG_DONE is set after DQBUF

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Ribalda commit 3171cc2b4eb9831ab4df1d80d0410a945b8bc84e upstream. According to the doc, V4L2_BUF_FLAG_DONE is cleared after DQBUF: V4L2_BUF_FLAG_DONE 0x0004 ... After calling

[PATCH 3.18 59/93] media: v4l2-compat-ioctl32.c: add missing VIDIOC_PREPARE_BUF

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 3ee6d040719ae09110e5cdf24d5386abe5d1b776 upstream. The result of the VIDIOC_PREPARE_BUF ioctl was never copied back to userspace since it was

[PATCH 3.18 59/93] media: v4l2-compat-ioctl32.c: add missing VIDIOC_PREPARE_BUF

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 3ee6d040719ae09110e5cdf24d5386abe5d1b776 upstream. The result of the VIDIOC_PREPARE_BUF ioctl was never copied back to userspace since it was missing in the switch.

Re: [PATCH] mm-vmscan-dont-mess-with-pgdat-flags-in-memcg-reclaim-v2-fix

On Fri, Apr 6, 2018 at 8:09 AM, Andrey Ryabinin wrote: > > > On 04/06/2018 05:37 PM, Shakeel Butt wrote: > >>> >>> @@ -2482,7 +2494,7 @@ static inline bool should_continue_reclaim(struct >>> pglist_data *pgdat, >>> static bool pgdat_memcg_congested(pg_data_t *pgdat,

Re: [PATCH] mm-vmscan-dont-mess-with-pgdat-flags-in-memcg-reclaim-v2-fix

On Fri, Apr 6, 2018 at 8:09 AM, Andrey Ryabinin wrote: > > > On 04/06/2018 05:37 PM, Shakeel Butt wrote: > >>> >>> @@ -2482,7 +2494,7 @@ static inline bool should_continue_reclaim(struct >>> pglist_data *pgdat, >>> static bool pgdat_memcg_congested(pg_data_t *pgdat, struct mem_cgroup >>>

[PATCH 3.18 62/93] media: v4l2-compat-ioctl32.c: avoid sizeof(type)

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 333b1e9f96ce05f7498b581509bb30cde03018bf upstream. Instead of doing sizeof(struct foo) use sizeof(*up). There even were cases where 4 *

[PATCH 3.18 62/93] media: v4l2-compat-ioctl32.c: avoid sizeof(type)

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 333b1e9f96ce05f7498b581509bb30cde03018bf upstream. Instead of doing sizeof(struct foo) use sizeof(*up). There even were cases where 4 * sizeof(__u32) was used instead of

[PATCH 3.18 61/93] media: v4l2-compat-ioctl32.c: move helper functions to __get/put_v4l2_format32

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 486c521510c44a04cd756a9267e7d1e271c8a4ba upstream. These helper functions do not really help. Move the code to the __get/put_v4l2_format32

[PATCH 3.18 63/93] media: v4l2-compat-ioctl32.c: copy m.userptr in put_v4l2_plane32

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 8ed5a59dcb47a6f76034ee760b36e089f3e82529 upstream. The struct v4l2_plane32 should set m.userptr as well. The same happens in v4l2_buffer32 and

[PATCH 3.18 61/93] media: v4l2-compat-ioctl32.c: move helper functions to __get/put_v4l2_format32

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 486c521510c44a04cd756a9267e7d1e271c8a4ba upstream. These helper functions do not really help. Move the code to the __get/put_v4l2_format32 functions. Signed-off-by: Hans

[PATCH 3.18 63/93] media: v4l2-compat-ioctl32.c: copy m.userptr in put_v4l2_plane32

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 8ed5a59dcb47a6f76034ee760b36e089f3e82529 upstream. The struct v4l2_plane32 should set m.userptr as well. The same happens in v4l2_buffer32 and v4l2-compliance tests for

[PATCH 3.18 64/93] media: v4l2-compat-ioctl32.c: fix ctrl_is_pointer

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit b8c601e8af2d08f733d74defa8465303391bb930 upstream. ctrl_is_pointer just hardcoded two known string controls, but that caused problems when using

[PATCH 3.18 64/93] media: v4l2-compat-ioctl32.c: fix ctrl_is_pointer

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit b8c601e8af2d08f733d74defa8465303391bb930 upstream. ctrl_is_pointer just hardcoded two known string controls, but that caused problems when using e.g. custom controls that

[PATCH 3.18 65/93] media: v4l2-compat-ioctl32.c: make ctrl_is_pointer work for subdevs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 273caa260035c03d89ad63d72d8cd3d9e5c5e3f1 upstream. If the device is of type VFL_TYPE_SUBDEV then vdev->ioctl_ops is NULL so the 'if

[PATCH 3.18 65/93] media: v4l2-compat-ioctl32.c: make ctrl_is_pointer work for subdevs

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil commit 273caa260035c03d89ad63d72d8cd3d9e5c5e3f1 upstream. If the device is of type VFL_TYPE_SUBDEV then vdev->ioctl_ops is NULL so the 'if (!ops->vidioc_query_ext_ctrl)' check

[PATCH 3.18 66/93] media: v4l2-compat-ioctl32: Copy v4l2_window->global_alpha

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Mentz commit 025a26fa14f8fd55d50ab284a30c016a5be953d0 upstream. Commit b2787845fb91 ("V4L/DVB (5289): Add support for video output overlays.") added the field

[PATCH 3.18 66/93] media: v4l2-compat-ioctl32: Copy v4l2_window->global_alpha

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Mentz commit 025a26fa14f8fd55d50ab284a30c016a5be953d0 upstream. Commit b2787845fb91 ("V4L/DVB (5289): Add support for video output overlays.") added the field global_alpha to struct

[PATCH 3.18 48/93] xhci: Fix ring leak in failure path of xhci_alloc_virt_device()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings This is a stable-only fix for the backport of commit 5d9b70f7d52e ("xhci: Don't add a virt_dev to the devs array before it's fully allocated"). In

[PATCH 3.18 48/93] xhci: Fix ring leak in failure path of xhci_alloc_virt_device()

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ben Hutchings This is a stable-only fix for the backport of commit 5d9b70f7d52e ("xhci: Don't add a virt_dev to the devs array before it's fully allocated"). In branches that predate commit

[PATCH 3.18 70/93] media: v4l2-compat-ioctl32.c: refactor compat ioctl32 logic

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Mentz commit a1dfb4c48cc1e64eeb7800a27c66a6f7e88d075a upstream. The 32-bit compat v4l2 ioctl handling is implemented based on its 64-bit equivalent. It converts

[PATCH 3.18 70/93] media: v4l2-compat-ioctl32.c: refactor compat ioctl32 logic

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Mentz commit a1dfb4c48cc1e64eeb7800a27c66a6f7e88d075a upstream. The 32-bit compat v4l2 ioctl handling is implemented based on its 64-bit equivalent. It converts 32-bit data structures

Re: [PATCH 2/3] iio:dac:ad5686: Add AD5672R/AD5676/AD5676R/AD5684R/AD5685R/AD5686R support

On Fri, 30 Mar 2018 16:55:18 +0300 Stefan Popa wrote: > The AD5684R/AD5685R/AD5686R are a family of 4 channel DACs with 12-bit, > 14-bit and 16-bit precision respectively. The devices come either with a > built-in reference or no built-in reference. > > The

Re: [PATCH 2/3] iio:dac:ad5686: Add AD5672R/AD5676/AD5676R/AD5684R/AD5685R/AD5686R support

On Fri, 30 Mar 2018 16:55:18 +0300 Stefan Popa wrote: > The AD5684R/AD5685R/AD5686R are a family of 4 channel DACs with 12-bit, > 14-bit and 16-bit precision respectively. The devices come either with a > built-in reference or no built-in reference. > > The AD5672R/AD5676/AD5676R are similar,

[PATCH 3.18 72/93] media: media/v4l2-ctrls: volatiles should not generate CH_VALUE

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Ribalda Volatile controls should not generate CH_VALUE events. Set has_changed to false to prevent this happening. Signed-off-by: Ricardo Ribalda Delgado

[PATCH 3.18 72/93] media: media/v4l2-ctrls: volatiles should not generate CH_VALUE

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Ricardo Ribalda Volatile controls should not generate CH_VALUE events. Set has_changed to false to prevent this happening. Signed-off-by: Ricardo Ribalda Delgado Signed-off-by: Hans Verkuil

[PATCH 3.18 73/93] media: v4l2-compat-ioctl32: use compat_u64 for video standard

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab Instead of using the "v4l2_std_id" typedef, use compat_u64, as otherwise it fails to properly handle some ioctls. Signed-off-by: Mauro Carvalho

[PATCH 3.18 73/93] media: v4l2-compat-ioctl32: use compat_u64 for video standard

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Mauro Carvalho Chehab Instead of using the "v4l2_std_id" typedef, use compat_u64, as otherwise it fails to properly handle some ioctls. Signed-off-by: Mauro Carvalho Chehab Signed-off-by:

[PATCH 3.18 71/93] media: v4l2-ctrls: fix sparse warning

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil The warning is simple: drivers/media/v4l2-core/v4l2-ctrls.c:1685:15: warning: incorrect type in assignment (different address spaces) but the fix isn't.

[PATCH 3.18 71/93] media: v4l2-ctrls: fix sparse warning

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Hans Verkuil The warning is simple: drivers/media/v4l2-core/v4l2-ctrls.c:1685:15: warning: incorrect type in assignment (different address spaces) but the fix isn't. The core problem was

[PATCH 3.18 49/93] kprobes/x86: Fix to set RWX bits correctly before releasing trampoline

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit c93f5cf571e7795f97d49ef51b766cf25e328545 upstream. Fix kprobes to set(recover) RWX bits correctly on trampoline buffer before releasing it.

[PATCH 3.18 49/93] kprobes/x86: Fix to set RWX bits correctly before releasing trampoline

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Masami Hiramatsu commit c93f5cf571e7795f97d49ef51b766cf25e328545 upstream. Fix kprobes to set(recover) RWX bits correctly on trampoline buffer before releasing it. Releasing readonly page to

[PATCH 3.18 75/93] USB: serial: ftdi_sio: add RT Systems VX-8 cable

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Major Hayden commit 9608e5c0f079390473b484ef92334dfd3431bb89 upstream. This patch adds a device ID for the RT Systems cable used to program Yaesu VX-8R/VX-8DR handheld radios.

[PATCH 3.18 75/93] USB: serial: ftdi_sio: add RT Systems VX-8 cable

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Major Hayden commit 9608e5c0f079390473b484ef92334dfd3431bb89 upstream. This patch adds a device ID for the RT Systems cable used to program Yaesu VX-8R/VX-8DR handheld radios. It uses the

Re: [PATCH 1/7] arm64: dts: renesas: r8a77970: add FCPVD support

Hi Jacopo, Thank you for the patch. On Friday, 6 April 2018 16:08:06 EEST Jacopo Mondi wrote: > From: Sergei Shtylyov > > Describe FCPVD0 in the R8A77970 device tree; it will be used by VSPD0 in > the next patch... > > Based on the original (and large)

Re: [PATCH 1/7] arm64: dts: renesas: r8a77970: add FCPVD support

Hi Jacopo, Thank you for the patch. On Friday, 6 April 2018 16:08:06 EEST Jacopo Mondi wrote: > From: Sergei Shtylyov > > Describe FCPVD0 in the R8A77970 device tree; it will be used by VSPD0 in > the next patch... > > Based on the original (and large) patch by Daisuke Matsushita > . > >

[PATCH 3.18 77/93] USB: serial: cp210x: add ELDAT Easywave RX09 id

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 1f1e82f74c0947e40144688c9e36abe4b3999f49 upstream. Add device id for ELDAT Easywave RX09 tranceiver. Reported-by: Jan Jansen Cc:

[PATCH 3.18 77/93] USB: serial: cp210x: add ELDAT Easywave RX09 id

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 1f1e82f74c0947e40144688c9e36abe4b3999f49 upstream. Add device id for ELDAT Easywave RX09 tranceiver. Reported-by: Jan Jansen Cc: stable Signed-off-by: Johan Hovold

[PATCH 3.18 50/93] xfrm_user: uncoditionally validate esn replay attribute struct

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit d97ca5d714a5334aecadadf696875da40f1fbf3e upstream. The sanity test added in ecd7918745234 can be bypassed, validation only occurs if XFRM_STATE_ESN

[PATCH 3.18 50/93] xfrm_user: uncoditionally validate esn replay attribute struct

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit d97ca5d714a5334aecadadf696875da40f1fbf3e upstream. The sanity test added in ecd7918745234 can be bypassed, validation only occurs if XFRM_STATE_ESN flag is set, but

[PATCH 3.18 78/93] mei: remove dev_err message on an unsupported ioctl

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit bb0829a741792b56c908d7745bc0b2b540293bcc upstream. Currently the driver spams the kernel log on unsupported ioctls which is unnecessary as the

[PATCH 3.18 78/93] mei: remove dev_err message on an unsupported ioctl

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Colin Ian King commit bb0829a741792b56c908d7745bc0b2b540293bcc upstream. Currently the driver spams the kernel log on unsupported ioctls which is unnecessary as the ioctl returns -ENOIOCTLCMD

[PATCH 3.18 80/93] parport_pc: Add support for WCH CH382L PCI-E single parallel port card.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Gerasiov commit 823f7923833c6cc2b16e601546d607dcfb368004 upstream. WCH CH382L is a PCI-E adapter with 1 parallel port. It is similair to CH382 but serial ports are

[PATCH 3.18 80/93] parport_pc: Add support for WCH CH382L PCI-E single parallel port card.

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Alexander Gerasiov commit 823f7923833c6cc2b16e601546d607dcfb368004 upstream. WCH CH382L is a PCI-E adapter with 1 parallel port. It is similair to CH382 but serial ports are not soldered on

[PATCH 3.18 52/93] xfrm: Refuse to insert 32 bit userspace socket policies on 64 bit systems

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert commit 19d7df69fdb2636856dc8919de72fc1bf8f79598 upstream. We don't have a compat layer for xfrm, so userspace and kernel structures have

[PATCH 3.18 52/93] xfrm: Refuse to insert 32 bit userspace socket policies on 64 bit systems

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Steffen Klassert commit 19d7df69fdb2636856dc8919de72fc1bf8f79598 upstream. We don't have a compat layer for xfrm, so userspace and kernel structures have different sizes in this case. This

[PATCH 3.18 53/93] netfilter: bridge: ebt_among: add more missing match size checks

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit c8d70a700a5b486bfa8e5a7d33d805389f6e59f9 upstream. ebt_among is special, it has a dynamic match size and is exempt from the central size checks.

[PATCH 3.18 53/93] netfilter: bridge: ebt_among: add more missing match size checks

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Florian Westphal commit c8d70a700a5b486bfa8e5a7d33d805389f6e59f9 upstream. ebt_among is special, it has a dynamic match size and is exempt from the central size checks. commit c4585a2823edf

[PATCH 3.18 55/93] Bluetooth: Fix missing encryption refresh on Security Request

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Szymon Janc commit 64e759f58f128730b97a3c3a26d283c075ad7c86 upstream. If Security Request is received on connection that is already encrypted with sufficient security

[PATCH 3.18 55/93] Bluetooth: Fix missing encryption refresh on Security Request

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Szymon Janc commit 64e759f58f128730b97a3c3a26d283c075ad7c86 upstream. If Security Request is received on connection that is already encrypted with sufficient security master should perform

Re: [PATCH v3] net: thunderx: rework mac addresses list to u64 array

Self-NACK here, because of https://lkml.org/lkml/2018/4/6/724 Sorry for noise. Vadim On Fri, Apr 06, 2018 at 07:04:43AM -0700, Vadim Lomovtsev wrote: > From: Vadim Lomovtsev > > It is too expensive to pass u64 values via linked list, instead > allocate array for

Re: [PATCH v3] net: thunderx: rework mac addresses list to u64 array

Self-NACK here, because of https://lkml.org/lkml/2018/4/6/724 Sorry for noise. Vadim On Fri, Apr 06, 2018 at 07:04:43AM -0700, Vadim Lomovtsev wrote: > From: Vadim Lomovtsev > > It is too expensive to pass u64 values via linked list, instead > allocate array for them by overall number of mac

[PATCH 3.18 82/93] crypto: x86/cast5-avx - fix ECB encryption when long sg follows short one

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 8f461b1e02ed546fbd0f11611138da67fd85a30f upstream. With ecb-cast5-avx, if a 128+ byte scatterlist element followed a shorter one, then the algorithm

[PATCH 3.18 82/93] crypto: x86/cast5-avx - fix ECB encryption when long sg follows short one

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Eric Biggers commit 8f461b1e02ed546fbd0f11611138da67fd85a30f upstream. With ecb-cast5-avx, if a 128+ byte scatterlist element followed a shorter one, then the algorithm accidentally

[PATCH 3.18 92/93] Revert "ARM: dts: omap3-n900: Fix the audio CODECs reset pin"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit 9d8df5594467b6c73c3833b462abe5811fe7295b which was commit 7be4b5dc7ffa9499ac6ef33a5ffa9ff43f9b7057 upstream. It requires a

[PATCH 3.18 92/93] Revert "ARM: dts: omap3-n900: Fix the audio CODECs reset pin"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit 9d8df5594467b6c73c3833b462abe5811fe7295b which was commit 7be4b5dc7ffa9499ac6ef33a5ffa9ff43f9b7057 upstream. It requires a driver that was not merged

[PATCH v7 [RESEND] 2/2] dt-bindings: introduce Command DB for QCOM SoCs

From: Mahesh Sivasubramanian Command DB provides information on shared resources like clocks, regulators etc., probed at boot by the remote subsytem and made available in shared memory. Cc: devicet...@vger.kernel.org Signed-off-by: Mahesh Sivasubramanian

[PATCH v7 [RESEND] 2/2] dt-bindings: introduce Command DB for QCOM SoCs

From: Mahesh Sivasubramanian Command DB provides information on shared resources like clocks, regulators etc., probed at boot by the remote subsytem and made available in shared memory. Cc: devicet...@vger.kernel.org Signed-off-by: Mahesh Sivasubramanian Signed-off-by: Lina Iyer Reviewed-by:

Re: [PATCH v2] net: thunderx: rework mac addresses list to u64 array

On Fri, Apr 06, 2018 at 11:06:03AM -0400, David Miller wrote: > From: Vadim Lomovtsev > Date: Fri, 6 Apr 2018 04:14:25 -0700 > > > diff --git a/drivers/net/ethernet/cavium/thunder/nic.h > > b/drivers/net/ethernet/cavium/thunder/nic.h > > index

Re: [PATCH v2] net: thunderx: rework mac addresses list to u64 array

On Fri, Apr 06, 2018 at 11:06:03AM -0400, David Miller wrote: > From: Vadim Lomovtsev > Date: Fri, 6 Apr 2018 04:14:25 -0700 > > > diff --git a/drivers/net/ethernet/cavium/thunder/nic.h > > b/drivers/net/ethernet/cavium/thunder/nic.h > > index 5fc46c5a4f36..448d1fafc827 100644 > > ---

[PATCH v7 [RESEND] 1/2] drivers: qcom: add command DB driver

From: Mahesh Sivasubramanian Command DB is a simple database in the shared memory of QCOM SoCs, that provides information regarding shared resources. Some shared resources in the SoC have properties that are probed dynamically at boot by the remote processor. The

[PATCH v7 [RESEND] 1/2] drivers: qcom: add command DB driver

From: Mahesh Sivasubramanian Command DB is a simple database in the shared memory of QCOM SoCs, that provides information regarding shared resources. Some shared resources in the SoC have properties that are probed dynamically at boot by the remote processor. The information pertaining to the

[PATCH 3.18 91/93] Revert "PCI/MSI: Stop disabling MSI/MSI-X in pci_device_shutdown()"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit 058645e2f0647c85f2bfd51546d198739fd2 which was commit fda78d7a0ead144f4b2cdb582dcba47911f4952c upstream. The dependancy

[PATCH 3.18 91/93] Revert "PCI/MSI: Stop disabling MSI/MSI-X in pci_device_shutdown()"

3.18-stable review patch. If anyone has any objections, please let me know. -- From: Greg Kroah-Hartman This reverts commit 058645e2f0647c85f2bfd51546d198739fd2 which was commit fda78d7a0ead144f4b2cdb582dcba47911f4952c upstream. The dependancy tree is just too messy here,

[PATCH v7 [RESEND] 0/2] drivers/qcom: add Command DB support

Resending with minor rephrase of 'reg' property description. Changes since v6: - Fix 'reg' property - Add reviewed-by tags Changes since v5: - Remove indirection of command db start address - Rebase on top of 4.16 Changes since v4: - Address comments from

[PATCH v7 [RESEND] 0/2] drivers/qcom: add Command DB support

Resending with minor rephrase of 'reg' property description. Changes since v6: - Fix 'reg' property - Add reviewed-by tags Changes since v5: - Remove indirection of command db start address - Rebase on top of 4.16 Changes since v4: - Address comments from

<    3   4   5   6   7   8   9   10   11   12   >