Re: [RFC PATCH net v2 0/3] Fix OdroidC2 Gigabit Tx link issue

On Thu, 2016-11-24 at 15:40 +0100, Martin Blumenstingl wrote: > Hi Jerome, > > On Mon, Nov 21, 2016 at 4:35 PM, Jerome Brunet > wrote: > > > > This patchset fixes an issue with the OdroidC2 board (DWMAC + > > RTL8211F). > > Initially reported as a low Tx throughput issue

Re: [RFC PATCH net v2 0/3] Fix OdroidC2 Gigabit Tx link issue

On Thu, 2016-11-24 at 15:40 +0100, Martin Blumenstingl wrote: > Hi Jerome, > > On Mon, Nov 21, 2016 at 4:35 PM, Jerome Brunet > wrote: > > > > This patchset fixes an issue with the OdroidC2 board (DWMAC + > > RTL8211F). > > Initially reported as a low Tx throughput issue at gigabit speed, > >

Re: linux-next: Tree for Nov 24

On Thu, Nov 24, 2016 at 12:35 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20161123: > > Removed tree: remoteproc (no longer used) > > The powerpc tree gained a conflict against the powerpc-fixes tree. > > The kvm-ppc-paulus tree gained conflicts against the

Re: linux-next: Tree for Nov 24

On Thu, Nov 24, 2016 at 12:35 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20161123: > > Removed tree: remoteproc (no longer used) > > The powerpc tree gained a conflict against the powerpc-fixes tree. > > The kvm-ppc-paulus tree gained conflicts against the powerpc-fixes and >

Is it an error to have two instances of "reboot" running at the same time?

-- Regards, Ajay

Is it an error to have two instances of "reboot" running at the same time?

-- Regards, Ajay

Re: [PATCH v5 2/2] DW DMAC: add multi-block property to device tree

On Thu, 2016-11-24 at 17:52 +0200, Andy Shevchenko wrote: > On Thu, 2016-11-24 at 18:04 +0300, Eugeniy Paltsev wrote: > > Several versions of DW DMAC have multi block transfers hardware > > support. Hardware support of multi block transfers is disabled > > by default if we use DT to configure DMAC

Re: [PATCH v5 2/2] DW DMAC: add multi-block property to device tree

On Thu, 2016-11-24 at 17:52 +0200, Andy Shevchenko wrote: > On Thu, 2016-11-24 at 18:04 +0300, Eugeniy Paltsev wrote: > > Several versions of DW DMAC have multi block transfers hardware > > support. Hardware support of multi block transfers is disabled > > by default if we use DT to configure DMAC

Re: [PATCH] Move platform device creation earlier in the initialization

On Mon, Nov 07, 2016 at 12:35:10PM -0600, miny...@acm.org wrote: > From: Corey Minyard > > Some logs are printed out early using smi->dev, but on a platform device > that is not created until later. So move the creation of that device > structure earlier in the sequence so

Re: [PATCH] Move platform device creation earlier in the initialization

On Mon, Nov 07, 2016 at 12:35:10PM -0600, miny...@acm.org wrote: > From: Corey Minyard > > Some logs are printed out early using smi->dev, but on a platform device > that is not created until later. So move the creation of that device > structure earlier in the sequence so it can be used for

Re: [PATCH v3] media: i2c-polling: add i2c-polling driver

Hi Matt, On Thursday 24 Nov 2016 00:04:24 Matt Ranostay wrote: > On Wed, Nov 23, 2016 at 10:31 PM, Matt Ranostay wrote: > > On Wed, Nov 23, 2016 at 8:30 AM, Laurent Pinchart wrote: > >> On Tuesday 22 Nov 2016 17:18:40 Matt Ranostay wrote: > >>> There are several thermal sensors that only have a

Re: [PATCH v3] media: i2c-polling: add i2c-polling driver

Hi Matt, On Thursday 24 Nov 2016 00:04:24 Matt Ranostay wrote: > On Wed, Nov 23, 2016 at 10:31 PM, Matt Ranostay wrote: > > On Wed, Nov 23, 2016 at 8:30 AM, Laurent Pinchart wrote: > >> On Tuesday 22 Nov 2016 17:18:40 Matt Ranostay wrote: > >>> There are several thermal sensors that only have a

