Re: [REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

2017-12-11 Thread Willem de Bruijn
On Mon, Dec 11, 2017 at 4:44 PM, Greg Kroah-Hartman wrote: > On Mon, Dec 11, 2017 at 04:25:26PM -0500, Willem de Bruijn wrote: >> Note that UFO was removed in 4.14 and that skb_warn_bad_offload >> can happen for various types of packets, so there may be multiple >>

Re: [REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

2017-12-11 Thread Willem de Bruijn
On Mon, Dec 11, 2017 at 4:44 PM, Greg Kroah-Hartman wrote: > On Mon, Dec 11, 2017 at 04:25:26PM -0500, Willem de Bruijn wrote: >> Note that UFO was removed in 4.14 and that skb_warn_bad_offload >> can happen for various types of packets, so there may be multiple >> independent bug reports. I'm

Re: [PATCH] Documentation: Better document the hardlockup_panic sysctl

2017-12-11 Thread Jonathan Corbet
On Sun, 10 Dec 2017 01:48:46 -0600 Scott Wood wrote: > Commit ac1f591249d95372f ("kernel/watchdog.c: add sysctl knob > hardlockup_panic") added the hardlockup_panic sysctl, but did not add it > to Documentation/sysctl/kernel.txt. Add this, and reference it from the >

Re: [PATCH] Documentation: Better document the hardlockup_panic sysctl

2017-12-11 Thread Jonathan Corbet
On Sun, 10 Dec 2017 01:48:46 -0600 Scott Wood wrote: > Commit ac1f591249d95372f ("kernel/watchdog.c: add sysctl knob > hardlockup_panic") added the hardlockup_panic sysctl, but did not add it > to Documentation/sysctl/kernel.txt. Add this, and reference it from the > corresponding entry in

Re: [PATCH v4 72/73] xfs: Convert mru cache to XArray

2017-12-11 Thread Dave Chinner
On Sun, Dec 10, 2017 at 08:23:15PM -0800, Matthew Wilcox wrote: > On Mon, Dec 11, 2017 at 10:57:45AM +1100, Dave Chinner wrote: > > i.e. the fact the cmpxchg failed may not have anything to do with a > > race condtion - it failed because the slot wasn't empty like we > > expected it to be. There

Re: [PATCH v4 72/73] xfs: Convert mru cache to XArray

2017-12-11 Thread Dave Chinner
On Sun, Dec 10, 2017 at 08:23:15PM -0800, Matthew Wilcox wrote: > On Mon, Dec 11, 2017 at 10:57:45AM +1100, Dave Chinner wrote: > > i.e. the fact the cmpxchg failed may not have anything to do with a > > race condtion - it failed because the slot wasn't empty like we > > expected it to be. There

Re: [PATCH v5] leds: trigger: Introduce a NETDEV trigger

2017-12-11 Thread Jacek Anaszewski
Hi Ben, Thanks for the update. On 12/10/2017 10:17 PM, Ben Whitten wrote: > This commit introduces a NETDEV trigger for named device > activity. Available triggers are link, rx, and tx. > > Signed-off-by: Ben Whitten > > --- > Changes in v5: > Adjust header comment

Re: [PATCH v5] leds: trigger: Introduce a NETDEV trigger

2017-12-11 Thread Jacek Anaszewski
Hi Ben, Thanks for the update. On 12/10/2017 10:17 PM, Ben Whitten wrote: > This commit introduces a NETDEV trigger for named device > activity. Available triggers are link, rx, and tx. > > Signed-off-by: Ben Whitten > > --- > Changes in v5: > Adjust header comment style to be consistent >

Re: [PATCH 0/2] mux: add overview and add to driver-api docs

2017-12-11 Thread Jonathan Corbet
On Mon, 11 Dec 2017 09:29:41 +0100 Peter Rosin wrote: > Don't know if this is worth adding, but it might answer at least a few > questions. > > It looks ok when I view the htmldocs output, but I'm not all that certain > this is good to go? Almost, but I have one request: the

Re: [PATCH 0/2] mux: add overview and add to driver-api docs

2017-12-11 Thread Jonathan Corbet
On Mon, 11 Dec 2017 09:29:41 +0100 Peter Rosin wrote: > Don't know if this is worth adding, but it might answer at least a few > questions. > > It looks ok when I view the htmldocs output, but I'm not all that certain > this is good to go? Almost, but I have one request: the new mux.rst file

Re: [PATCH 1/4] fs/notify: fdinfo can report unsupported file handles.

2017-12-11 Thread NeilBrown
On Mon, Dec 11 2017, Amir Goldstein wrote: > On Mon, Dec 11, 2017 at 8:04 AM, NeilBrown wrote: >> If a filesystem does not set sb->s_export_op, then it >> does not support filehandles and export_fs_encode_fh() >> and exportfs_encode_inode_fh() should not be called. >> They will

Re: [PATCH 1/4] fs/notify: fdinfo can report unsupported file handles.

2017-12-11 Thread NeilBrown
On Mon, Dec 11 2017, Amir Goldstein wrote: > On Mon, Dec 11, 2017 at 8:04 AM, NeilBrown wrote: >> If a filesystem does not set sb->s_export_op, then it >> does not support filehandles and export_fs_encode_fh() >> and exportfs_encode_inode_fh() should not be called. >> They will use

Re: [GIT PULL] workqueue fixes for v4.15-rc1

2017-12-11 Thread Tejun Heo
Oops, $SUBJ should have been "workqueue fixes for v4.15-rc3", not rc1. Thanks. -- tejun

Re: [GIT PULL] workqueue fixes for v4.15-rc1

2017-12-11 Thread Tejun Heo
Oops, $SUBJ should have been "workqueue fixes for v4.15-rc3", not rc1. Thanks. -- tejun

[GIT PULL] libata fixes for v4.15-rc3

2017-12-11 Thread Tejun Heo
Hello, Linus. Nothing too interesting. David Milburn improved a corner case misbehavior during hotplug. Other than that, minor driver-specific fixes. Thanks. The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: Linux 4.15-rc1 (2017-11-26 16:01:47 -0800) are

[GIT PULL] libata fixes for v4.15-rc3

2017-12-11 Thread Tejun Heo
Hello, Linus. Nothing too interesting. David Milburn improved a corner case misbehavior during hotplug. Other than that, minor driver-specific fixes. Thanks. The following changes since commit 4fbd8d194f06c8a3fd2af1ce560ddb31f7ec8323: Linux 4.15-rc1 (2017-11-26 16:01:47 -0800) are

Re: [PATCH RESEND] KVM: X86: Fix load bad host fpu state

2017-12-11 Thread Wanpeng Li
2017-12-12 4:48 GMT+08:00 David Hildenbrand : > On 10.12.2017 22:44, Wanpeng Li wrote: >> From: Wanpeng Li >> >> [ cut here ] >> Bad FPU state detected at kvm_put_guest_fpu+0xd8/0x2d0 [kvm], >> reinitializing FPU registers. >>

Re: [PATCH RESEND] KVM: X86: Fix load bad host fpu state

2017-12-11 Thread Wanpeng Li
2017-12-12 4:48 GMT+08:00 David Hildenbrand : > On 10.12.2017 22:44, Wanpeng Li wrote: >> From: Wanpeng Li >> >> [ cut here ] >> Bad FPU state detected at kvm_put_guest_fpu+0xd8/0x2d0 [kvm], >> reinitializing FPU registers. >> WARNING: CPU: 1 PID: 4594 at

Re: [PATCH] Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops

2017-12-11 Thread John Stultz
On Thu, Nov 16, 2017 at 10:07 PM, Marcel Holtmann wrote: > Hi Lukas, > >> John Stultz reports a boot time crash with the HiKey board (which uses >> hci_serdev) occurring in hci_uart_tx_wakeup(). That function is >> contained in hci_ldisc.c, but also called from the newer

Re: [PATCH] Bluetooth: hci_serdev: Init hci_uart proto_lock to avoid oops

2017-12-11 Thread John Stultz
On Thu, Nov 16, 2017 at 10:07 PM, Marcel Holtmann wrote: > Hi Lukas, > >> John Stultz reports a boot time crash with the HiKey board (which uses >> hci_serdev) occurring in hci_uart_tx_wakeup(). That function is >> contained in hci_ldisc.c, but also called from the newer hci_serdev.c. >> It

[GIT PULL] workqueue fixes for v4.15-rc1

2017-12-11 Thread Tejun Heo
Hello, * Lai's hotplug simplifications inadvertently fix a possible deadlock involving cpuset and workqueue. * CPU isolation fix which was reverted due to the changes in the housekeeping code resurrected. * A trivial unused include removal. Thanks. The following changes since commit

[GIT PULL] workqueue fixes for v4.15-rc1

2017-12-11 Thread Tejun Heo
Hello, * Lai's hotplug simplifications inadvertently fix a possible deadlock involving cpuset and workqueue. * CPU isolation fix which was reverted due to the changes in the housekeeping code resurrected. * A trivial unused include removal. Thanks. The following changes since commit

[PATCH] phy: rockchip-typec: Try to turn the PHY on several times

2017-12-11 Thread Douglas Anderson
Bind / unbind stress testing of the USB controller on rk3399 found that we'd often end up with lots of failures that looked like this: phy phy-ff80.phy.9: phy poweron failed --> -110 dwc3 fe90.dwc3: failed to initialize core dwc3: probe of fe90.dwc3 failed with error -110 Those

[PATCH] phy: rockchip-typec: Try to turn the PHY on several times

2017-12-11 Thread Douglas Anderson
Bind / unbind stress testing of the USB controller on rk3399 found that we'd often end up with lots of failures that looked like this: phy phy-ff80.phy.9: phy poweron failed --> -110 dwc3 fe90.dwc3: failed to initialize core dwc3: probe of fe90.dwc3 failed with error -110 Those

Re: [PATCH v3] binder: fix proc->files use-after-free

2017-12-11 Thread Greg KH
On Mon, Dec 11, 2017 at 01:23:28PM -0800, Todd Kjos wrote: > Greg- when this is in, we'll want it in 4.14 as well. Ugh, missed that, I'll be sure to mark it for stable, thanks for letting me know. greg k-h

Re: [PATCH v3] binder: fix proc->files use-after-free

2017-12-11 Thread Greg KH
On Mon, Dec 11, 2017 at 01:23:28PM -0800, Todd Kjos wrote: > Greg- when this is in, we'll want it in 4.14 as well. Ugh, missed that, I'll be sure to mark it for stable, thanks for letting me know. greg k-h

Re: [REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

2017-12-11 Thread Greg Kroah-Hartman
On Mon, Dec 11, 2017 at 04:25:26PM -0500, Willem de Bruijn wrote: > Note that UFO was removed in 4.14 and that skb_warn_bad_offload > can happen for various types of packets, so there may be multiple > independent bug reports. I'm investigating two other non-UFO reports > just now. Meta-comment,

Re: [REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

2017-12-11 Thread Greg Kroah-Hartman
On Mon, Dec 11, 2017 at 04:25:26PM -0500, Willem de Bruijn wrote: > Note that UFO was removed in 4.14 and that skb_warn_bad_offload > can happen for various types of packets, so there may be multiple > independent bug reports. I'm investigating two other non-UFO reports > just now. Meta-comment,

Re: [PATCH v5] kernel: make groups_sort calling a responsibility group_info allocators

2017-12-11 Thread NeilBrown
On Mon, Dec 11 2017, Thiago Rafael Becker wrote: > In testing, we found that nfsd threads may call set_groups in parallel for > the same entry cached in auth.unix.gid, racing in the call of groups_sort, > corrupting the groups for that entry and leading to permission denials for > the client. > >

Re: [PATCH v5] kernel: make groups_sort calling a responsibility group_info allocators

2017-12-11 Thread NeilBrown
On Mon, Dec 11 2017, Thiago Rafael Becker wrote: > In testing, we found that nfsd threads may call set_groups in parallel for > the same entry cached in auth.unix.gid, racing in the call of groups_sort, > corrupting the groups for that entry and leading to permission denials for > the client. > >

Re: [PATCH v4 72/73] xfs: Convert mru cache to XArray

2017-12-11 Thread Dave Chinner
On Sat, Dec 09, 2017 at 09:00:18AM -0800, Joe Perches wrote: > On Sat, 2017-12-09 at 09:36 +1100, Dave Chinner wrote: > > 1. Using lockdep_set_novalidate_class() for anything other > > than device->mutex will throw checkpatch warnings. Nice. (*) > [] > > (*) checkpatch.pl is considered

Re: [PATCH v4 72/73] xfs: Convert mru cache to XArray

2017-12-11 Thread Dave Chinner
On Sat, Dec 09, 2017 at 09:00:18AM -0800, Joe Perches wrote: > On Sat, 2017-12-09 at 09:36 +1100, Dave Chinner wrote: > > 1. Using lockdep_set_novalidate_class() for anything other > > than device->mutex will throw checkpatch warnings. Nice. (*) > [] > > (*) checkpatch.pl is considered

Re: [PATCH] media: pxa_camera: disable and unprepare the clock source on error

2017-12-11 Thread Laurent Pinchart
Hi Flavio, On Monday, 11 December 2017 23:05:46 EET Flavio Ceolin wrote: > > On Wednesday, 6 December 2017 18:38:50 EET Flavio Ceolin wrote: > >> pxa_camera_probe() was not calling pxa_camera_deactivate(), > >> responsible to call clk_disable_unprepare(), on the failure path. This > >> was

Re: [PATCH] media: pxa_camera: disable and unprepare the clock source on error

2017-12-11 Thread Laurent Pinchart
Hi Flavio, On Monday, 11 December 2017 23:05:46 EET Flavio Ceolin wrote: > > On Wednesday, 6 December 2017 18:38:50 EET Flavio Ceolin wrote: > >> pxa_camera_probe() was not calling pxa_camera_deactivate(), > >> responsible to call clk_disable_unprepare(), on the failure path. This > >> was

Re: [PATCH] docs: refcount_t documentation

2017-12-11 Thread Jonathan Corbet
On Tue, 5 Dec 2017 12:46:35 +0200 Elena Reshetova wrote: > Some functions from refcount_t API provide different > memory ordering guarantees that their atomic counterparts. > This adds a document outlining these differences ( >

Re: [PATCH] docs: refcount_t documentation

2017-12-11 Thread Jonathan Corbet
On Tue, 5 Dec 2017 12:46:35 +0200 Elena Reshetova wrote: > Some functions from refcount_t API provide different > memory ordering guarantees that their atomic counterparts. > This adds a document outlining these differences ( > Documentation/core-api/refcount-vs-atomic.rst) as well as > some

Re: [PATCH v9 1/2] dt: bindings: lm3692x: Add bindings for lm3692x LED driver

2017-12-11 Thread Jacek Anaszewski
Dan, On 12/11/2017 07:26 PM, Dan Murphy wrote: > This adds the devicetree bindings for the LM3692x > I2C LED string driver. > > Acked-by: Pavel Machek > Signed-off-by: Dan Murphy > --- > > v9 - Moved 2 nodes to Optional Child and renamed node names to device type

Re: [PATCH v9 1/2] dt: bindings: lm3692x: Add bindings for lm3692x LED driver

2017-12-11 Thread Jacek Anaszewski
Dan, On 12/11/2017 07:26 PM, Dan Murphy wrote: > This adds the devicetree bindings for the LM3692x > I2C LED string driver. > > Acked-by: Pavel Machek > Signed-off-by: Dan Murphy > --- > > v9 - Moved 2 nodes to Optional Child and renamed node names to device type >

Re: [PATCH v4 5/5] ARM: ep93xx: ts72xx: Add support for BK3 board - ts72xx derivative

2017-12-11 Thread Lukasz Majewski
Hi Hartley, > On Thursday, November 30, 2017 4:52 PM, Lukasz Majewski wrote: > > > > The BK3 board is a derivative of the ts72xx reference design. > > Lukasz, > > I was just reviewing the other TS-72xx boards and noticed this: > > > > > +/* BK3 specific defines */ > > +#define

Re: [PATCH v4 5/5] ARM: ep93xx: ts72xx: Add support for BK3 board - ts72xx derivative

2017-12-11 Thread Lukasz Majewski
Hi Hartley, > On Thursday, November 30, 2017 4:52 PM, Lukasz Majewski wrote: > > > > The BK3 board is a derivative of the ts72xx reference design. > > Lukasz, > > I was just reviewing the other TS-72xx boards and noticed this: > > > > > +/* BK3 specific defines */ > > +#define

[PATCH v3 2/2] hwmon (pmbus): cffps: Add debugfs entries

2017-12-11 Thread Eddie James
From: "Edward A. James" Add debugfs entries for additional power supply data, including part number, serial number, FRU number, firmware revision, ccin, and the input history of the power supply. The input history is 10 minutes of input power data in the form of twenty

[PATCH v3 1/2] hwmon (pmbus): Export pmbus device debugfs directory entry

2017-12-11 Thread Eddie James
From: "Edward A. James" Pmbus client drivers, if they want to use debugfs, should use the same root directory as the pmbus debugfs entries are using. Therefore, export the device dentry for the pmbus client. Signed-off-by: Edward A. James ---

[PATCH v3 2/2] hwmon (pmbus): cffps: Add debugfs entries

2017-12-11 Thread Eddie James
From: "Edward A. James" Add debugfs entries for additional power supply data, including part number, serial number, FRU number, firmware revision, ccin, and the input history of the power supply. The input history is 10 minutes of input power data in the form of twenty 30-second packets. Each

[PATCH v3 1/2] hwmon (pmbus): Export pmbus device debugfs directory entry

2017-12-11 Thread Eddie James
From: "Edward A. James" Pmbus client drivers, if they want to use debugfs, should use the same root directory as the pmbus debugfs entries are using. Therefore, export the device dentry for the pmbus client. Signed-off-by: Edward A. James --- drivers/hwmon/pmbus/pmbus.h | 2 ++

[PATCH v3 0/2] hwmon (pmbus): cffps: Add debugfs entries

2017-12-11 Thread Eddie James
From: "Edward A. James" This series enables debugfs entries in the IBM common form factor power supply driver. In order to avoid multiple debugfs directories for the same driver, the first patch in the series allows a pmbus client driver to query pmbus core for it's debugfs

[PATCH v3 0/2] hwmon (pmbus): cffps: Add debugfs entries

2017-12-11 Thread Eddie James
From: "Edward A. James" This series enables debugfs entries in the IBM common form factor power supply driver. In order to avoid multiple debugfs directories for the same driver, the first patch in the series allows a pmbus client driver to query pmbus core for it's debugfs directory. The

Re: [REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

2017-12-11 Thread David Miller
From: Joseph Salisbury Date: Mon, 11 Dec 2017 15:35:34 -0500 > A kernel bug report was opened against Ubuntu [0].  It was found that > reverting the following commit resolved this bug: > > commit b2504a5dbef3305ef41988ad270b0e8ec289331c > Author: Eric Dumazet

Re: [REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

2017-12-11 Thread David Miller
From: Joseph Salisbury Date: Mon, 11 Dec 2017 15:35:34 -0500 > A kernel bug report was opened against Ubuntu [0].  It was found that > reverting the following commit resolved this bug: > > commit b2504a5dbef3305ef41988ad270b0e8ec289331c > Author: Eric Dumazet > Date:   Tue Jan 31 10:20:32 2017

[PATCH] arch: define weak abort

2017-12-11 Thread Sudip Mukherjee
gcc was generating abort due to 'divide by zero' and if it is not defined in the toolchain the build fails. Currently 'frv' and 'arc' are failing. Previously other arch was also broken like m32r was fixed by d22e3d69ee1a ("m32r: fix build failure"). Lets define this weak function which is common

[PATCH] arch: define weak abort

2017-12-11 Thread Sudip Mukherjee
gcc was generating abort due to 'divide by zero' and if it is not defined in the toolchain the build fails. Currently 'frv' and 'arc' are failing. Previously other arch was also broken like m32r was fixed by d22e3d69ee1a ("m32r: fix build failure"). Lets define this weak function which is common

Re: [REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

2017-12-11 Thread Willem de Bruijn
On Mon, Dec 11, 2017 at 3:35 PM, Joseph Salisbury wrote: > Hi Eric, > > A kernel bug report was opened against Ubuntu [0]. It was found that > reverting the following commit resolved this bug: The recorded trace in that bug is against 4.10.0 with some backports.

Re: [REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

2017-12-11 Thread Willem de Bruijn
On Mon, Dec 11, 2017 at 3:35 PM, Joseph Salisbury wrote: > Hi Eric, > > A kernel bug report was opened against Ubuntu [0]. It was found that > reverting the following commit resolved this bug: The recorded trace in that bug is against 4.10.0 with some backports. Given that commit b2504a5dbef3

Re: [ANNOUNCE] 4.1.46-rt52

2017-12-11 Thread Julia Cartwright
On Mon, Dec 11, 2017 at 03:01:39PM -0600, Corey Minyard wrote: > On 12/11/2017 02:20 PM, Julia Cartwright wrote: > > On Mon, Dec 11, 2017 at 01:04:58PM -0600, Corey Minyard wrote: [..] > > > > > > > > Sebastian Andrzej Siewior (2): > > > > PM / CPU: replace raw_notifier with

Re: [ANNOUNCE] 4.1.46-rt52

2017-12-11 Thread Julia Cartwright
On Mon, Dec 11, 2017 at 03:01:39PM -0600, Corey Minyard wrote: > On 12/11/2017 02:20 PM, Julia Cartwright wrote: > > On Mon, Dec 11, 2017 at 01:04:58PM -0600, Corey Minyard wrote: [..] > > > > > > > > Sebastian Andrzej Siewior (2): > > > > PM / CPU: replace raw_notifier with

Re: [PATCH v3] binder: fix proc->files use-after-free

2017-12-11 Thread Todd Kjos
Greg- when this is in, we'll want it in 4.14 as well. On Mon, Nov 27, 2017 at 9:32 AM, Todd Kjos wrote: > proc->files cleanup is initiated by binder_vma_close. Therefore > a reference on the binder_proc is not enough to prevent the > files_struct from being released while the

Re: [PATCH v3] binder: fix proc->files use-after-free

2017-12-11 Thread Todd Kjos
Greg- when this is in, we'll want it in 4.14 as well. On Mon, Nov 27, 2017 at 9:32 AM, Todd Kjos wrote: > proc->files cleanup is initiated by binder_vma_close. Therefore > a reference on the binder_proc is not enough to prevent the > files_struct from being released while the binder_proc still

Re: [PATCH] Documentation: kernel-hacking: corrected a typo

2017-12-11 Thread Jonathan Corbet
On Fri, 8 Dec 2017 19:10:54 +0100 Marco Donato Torsello wrote: > Corrected a typo. > > Signed-off-by: Marco Donato Torsello > --- > Documentation/kernel-hacking/hacking.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-)

Re: [PATCH] Documentation: kernel-hacking: corrected a typo

2017-12-11 Thread Jonathan Corbet
On Fri, 8 Dec 2017 19:10:54 +0100 Marco Donato Torsello wrote: > Corrected a typo. > > Signed-off-by: Marco Donato Torsello > --- > Documentation/kernel-hacking/hacking.rst | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) Applied to the docs tree, thanks. jon

Re: [PATCH v2 2/2] drm/tinydrm: add driver for ST7735R panels

2017-12-11 Thread Noralf Trønnes
Den 10.12.2017 23.10, skrev David Lechner: This adds a new driver for Sitronix ST7735R display panels. This has been tested using an Adafruit 1.8" TFT. Signed-off-by: David Lechner --- +static void st7735r_pipe_enable(struct drm_simple_display_pipe *pipe, +

Re: [PATCH v2 2/2] drm/tinydrm: add driver for ST7735R panels

2017-12-11 Thread Noralf Trønnes
Den 10.12.2017 23.10, skrev David Lechner: This adds a new driver for Sitronix ST7735R display panels. This has been tested using an Adafruit 1.8" TFT. Signed-off-by: David Lechner --- +static void st7735r_pipe_enable(struct drm_simple_display_pipe *pipe, +

Re: [PATCH] Documentation: mono: Update links and s/CVS/Git/

2017-12-11 Thread Jonathan Corbet
On Sat, 9 Dec 2017 17:21:04 +0100 Jonathan Neuschäfer wrote: > The URLs in mono.rst redirect to pages on www.mono-project.com, so let's > update them. I took the liberty to update the compilation instructions > to the Linux-specific version, because readers of the kernel

Re: [PATCH] Documentation: mono: Update links and s/CVS/Git/

2017-12-11 Thread Jonathan Corbet
On Sat, 9 Dec 2017 17:21:04 +0100 Jonathan Neuschäfer wrote: > The URLs in mono.rst redirect to pages on www.mono-project.com, so let's > update them. I took the liberty to update the compilation instructions > to the Linux-specific version, because readers of the kernel > documentation will

Re: [PATCH] tuners: tda8290: reduce stack usage with kasan

2017-12-11 Thread Michael Ira Krufky
On Mon, Dec 11, 2017 at 2:34 PM, Joe Perches wrote: > On Mon, 2017-12-11 at 13:06 +0100, Arnd Bergmann wrote: >> With CONFIG_KASAN enabled, we get a relatively large stack frame in one >> function >> >> drivers/media/tuners/tda8290.c: In function 'tda8290_set_params': >>

Re: [PATCH] tuners: tda8290: reduce stack usage with kasan

2017-12-11 Thread Michael Ira Krufky
On Mon, Dec 11, 2017 at 2:34 PM, Joe Perches wrote: > On Mon, 2017-12-11 at 13:06 +0100, Arnd Bergmann wrote: >> With CONFIG_KASAN enabled, we get a relatively large stack frame in one >> function >> >> drivers/media/tuners/tda8290.c: In function 'tda8290_set_params': >>

Re: [PATCH v2] mm: terminate shrink_slab loop if signal is pending

2017-12-11 Thread Suren Baghdasaryan
On Sun, Dec 10, 2017 at 2:13 AM, Michal Hocko wrote: > On Fri 08-12-17 10:06:26, Suren Baghdasaryan wrote: >> On Fri, Dec 8, 2017 at 6:03 AM, Tetsuo Handa >> wrote: >> > Michal Hocko wrote: >> >> On Fri 08-12-17 20:36:16, Tetsuo Handa wrote:

Re: [PATCH v2] mm: terminate shrink_slab loop if signal is pending

2017-12-11 Thread Suren Baghdasaryan
On Sun, Dec 10, 2017 at 2:13 AM, Michal Hocko wrote: > On Fri 08-12-17 10:06:26, Suren Baghdasaryan wrote: >> On Fri, Dec 8, 2017 at 6:03 AM, Tetsuo Handa >> wrote: >> > Michal Hocko wrote: >> >> On Fri 08-12-17 20:36:16, Tetsuo Handa wrote: >> >> > On 2017/12/08 17:22, Michal Hocko wrote: >> >>

[PATCH v2] mm: Release a semaphore in 'get_vaddr_frames()'

2017-12-11 Thread Christophe JAILLET
A semaphore is acquired before this check, so we must release it before leaving. Fixes: b7f0554a56f2 ("mm: fail get_vaddr_frames() for filesystem-dax mappings") Signed-off-by: Christophe JAILLET --- -- Untested -- v1 -> v2: 'goto out' instead of duplicating code

[PATCH v2] mm: Release a semaphore in 'get_vaddr_frames()'

2017-12-11 Thread Christophe JAILLET
A semaphore is acquired before this check, so we must release it before leaving. Fixes: b7f0554a56f2 ("mm: fail get_vaddr_frames() for filesystem-dax mappings") Signed-off-by: Christophe JAILLET --- -- Untested -- v1 -> v2: 'goto out' instead of duplicating code --- mm/frame_vector.c | 6

Re: [PATCH] media: pxa_camera: disable and unprepare the clock source on error

2017-12-11 Thread Flavio Ceolin
Hi Laurent, > Hi Flavio, > > Thank you for the patch. > > On Wednesday, 6 December 2017 18:38:50 EET Flavio Ceolin wrote: >> pxa_camera_probe() was not calling pxa_camera_deactivate(), >> responsible to call clk_disable_unprepare(), on the failure path. This >> was leading to unbalancing source

Re: [PATCH] media: pxa_camera: disable and unprepare the clock source on error

2017-12-11 Thread Flavio Ceolin
Hi Laurent, > Hi Flavio, > > Thank you for the patch. > > On Wednesday, 6 December 2017 18:38:50 EET Flavio Ceolin wrote: >> pxa_camera_probe() was not calling pxa_camera_deactivate(), >> responsible to call clk_disable_unprepare(), on the failure path. This >> was leading to unbalancing source

Re: [PATCH v2] mm: terminate shrink_slab loop if signal is pending

2017-12-11 Thread Suren Baghdasaryan
On Sat, Dec 9, 2017 at 12:08 AM, Tetsuo Handa wrote: > Suren Baghdasaryan wrote: >> On Fri, Dec 8, 2017 at 6:03 AM, Tetsuo Handa >> wrote: >> >> > >> This change checks for pending >> >> > >> fatal signals inside shrink_slab

Re: [PATCH v2] mm: terminate shrink_slab loop if signal is pending

2017-12-11 Thread Suren Baghdasaryan
On Sat, Dec 9, 2017 at 12:08 AM, Tetsuo Handa wrote: > Suren Baghdasaryan wrote: >> On Fri, Dec 8, 2017 at 6:03 AM, Tetsuo Handa >> wrote: >> >> > >> This change checks for pending >> >> > >> fatal signals inside shrink_slab loop and if one is detected >> >> > >> terminates this loop early. >>

RE: [PATCH 1/2] vmbus: unregister device_obj->channels_kset

2017-12-11 Thread Dexuan Cui
> From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Monday, December 11, 2017 12:59 PM > To: Dexuan Cui > Cc: Stephen Hemminger ; o...@aepfle.de; > Stephen Hemminger ; jasow...@redhat.com; >

RE: [PATCH 1/2] vmbus: unregister device_obj->channels_kset

2017-12-11 Thread Dexuan Cui
> From: Greg KH [mailto:gre...@linuxfoundation.org] > Sent: Monday, December 11, 2017 12:59 PM > To: Dexuan Cui > Cc: Stephen Hemminger ; o...@aepfle.de; > Stephen Hemminger ; jasow...@redhat.com; > linux-kernel@vger.kernel.org; sta...@vger.kernel.org; a...@canonical.com; >

Re: linux-next: Signed-off-by missing for commit in the nand tree

2017-12-11 Thread Boris Brezillon
On Tue, 12 Dec 2017 07:50:34 +1100 Stephen Rothwell wrote: > Hi Boris, > > Commit > > b8267c7ef4f1 ("mtd: nand: add ->exec_op() implementation") > > is missing a Signed-off-by from its committer. > Just fixed it. Thanks, Boris

Re: linux-next: Signed-off-by missing for commit in the nand tree

2017-12-11 Thread Boris Brezillon
On Tue, 12 Dec 2017 07:50:34 +1100 Stephen Rothwell wrote: > Hi Boris, > > Commit > > b8267c7ef4f1 ("mtd: nand: add ->exec_op() implementation") > > is missing a Signed-off-by from its committer. > Just fixed it. Thanks, Boris

Re: [ANNOUNCE] 4.1.46-rt52

2017-12-11 Thread Corey Minyard
On 12/11/2017 02:20 PM, Julia Cartwright wrote: On Mon, Dec 11, 2017 at 01:04:58PM -0600, Corey Minyard wrote: On 11/29/2017 05:13 PM, Julia Cartwright wrote: Hello RT Folks! I'm pleased to announce the 4.1.46-rt52 stable release. You can get this release via the git tree at:

Re: [ANNOUNCE] 4.1.46-rt52

2017-12-11 Thread Corey Minyard
On 12/11/2017 02:20 PM, Julia Cartwright wrote: On Mon, Dec 11, 2017 at 01:04:58PM -0600, Corey Minyard wrote: On 11/29/2017 05:13 PM, Julia Cartwright wrote: Hello RT Folks! I'm pleased to announce the 4.1.46-rt52 stable release. You can get this release via the git tree at:

Re: [PATCH 1/2] vmbus: unregister device_obj->channels_kset

2017-12-11 Thread Greg KH
On Mon, Dec 11, 2017 at 08:41:44PM +, Dexuan Cui wrote: > > From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On > > Behalf Of Stephen Hemminger > > Sent: Tuesday, November 28, 2017 9:30 AM > > To: Greg KH > > Cc: o...@aepfle.de; Stephen Hemminger

Re: [PATCH 1/2] vmbus: unregister device_obj->channels_kset

2017-12-11 Thread Greg KH
On Mon, Dec 11, 2017 at 08:41:44PM +, Dexuan Cui wrote: > > From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On > > Behalf Of Stephen Hemminger > > Sent: Tuesday, November 28, 2017 9:30 AM > > To: Greg KH > > Cc: o...@aepfle.de; Stephen Hemminger ; > > jasow...@redhat.com;

Re: [PATCH] sched/fair: Prevent a division by 0 in scale_rt_capacity()

2017-12-11 Thread Rohit Jain
Hi Filippo, On 12/09/2017 12:03 AM, Filippo Sironi wrote: ... since total = sched_avg_period() + delta can yield 0x1, which results in a division by 0, given that div_u64() takes a u32 divisor. Use div64_u64() instead. divide error: [#1] SMP CPU: 7 PID: 0 Comm: swapper/7 Not

Re: [PATCH] sched/fair: Prevent a division by 0 in scale_rt_capacity()

2017-12-11 Thread Rohit Jain
Hi Filippo, On 12/09/2017 12:03 AM, Filippo Sironi wrote: ... since total = sched_avg_period() + delta can yield 0x1, which results in a division by 0, given that div_u64() takes a u32 divisor. Use div64_u64() instead. divide error: [#1] SMP CPU: 7 PID: 0 Comm: swapper/7 Not

[PATCH net,stable] net: qmi_wwan: add Sierra EM7565 1199:9091

2017-12-11 Thread ssjoholm
From: Sebastian Sjoholm Sierra Wireless EM7565 is an Qualcomm MDM9x50 based M.2 modem. The USB id is added to qmi_wwan.c to allow QMI communication with the EM7565. Signed-off-by: Sebastian Sjoholm Acked-by: Bjørn Mork --- [The corresponding

[PATCH net,stable] net: qmi_wwan: add Sierra EM7565 1199:9091

2017-12-11 Thread ssjoholm
From: Sebastian Sjoholm Sierra Wireless EM7565 is an Qualcomm MDM9x50 based M.2 modem. The USB id is added to qmi_wwan.c to allow QMI communication with the EM7565. Signed-off-by: Sebastian Sjoholm Acked-by: Bjørn Mork --- [The corresponding qcserial patch will be submitted by Reinhard

linux-next: Signed-off-by missing for commit in the nand tree

2017-12-11 Thread Stephen Rothwell
Hi Boris, Commit b8267c7ef4f1 ("mtd: nand: add ->exec_op() implementation") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell

linux-next: Signed-off-by missing for commit in the nand tree

2017-12-11 Thread Stephen Rothwell
Hi Boris, Commit b8267c7ef4f1 ("mtd: nand: add ->exec_op() implementation") is missing a Signed-off-by from its committer. -- Cheers, Stephen Rothwell

Re: [PATCH] KVM: X86: Fix host dr6 miss restore

2017-12-11 Thread David Hildenbrand
On 10.12.2017 01:44, Wanpeng Li wrote: > 2017-12-08 20:39 GMT+08:00 David Hildenbrand : >> On 08.12.2017 10:12, Wanpeng Li wrote: >>> From: Wanpeng Li >>> >>> Reported by syzkaller: >>> >>>WARNING: CPU: 0 PID: 12927 at arch/x86/kernel/traps.c:780 >>>

Re: [PATCH] KVM: X86: Fix host dr6 miss restore

2017-12-11 Thread David Hildenbrand
On 10.12.2017 01:44, Wanpeng Li wrote: > 2017-12-08 20:39 GMT+08:00 David Hildenbrand : >> On 08.12.2017 10:12, Wanpeng Li wrote: >>> From: Wanpeng Li >>> >>> Reported by syzkaller: >>> >>>WARNING: CPU: 0 PID: 12927 at arch/x86/kernel/traps.c:780 >>> do_debug+0x222/0x250 >>>CPU: 0 PID:

Re: [PATCH RESEND] KVM: X86: Fix load bad host fpu state

2017-12-11 Thread David Hildenbrand
On 10.12.2017 22:44, Wanpeng Li wrote: > From: Wanpeng Li > > [ cut here ] > Bad FPU state detected at kvm_put_guest_fpu+0xd8/0x2d0 [kvm], reinitializing > FPU registers. > WARNING: CPU: 1 PID: 4594 at arch/x86/mm/extable.c:103 >

Re: [PATCH RESEND] KVM: X86: Fix load bad host fpu state

2017-12-11 Thread David Hildenbrand
On 10.12.2017 22:44, Wanpeng Li wrote: > From: Wanpeng Li > > [ cut here ] > Bad FPU state detected at kvm_put_guest_fpu+0xd8/0x2d0 [kvm], reinitializing > FPU registers. > WARNING: CPU: 1 PID: 4594 at arch/x86/mm/extable.c:103 > ex_handler_fprestore+0x88/0x90 > CPU:

[PATCH 41/45] arch/x86: remove duplicate includes

2017-12-11 Thread Pravin Shedge
These duplicate includes have been found with scripts/checkincludes.pl but they have been removed manually to avoid removing false positives. Signed-off-by: Pravin Shedge --- arch/x86/kernel/itmt.c | 1 - arch/x86/kernel/process.c | 1 -

[PATCH 41/45] arch/x86: remove duplicate includes

2017-12-11 Thread Pravin Shedge
These duplicate includes have been found with scripts/checkincludes.pl but they have been removed manually to avoid removing false positives. Signed-off-by: Pravin Shedge --- arch/x86/kernel/itmt.c | 1 - arch/x86/kernel/process.c | 1 - arch/x86/kernel/setup.c| 1 -

RE: [PATCH 1/2] vmbus: unregister device_obj->channels_kset

2017-12-11 Thread Dexuan Cui
> From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On > Behalf Of Stephen Hemminger > Sent: Tuesday, November 28, 2017 9:30 AM > To: Greg KH > Cc: o...@aepfle.de; Stephen Hemminger ; > jasow...@redhat.com;

RE: [PATCH 1/2] vmbus: unregister device_obj->channels_kset

2017-12-11 Thread Dexuan Cui
> From: devel [mailto:driverdev-devel-boun...@linuxdriverproject.org] On > Behalf Of Stephen Hemminger > Sent: Tuesday, November 28, 2017 9:30 AM > To: Greg KH > Cc: o...@aepfle.de; Stephen Hemminger ; > jasow...@redhat.com; linux-kernel@vger.kernel.org; sta...@vger.kernel.org; >

Re: [PATCH 2/2] ntb_hw_switchtec: Check for alignment of the buffer in mw_set_trans()

2017-12-11 Thread Logan Gunthorpe
On 11/12/17 01:06 PM, Allen Hubbe wrote: In switchtec_ntb_mw_get_align, for the lut case it seems to require alignment the same as Intel, aligned to mw size, but for the non-lut case you are saying that SZ_4K is not necessarily correct. The SZ_4K is the minimum, but the actual alignment

Re: [PATCH 2/2] ntb_hw_switchtec: Check for alignment of the buffer in mw_set_trans()

2017-12-11 Thread Logan Gunthorpe
On 11/12/17 01:06 PM, Allen Hubbe wrote: In switchtec_ntb_mw_get_align, for the lut case it seems to require alignment the same as Intel, aligned to mw size, but for the non-lut case you are saying that SZ_4K is not necessarily correct. The SZ_4K is the minimum, but the actual alignment

[REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

2017-12-11 Thread Joseph Salisbury
Hi Eric, A kernel bug report was opened against Ubuntu [0].  It was found that reverting the following commit resolved this bug: commit b2504a5dbef3305ef41988ad270b0e8ec289331c Author: Eric Dumazet Date:   Tue Jan 31 10:20:32 2017 -0800     net: reduce

Re: [PATCH net,stable] net: qmi_wwan: add Sierra EM7565 1199:9091

2017-12-11 Thread Bjørn Mork
ssjoh...@mac.com writes: > From: Sebastian Sjoholm > > From: Sebastian Sjoholm > > Sierra Wireless EM7565 is an Qualcomm MDM9x50 based M.2 modem. > The USB id is added to qmi_wwan.c to allow QMI communication with the EM7565. > > Signed-off-by: Sebastian

[REGRESSION][4.13.y][4.14.y][v4.15.y] net: reduce skb_warn_bad_offload() noise

2017-12-11 Thread Joseph Salisbury
Hi Eric, A kernel bug report was opened against Ubuntu [0].  It was found that reverting the following commit resolved this bug: commit b2504a5dbef3305ef41988ad270b0e8ec289331c Author: Eric Dumazet Date:   Tue Jan 31 10:20:32 2017 -0800     net: reduce skb_warn_bad_offload() noise     The

Re: [PATCH net,stable] net: qmi_wwan: add Sierra EM7565 1199:9091

2017-12-11 Thread Bjørn Mork
ssjoh...@mac.com writes: > From: Sebastian Sjoholm > > From: Sebastian Sjoholm > > Sierra Wireless EM7565 is an Qualcomm MDM9x50 based M.2 modem. > The USB id is added to qmi_wwan.c to allow QMI communication with the EM7565. > > Signed-off-by: Sebastian Sjoholm > --- > [The corresponding

<    1   2   3   4   5   6   7   8   9   10   >