Re: [PATCH v5 2/2] DW DMAC: add multi-block property to device tree

On Thu, 2016-11-24 at 18:04 +0300, Eugeniy Paltsev wrote: > Several versions of DW DMAC have multi block transfers hardware > support. Hardware support of multi block transfers is disabled > by default if we use DT to configure DMAC and software emulation > of multi block transfers used instead. >

Re: [PATCH v5 2/2] DW DMAC: add multi-block property to device tree

On Thu, 2016-11-24 at 18:04 +0300, Eugeniy Paltsev wrote: > Several versions of DW DMAC have multi block transfers hardware > support. Hardware support of multi block transfers is disabled > by default if we use DT to configure DMAC and software emulation > of multi block transfers used instead. >

Re: [PATCH] checkpatch: warn if is already included

On Thu, 2016-11-24 at 22:45 +0800, Geliang Tang wrote: > Some headers are included twice. Emit a warning when they occur. > For example: > $ ./scripts/checkpatch.pl -f drivers/of/overlay.c > WARNING: Do not use #include , this header is already included > +#include > > WARNING: Do not use

Re: [PATCH] checkpatch: warn if is already included

On Thu, 2016-11-24 at 22:45 +0800, Geliang Tang wrote: > Some headers are included twice. Emit a warning when they occur. > For example: > $ ./scripts/checkpatch.pl -f drivers/of/overlay.c > WARNING: Do not use #include , this header is already included > +#include > > WARNING: Do not use

[PATCH] Input: Change msleep to usleep_range for small msecs

msleep(1~20) may not do what the caller intends, and will often sleep longer. (~20 ms actual sleep for any value given in the 1~20ms range) This is not the desired behaviour for many cases like device resume time, device suspend time, device enable time, etc. Thus, change msleep to usleep_range

Re: [PATCH 1/4] serial: core: Add LED trigger support

On Thu, Nov 24, 2016 at 07:41:37AM +0100, Sascha Hauer wrote: > On Wed, Nov 23, 2016 at 10:13:02AM -0700, Mathieu Poirier wrote: > > On Wed, Nov 23, 2016 at 11:01:03AM +0100, Sascha Hauer wrote: > > > With this patch the serial core provides LED triggers for RX and TX. > > > > > > As the serial

[PATCH] Input: Change msleep to usleep_range for small msecs

msleep(1~20) may not do what the caller intends, and will often sleep longer. (~20 ms actual sleep for any value given in the 1~20ms range) This is not the desired behaviour for many cases like device resume time, device suspend time, device enable time, etc. Thus, change msleep to usleep_range

Re: [PATCH 1/4] serial: core: Add LED trigger support

On Thu, Nov 24, 2016 at 07:41:37AM +0100, Sascha Hauer wrote: > On Wed, Nov 23, 2016 at 10:13:02AM -0700, Mathieu Poirier wrote: > > On Wed, Nov 23, 2016 at 11:01:03AM +0100, Sascha Hauer wrote: > > > With this patch the serial core provides LED triggers for RX and TX. > > > > > > As the serial

Re: linux-next: Tree for Nov 24

On Thu, Nov 24, 2016 at 12:35 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20161123: > > Removed tree: remoteproc (no longer used) > > The powerpc tree gained a conflict against the powerpc-fixes tree. > > The kvm-ppc-paulus tree gained conflicts against the

Re: linux-next: Tree for Nov 24

On Thu, Nov 24, 2016 at 12:35 AM, Stephen Rothwell wrote: > Hi all, > > Changes since 20161123: > > Removed tree: remoteproc (no longer used) > > The powerpc tree gained a conflict against the powerpc-fixes tree. > > The kvm-ppc-paulus tree gained conflicts against the powerpc-fixes and >

Regarding "scsi_lib: Decode T10 vendor IDs" d230823a1c4c3e97afd4c934b86b3975d5e20249

Hi, Regarding this commit : https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d230823a1c4c3e97afd4c934b86b3975d5e20249 Looking at both the code and the comment, it seems to me you wanted 'T10' id to be a last resort if nothing else was available. If that was the

Regarding "scsi_lib: Decode T10 vendor IDs" d230823a1c4c3e97afd4c934b86b3975d5e20249

Hi, Regarding this commit : https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=d230823a1c4c3e97afd4c934b86b3975d5e20249 Looking at both the code and the comment, it seems to me you wanted 'T10' id to be a last resort if nothing else was available. If that was the

Re: [patch] iio: tsl2583: make array large enough

On Thu, Nov 24, 2016 at 04:38:07PM +0300, Dan Carpenter wrote: > This array is supposed to have 10 elements. Smatch complains that with > the current code we can have n == max_ints and read beyond the end of > the array. > > Fixes: ac4f6eee8fe8 ("staging: iio: TAOS tsl258x: Device driver") >

Re: [patch] iio: tsl2583: make array large enough

On Thu, Nov 24, 2016 at 04:38:07PM +0300, Dan Carpenter wrote: > This array is supposed to have 10 elements. Smatch complains that with > the current code we can have n == max_ints and read beyond the end of > the array. > > Fixes: ac4f6eee8fe8 ("staging: iio: TAOS tsl258x: Device driver") >

[PATCH 4.8 13/67] mfd: stmpe: Fix RESET regression on STMPE2401

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit f40584200bc4af7aa4399635b9ac213c62a13ae7 upstream. Since commit c4dd1ba355aae2bc3d1213da6c66c53e3c31e028 ("mfd: stmpe: Add reset support for all

[PATCH 4.8 10/67] IB/rdmavt: rdmavt can handle non aligned page maps

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Dennis Dalessandro commit e1fafdcbe0e3e769c6a83317dd845bc99b4fe61d upstream. The initial code for rdmavt carried with it a restriction that was a vestige from the

[PATCH 4.8 43/67] iwlwifi: mvm: wake the wait queue when the RX sync counter is zero

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit 3a732c65de427fdae67a243fd331356034b5a1e8 upstream. When we sync the RX queues the driver waits to receive echo notification on all the RX queues. The

[PATCH 4.8 16/67] ALSA: usb-audio: Fix use-after-free of usb_device at disconnect

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 6ff1a25318ebf688ef9593fe09cd449f6fb4ad31 upstream. The usb-audio driver implements the deferred device disconnection for the device in use. In this mode,

[PATCH 4.8 13/67] mfd: stmpe: Fix RESET regression on STMPE2401

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Linus Walleij commit f40584200bc4af7aa4399635b9ac213c62a13ae7 upstream. Since commit c4dd1ba355aae2bc3d1213da6c66c53e3c31e028 ("mfd: stmpe: Add reset support for all STMPE variant") we're

[PATCH 4.8 10/67] IB/rdmavt: rdmavt can handle non aligned page maps

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Dennis Dalessandro commit e1fafdcbe0e3e769c6a83317dd845bc99b4fe61d upstream. The initial code for rdmavt carried with it a restriction that was a vestige from the qib driver, that to dma map a

[PATCH 4.8 43/67] iwlwifi: mvm: wake the wait queue when the RX sync counter is zero

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Sara Sharon commit 3a732c65de427fdae67a243fd331356034b5a1e8 upstream. When we sync the RX queues the driver waits to receive echo notification on all the RX queues. The wait queue is set with

[PATCH 4.8 16/67] ALSA: usb-audio: Fix use-after-free of usb_device at disconnect

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 6ff1a25318ebf688ef9593fe09cd449f6fb4ad31 upstream. The usb-audio driver implements the deferred device disconnection for the device in use. In this mode, the disconnection

[PATCH 4.8 18/67] ALSA: hda - Fix mic regression by ASRock mobo fixup

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 9a2541910dc7eaaa6859eea8a0ffda673059a623 upstream. The commit [1a3f099101b8: ALSA: hda - Fix surround output pins for ASRock B150M mobo] introduced a fixup

[PATCH 4.8 52/67] IB/rxe: Fix handling of erroneous WR

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Yonatan Cohen commit 002e062e13db10973adb8302f231e48b477c7ccf upstream. To correctly handle a erroneous WR this fix does the following 1. Make sure the bad WQE causes a

[PATCH 4.8 18/67] ALSA: hda - Fix mic regression by ASRock mobo fixup

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Takashi Iwai commit 9a2541910dc7eaaa6859eea8a0ffda673059a623 upstream. The commit [1a3f099101b8: ALSA: hda - Fix surround output pins for ASRock B150M mobo] introduced a fixup of pin configs

[PATCH 4.8 52/67] IB/rxe: Fix handling of erroneous WR

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Yonatan Cohen commit 002e062e13db10973adb8302f231e48b477c7ccf upstream. To correctly handle a erroneous WR this fix does the following 1. Make sure the bad WQE causes a user completion event.

[PATCH 4.8 12/67] mfd: intel-lpss: Do not put device in reset state on suspend

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Azhar Shaikh commit 274e43edcda6f709aa67e436b3123e45a6270923 upstream. Commit 41a3da2b8e163 ("mfd: intel-lpss: Save register context on suspend") saved the register

[PATCH 4.8 12/67] mfd: intel-lpss: Do not put device in reset state on suspend

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Azhar Shaikh commit 274e43edcda6f709aa67e436b3123e45a6270923 upstream. Commit 41a3da2b8e163 ("mfd: intel-lpss: Save register context on suspend") saved the register context while going to

[PATCH 4.8 51/67] IB/rxe: Fix kernel panic in UDP tunnel with GRO and RX checksum

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Yonatan Cohen commit 1454ca3a97e147bb91e98b087446c39cf6692a48 upstream. Missing initialization of udp_tunnel_sock_cfg causes to following kernel panic, while kernel

[PATCH 4.8 48/67] PM / sleep: dont suspend parent when async child suspend_{noirq, late} fails

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit 6f75c3fd56daf547d684127a7f83c283c3c160d1 upstream. Consider two devices, A and B, where B is a child of A, and B utilizes asynchronous suspend (it

[PATCH 4.8 51/67] IB/rxe: Fix kernel panic in UDP tunnel with GRO and RX checksum

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Yonatan Cohen commit 1454ca3a97e147bb91e98b087446c39cf6692a48 upstream. Missing initialization of udp_tunnel_sock_cfg causes to following kernel panic, while kernel tries to execute

[PATCH 4.8 48/67] PM / sleep: dont suspend parent when async child suspend_{noirq, late} fails

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Brian Norris commit 6f75c3fd56daf547d684127a7f83c283c3c160d1 upstream. Consider two devices, A and B, where B is a child of A, and B utilizes asynchronous suspend (it does not matter whether A

Re: [PATCH] gpio: Add Tegra186 support

On Wed, Nov 23, 2016 at 8:44 PM, Thierry Reding wrote: > On Wed, Nov 23, 2016 at 02:30:45PM +0100, Linus Walleij wrote: >> On Tue, Nov 22, 2016 at 6:55 PM, Thierry Reding >> wrote: >> >> > From: Thierry Reding >> > >> >

[PATCH 4.8 50/67] IB/rxe: Update qp state for user query

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Yonatan Cohen commit 6d931308f55faaef3f30bd0346c47f99528b229d upstream. The method rxe_qp_error() transitions QP to error state and make sure the QP is drained. It did

[PATCH 4.8 49/67] perf hists: Fix column length on --hierarchy

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Namhyung Kim commit c72ab446cac1d6c9551fd26c4cfef1b2fc5041fd upstream. Markus reported that there's a weird behavior on perf top --hierarchy regarding the column length.

[PATCH 4.8 50/67] IB/rxe: Update qp state for user query

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Yonatan Cohen commit 6d931308f55faaef3f30bd0346c47f99528b229d upstream. The method rxe_qp_error() transitions QP to error state and make sure the QP is drained. It did not though update the QP

[PATCH 4.8 49/67] perf hists: Fix column length on --hierarchy

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Namhyung Kim commit c72ab446cac1d6c9551fd26c4cfef1b2fc5041fd upstream. Markus reported that there's a weird behavior on perf top --hierarchy regarding the column length. Looking at the code,

Re: [PATCH] gpio: Add Tegra186 support

On Wed, Nov 23, 2016 at 8:44 PM, Thierry Reding wrote: > On Wed, Nov 23, 2016 at 02:30:45PM +0100, Linus Walleij wrote: >> On Tue, Nov 22, 2016 at 6:55 PM, Thierry Reding >> wrote: >> >> > From: Thierry Reding >> > >> > Tegra186 has two GPIO controllers that are largely register compatible >> >

Re: [patch] net/mlx5: remove a duplicate condition

On Thu, Nov 24, 2016 at 1:03 PM, Dan Carpenter wrote: > We verified that MLX5_FLOW_CONTEXT_ACTION_COUNT was set on the first > line of the function so we don't need to check again here. > > Signed-off-by: Dan Carpenter Acked-by: Saeed Mahameed

Re: [PATCH v2][RESEND] seq_file: don't set read position for invalid iterator

On Thu, Nov 24, 2016 at 4:23 PM, Tomasz Majchrzak wrote: > I don't understand it. Is it possible to map file position to the index > (record)? I think there is no way to determine record size without actually > reading it. Right. So don't update m->index when a

[PATCH 4.8 45/67] sunrpc: svc_age_temp_xprts_now should not call setsockopt non-tcp transports

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Scott Mayhew commit ea08e39230e898844d9de5b60cdbb30067cebfe7 upstream. This fixes the following panic that can occur with NFSoRDMA. general protection fault: [#1] SMP

[PATCH 4.8 42/67] iwlwifi: mvm: fix d3_test with unified D0/D3 images

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Luca Coelho commit 85cd69b8f1f7e289fe931a82889e673fd0f04842 upstream. When a unified D0/D3 image is used, we don't restart the FW in the D0->D3->D0 transitions.

Re: [patch] net/mlx5: remove a duplicate condition

On Thu, Nov 24, 2016 at 1:03 PM, Dan Carpenter wrote: > We verified that MLX5_FLOW_CONTEXT_ACTION_COUNT was set on the first > line of the function so we don't need to check again here. > > Signed-off-by: Dan Carpenter Acked-by: Saeed Mahameed

Re: [PATCH v2][RESEND] seq_file: don't set read position for invalid iterator

On Thu, Nov 24, 2016 at 4:23 PM, Tomasz Majchrzak wrote: > I don't understand it. Is it possible to map file position to the index > (record)? I think there is no way to determine record size without actually > reading it. Right. So don't update m->index when a zero size record is read. This

[PATCH 4.8 45/67] sunrpc: svc_age_temp_xprts_now should not call setsockopt non-tcp transports

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Scott Mayhew commit ea08e39230e898844d9de5b60cdbb30067cebfe7 upstream. This fixes the following panic that can occur with NFSoRDMA. general protection fault: [#1] SMP Modules linked in:

[PATCH 4.8 42/67] iwlwifi: mvm: fix d3_test with unified D0/D3 images

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Luca Coelho commit 85cd69b8f1f7e289fe931a82889e673fd0f04842 upstream. When a unified D0/D3 image is used, we don't restart the FW in the D0->D3->D0 transitions. Therefore, the d3_test

Re: [PATCH 7/10] mmc: sdhci-xenon: Add support to PHYs of Marvell Xenon SDHC

Hi Ulf, On 2016/11/24 22:33, Ulf Hansson wrote: > [...] > >>> + +static int __xenon_emmc_delay_adj_test(struct mmc_card *card) +{ + int err; + u8 *ext_csd = NULL; + + err = mmc_get_ext_csd(card, _csd); + kfree(ext_csd); >>> >>>

Re: [PATCH 7/10] mmc: sdhci-xenon: Add support to PHYs of Marvell Xenon SDHC

Hi Ulf, On 2016/11/24 22:33, Ulf Hansson wrote: > [...] > >>> + +static int __xenon_emmc_delay_adj_test(struct mmc_card *card) +{ + int err; + u8 *ext_csd = NULL; + + err = mmc_get_ext_csd(card, _csd); + kfree(ext_csd); >>> >>>

[PATCH 4.8 46/67] uwb: fix device reference leaks

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit d6124b409ca33c100170ffde51cd8dff761454a1 upstream. This subsystem consistently fails to drop the device reference taken by class_find_device(). Note that

[PATCH 4.8 53/67] IB/rxe: Clear queue buffer when modifying QP to reset

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Yonatan Cohen commit aa75b07b478a774b1432e2df1be5cd8ae834de0f upstream. RXE resets the send-q only once in rxe_qp_init_req() when QP is created, but when the QP is

[PATCH 4.8 44/67] mfd: core: Fix device reference leak in mfd_clone_cell

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 722f191080de641f023feaa7d5648caf377844f5 upstream. Make sure to drop the reference taken by bus_find_device_by_name() before returning from

[PATCH 4.8 47/67] PM / sleep: fix device reference leak in test_suspend

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit ceb75787bc75d0a7b88519ab8a68067ac690f55a upstream. Make sure to drop the reference taken by class_find_device() after opening the RTC device. Fixes:

[PATCH 4.8 46/67] uwb: fix device reference leaks

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit d6124b409ca33c100170ffde51cd8dff761454a1 upstream. This subsystem consistently fails to drop the device reference taken by class_find_device(). Note that some of these

[PATCH 4.8 53/67] IB/rxe: Clear queue buffer when modifying QP to reset

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Yonatan Cohen commit aa75b07b478a774b1432e2df1be5cd8ae834de0f upstream. RXE resets the send-q only once in rxe_qp_init_req() when QP is created, but when the QP is reused after QP reset, the

[PATCH 4.8 44/67] mfd: core: Fix device reference leak in mfd_clone_cell

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit 722f191080de641f023feaa7d5648caf377844f5 upstream. Make sure to drop the reference taken by bus_find_device_by_name() before returning from mfd_clone_cell(). Fixes:

[PATCH 4.8 47/67] PM / sleep: fix device reference leak in test_suspend

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Johan Hovold commit ceb75787bc75d0a7b88519ab8a68067ac690f55a upstream. Make sure to drop the reference taken by class_find_device() after opening the RTC device. Fixes: 77437fd4e61f (pm: boot

[PATCH 4.8 54/67] IB/mlx4: Check gid_index return value

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Jurgens commit 37995116fecfce2b61ee3da6e73b3e394c6818f9 upstream. Check the returned GID index value and return an error if it is invalid. Fixes: 5070cd2239bd

[PATCH 4.8 54/67] IB/mlx4: Check gid_index return value

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Jurgens commit 37995116fecfce2b61ee3da6e73b3e394c6818f9 upstream. Check the returned GID index value and return an error if it is invalid. Fixes: 5070cd2239bd ('IB/mlx4: Replace

Re: [PATCH] futex: Fix potential use-after-free in FUTEX_REQUEUE_PI

On Thu, Nov 24, 2016 at 04:19:41PM +0100, Thomas Gleixner wrote: > On Thu, 24 Nov 2016, Peter Zijlstra wrote: > > > > > While working on the futex code, I stumbled over this potential > > use-after-free scenario. > > > > pi_mutex is a pointer into pi_state, which we drop the reference on in > >

Re: [PATCH] futex: Fix potential use-after-free in FUTEX_REQUEUE_PI

On Thu, Nov 24, 2016 at 04:19:41PM +0100, Thomas Gleixner wrote: > On Thu, 24 Nov 2016, Peter Zijlstra wrote: > > > > > While working on the futex code, I stumbled over this potential > > use-after-free scenario. > > > > pi_mutex is a pointer into pi_state, which we drop the reference on in > >

[PATCH 4.8 58/67] IB/mlx5: Fix memory leak in query device

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Majd Dibbiny commit 90be7c8ab72853ff9fc407f01518a898df1f3045 upstream. We need to free dev->port when we fail to enable RoCE or initialize node data. Fixes: 0837e86a7a34

[PATCH 4.8 58/67] IB/mlx5: Fix memory leak in query device

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Majd Dibbiny commit 90be7c8ab72853ff9fc407f01518a898df1f3045 upstream. We need to free dev->port when we fail to enable RoCE or initialize node data. Fixes: 0837e86a7a34 ('IB/mlx5: Add per

Re: wl1251 & mac address & calibration data

Hi, On 24.11.2016 17:20, Pali Rohár wrote: In case when wl1251 is statically linked into kernel image, it is loaded and initialized before even userspace applications starts. Which leaves no option, but integrating libcal into kernel :). Ivo

[PATCH 4.8 67/67] gpio: pca953x: Fix corruption of other gpios in set_multiple.

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Phil Reid commit 53f8d322234649b4d6f1515b20c127a577efd164 upstream. gpiod_set_array_value_complex does not clear the bits field. Therefore when the drivers

[PATCH 4.8 59/67] IB/mlx5: Fix fatal error dispatching

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Eli Cohen commit dbaaff2a2caa03d472b5cc53a3fbfd415c97dc26 upstream. When an internal error condition is detected, make sure to set the device inactive after dispatching the

[PATCH 4.8 33/67] virtio-net: drop legacy features in virtio 1 mode

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Michael S. Tsirkin commit f3358507c11999c91abf54744658bccd49b5879c upstream. Virtio 1.0 spec says VIRTIO_F_ANY_LAYOUT and VIRTIO_NET_F_GSO are legacy-only feature bits. Do not

[PATCH 4.8 66/67] gpio: pca953x: Move memcpy into mutex lock for set multiple

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Phil Reid commit 386377b5473043c09b2de40bfe5abfb0fc87e1b4 upstream. Need to ensure that reg_output is not updated while setting multiple bits. This makes the mutex

Re: GPL-Archive for UniFi(R) AP AC PRO fw 3.4.17.3440

Hi, I don't care if you already have it or not. But I have the right to get the sources. Otherwise your are VIOLATING the GPL license of software YOU ARE USING ON UNIFI DEVICES. So I ask again, please provide me the source code of all the GPL components on the UniFi(R) AP AC PRO including the

[PATCH 4.8 60/67] IB/mlx5: Fix NULL pointer dereference on debug print

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Eli Cohen commit a1ab8402d15d2305d2315d96ec3294bfdf16587e upstream. For XRC QP CQs may not exist. Check before attempting dereference. Fixes: e126ba97dba9 ('mlx5: Add

[PATCH 4.8 66/67] gpio: pca953x: Move memcpy into mutex lock for set multiple

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Phil Reid commit 386377b5473043c09b2de40bfe5abfb0fc87e1b4 upstream. Need to ensure that reg_output is not updated while setting multiple bits. This makes the mutex locking behaviour for the

Re: GPL-Archive for UniFi(R) AP AC PRO fw 3.4.17.3440

Hi, I don't care if you already have it or not. But I have the right to get the sources. Otherwise your are VIOLATING the GPL license of software YOU ARE USING ON UNIFI DEVICES. So I ask again, please provide me the source code of all the GPL components on the UniFi(R) AP AC PRO including the

[PATCH 4.8 60/67] IB/mlx5: Fix NULL pointer dereference on debug print

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Eli Cohen commit a1ab8402d15d2305d2315d96ec3294bfdf16587e upstream. For XRC QP CQs may not exist. Check before attempting dereference. Fixes: e126ba97dba9 ('mlx5: Add driver for Mellanox

Re: wl1251 & mac address & calibration data

Hi, On 24.11.2016 17:20, Pali Rohár wrote: In case when wl1251 is statically linked into kernel image, it is loaded and initialized before even userspace applications starts. Which leaves no option, but integrating libcal into kernel :). Ivo

[PATCH 4.8 67/67] gpio: pca953x: Fix corruption of other gpios in set_multiple.

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Phil Reid commit 53f8d322234649b4d6f1515b20c127a577efd164 upstream. gpiod_set_array_value_complex does not clear the bits field. Therefore when the drivers set_multiple funciton is called bits

[PATCH 4.8 59/67] IB/mlx5: Fix fatal error dispatching

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Eli Cohen commit dbaaff2a2caa03d472b5cc53a3fbfd415c97dc26 upstream. When an internal error condition is detected, make sure to set the device inactive after dispatching the event so ULPs can

[PATCH 4.8 33/67] virtio-net: drop legacy features in virtio 1 mode

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Michael S. Tsirkin commit f3358507c11999c91abf54744658bccd49b5879c upstream. Virtio 1.0 spec says VIRTIO_F_ANY_LAYOUT and VIRTIO_NET_F_GSO are legacy-only feature bits. Do not negotiate them

[PATCH 4.8 57/67] IB/mlx5: Use cache line size to select CQE stride

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Jurgens commit 16b0e0695a73b68d8ca40288c8f9614ef208917b upstream. When creating kernel CQs use 128B CQE stride if the cache line size is 128B, 64B otherwise. This

[PATCH 4.8 61/67] IB/core: Avoid unsigned int overflow in sg_alloc_table

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Mark Bloch commit 3c7ba5760ab8eedec01159b267bb9bfcffe522ac upstream. sg_alloc_table gets unsigned int as parameter while the driver returns it as size_t. Check npages isn't

[PATCH 4.8 56/67] IB/mlx5: Validate requested RQT size

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Maor Gottlieb commit efd7f40082a0dfd112eb87ff2124467a5739216f upstream. Validate that the requested size of RQT is supported by firmware. Fixes: c5f9092936fe ('IB/mlx5:

[PATCH 4.8 57/67] IB/mlx5: Use cache line size to select CQE stride

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Daniel Jurgens commit 16b0e0695a73b68d8ca40288c8f9614ef208917b upstream. When creating kernel CQs use 128B CQE stride if the cache line size is 128B, 64B otherwise. This prevents multiple

[PATCH 4.8 61/67] IB/core: Avoid unsigned int overflow in sg_alloc_table

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Mark Bloch commit 3c7ba5760ab8eedec01159b267bb9bfcffe522ac upstream. sg_alloc_table gets unsigned int as parameter while the driver returns it as size_t. Check npages isn't greater than

[PATCH 4.8 56/67] IB/mlx5: Validate requested RQT size

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Maor Gottlieb commit efd7f40082a0dfd112eb87ff2124467a5739216f upstream. Validate that the requested size of RQT is supported by firmware. Fixes: c5f9092936fe ('IB/mlx5: Add Receive Work Queue

[PATCH v2 0/3] ARM: davinci: OHCI: Use a regulator instead of callbacks

Convert users of OHCI pdata to use a regulator instead of passing platform function pointers. This will help to remove the ohci platform callbacks in a future series. Changes form v1->v2 * Add function name and error number in error path print (Sekhar) Dependencies: 1. [PATCH v7 0/5] USB:

[PATCH v2 0/3] ARM: davinci: OHCI: Use a regulator instead of callbacks

Convert users of OHCI pdata to use a regulator instead of passing platform function pointers. This will help to remove the ohci platform callbacks in a future series. Changes form v1->v2 * Add function name and error number in error path print (Sekhar) Dependencies: 1. [PATCH v7 0/5] USB:

RE: [PATCH 4.8 12/67] mfd: intel-lpss: Do not put device in reset state on suspend

Hi Greg, Please pick this patch. No concerns. Regards, Azhar Shaikh -Original Message- From: Greg Kroah-Hartman [mailto:gre...@linuxfoundation.org] Sent: Thursday, November 24, 2016 7:27 AM To: linux-kernel@vger.kernel.org Cc: Greg Kroah-Hartman ;

[PATCH 4.8 34/67] clk: mmp: pxa910: fix return value check in pxa910_clk_init()

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit 10f2bfb092e3b49000526c02cfe8b2abbbdbb752 upstream. Fix the retrn value check which testing the wrong variable in pxa910_clk_init(). Fixes:

[PATCH 4.8 35/67] clk: mmp: pxa168: fix return value check in pxa168_clk_init()

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Wei Yongjun commit deab07261d54b4db7b627d38e0efac97f176c6d6 upstream. Fix the retrn value check which testing the wrong variable in pxa168_clk_init(). Fixes:

[PATCH 4.8 63/67] IB/uverbs: Fix leak of XRC target QPs

4.8-stable review patch. If anyone has any objections, please let me know. -- From: Tariq Toukan commit 5b810a242c28e1d8d64d718cebe75b79d86a0b2d upstream. The real QP is destroyed in case of the ref count reaches zero, but for XRC target QPs this call was

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