3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: John Blackwood
commit 5db4fd8c52810bd9740c1240ebf89223b171aa70 upstream.
Make sure to clear out any ptrace singlestep state when a ptra
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Borislav Petkov
commit 12e26969b32c79018165d52caff3762135614aa1 upstream.
I get the splat below when modprobing/rmmoding EDAC drivers.
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Borislav Petkov
commit fcd5c4dd8201595d4c598c9cca5e54760277d687 upstream.
EDAC workqueue destruction is really fragile. We cancel delay
On 02/04/2016 05:43 AM, Greg Kroah-Hartman wrote:
> On Tue, Feb 02, 2016 at 10:34:34PM +0800, Lu Baolu wrote:
>>
>> On 01/26/2016 08:58 PM, Lu Baolu wrote:
>>> Hi,
>>>
>>> This patch series adds support for early printk through USB3 debug port.
>>> USB3 debug port is described in xHCI specificati
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Peter Wu
commit 17bc55864f81dd730d05f09b1641312a7990d636 upstream.
Free skb for received frames with a wrong checksum. This can happen
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Will Deacon
commit 32d6397805d00573ce1fa55f408ce2bca15b0ad3 upstream.
In paging_init, we allocate the zero page, memset it to zero and
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Uri Mashiach
commit 9b2761cb72dc41e1948c8a5512b4efd384eda130 upstream.
The maximum chunks used by the function is
(SPI_AGGR_BUFFER_SIZE
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Will Deacon
commit d8d23fa0f27f3b2942a7bbc7378c7735324ed519 upstream.
We don't want to expose the DCC to userspace, particularly as the
On Thu, Feb 4, 2016 at 12:31 AM, Shilpa Bhat wrote:
> Hi,
>
> On 02/03/2016 10:50 PM, Rafael J. Wysocki wrote:
>> On Wed, Feb 3, 2016 at 6:20 PM, Juri Lelli wrote:
>>> On 03/02/16 21:40, Viresh Kumar wrote:
On 03-02-16, 15:54, Juri Lelli wrote:
> Ouch, I've just got this executing -f bas
Lubomir Rintel writes:
> diff --git a/arch/arm/boot/dts/bcm2835-rpi-b-plus.dts
> b/arch/arm/boot/dts/bcm2835-rpi-b-plus.dts
> index ef54050..32bbd2a 100644
> --- a/arch/arm/boot/dts/bcm2835-rpi-b-plus.dts
> +++ b/arch/arm/boot/dts/bcm2835-rpi-b-plus.dts
Hi,
Shouldn't this be common to all RPi1
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Nikolay Borisov
commit 18d03e8c25f173f4107a40d0b8c24defb6ed69f3 upstream.
When a thin pool is being destroyed delayed work items are
ca
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Alex Deucher
commit 0eb1c3d4084eeb6fb3a703f88d6ce1521f8fcdd1 upstream.
Combine the two quirks.
bug:
https://bugzilla.kernel.org/show_b
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Adrian Hunter
commit 5c671c410c8704800f4f1673b6f572137e7e6ddd upstream.
sdhci has a legacy facility to prevent runtime suspend if the
b
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Adrian Hunter
commit d9bfbb95ed598a09cf336adb0f190ee0ff802f0d upstream.
The 'ocr' parameter passed to mmc_set_signal_voltage()
defines
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Mike Snitzer
commit 512167788a6fe9481a33a3cce5f80b684631a1bb upstream.
Remove the unused struct block_op pointer that was inadvertantly
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Thomas Gleixner
commit fb75a4282d0d9a3c7c44d940582c2d226cf3acfb upstream.
If the proxy lock in the requeue loop acquires the rtmutex fo
On Wed, 3 Feb 2016, Michal Hocko wrote:
> From: Michal Hocko
>
> This is based on the idea from Mel Gorman discussed during LSFMM 2015 and
> independently brought up by Oleg Nesterov.
>
> The OOM killer currently allows to kill only a single task in a good
> hope that the task will terminate in
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Larry Finger
commit b24f19f16b9e43f54218c07609b783ea8625406a upstream.
The module parameter for software encryption was never transferr
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Lorenzo Pieralisi
commit 60792ad349f3c6dc5735aafefe5dc9121c79e320 upstream.
The pmuserenr_el0 register value is architecturally UNKNOWN
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Trond Myklebust
commit 762674f86d0328d5dc923c966e209e1ee59663f2 upstream.
Donald Buczek reports that a nfs4 client incorrectly denies
e
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Al Viro
commit 4d4d8573a8451acc9f01cbea24b7e55f04a252fe upstream.
Signed-off-by: Al Viro
Tested-by: Joshua Schmid
Tested-by: Eric Whe
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Kent Overstreet
commit c5f1e5adf956e3ba82d204c7c141a75da9fa449a upstream.
Signed-off-by: Takashi Iwai
Tested-by: Eric Wheeler
Cc: Ken
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Zheng Liu
commit fecaee6f20ee122ad75402c53d8278f9bb142ddc upstream.
This bug can be reproduced by the following script:
#!/bin/bash
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Trond Myklebust
commit ade14a7df796d4e86bd9d181193c883a57b13db0 upstream.
If a NFSv4 client uses the cache_consistency_bitmask in order
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Zheng Liu
commit 2ef9ccbfcb90cf84bdba320a571b18b05c41101b upstream.
Subject : [PATCH v2] bcache: fix a livelock in btree lock
Dat
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Andrew Elble
commit 361cad3c89070aeb37560860ea8bfc092d545adc upstream.
We've seen this in a packet capture - I've intermixed what I
thi
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Gabriel de Perthuis
commit d7076f21629f8f329bca4a44dc408d94670f49e2 upstream.
Allows to use register, not register_quiet in udev to avo
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Richard Cochran
commit 1b9f23727abb92c5e58f139e7d180befcaa06fe0 upstream.
The posix_clock_poll function is supposed to return a bit mas
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Zheng Liu
commit 2ecf0cdb2b437402110ab57546e02abfa68a716b upstream.
In bcache_init() function it forgot to unregister reboot notifier i
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Stefan Bader
commit 8d16ce540c94c9d366eb36fc91b7154d92d6397b upstream.
Added a safeguard in the shutdown case. At least while not being
From: Rafael J. Wysocki
The struct cpu_common_dbs_info structure represents the per-policy
part of the governor data (for the ondemand and conservative
governors), but its name doesn't reflect its purpose.
Rename it to struct policy_dbs_info and rename variables related to
it accordingly.
No fu
The phy-am335x driver selects 'USB_COMMON', but all other drivers
use 'depends on' for that symbol, and it depends on USB || USB_GADGET
itself, which causes a Kconfig warning:
warning: (AM335X_PHY_USB) selects USB_COMMON which has unmet direct
dependencies (USB_SUPPORT && (USB || USB_GADGET))
As
From: Rafael J. Wysocki
The ondemand and conservative governors are represented by
struct common_dbs_data whose name doesn't reflect the purpose it
is used for, so rename it to struct dbs_governor and rename
variables of that type accordingly.
No functional changes.
Signed-off-by: Rafael J. Wys
On Wed, Feb 03, 2016 at 11:21:17PM +0100, Krzysztof Adamski wrote:
On Wed, Feb 03, 2016 at 01:35:34PM +0100, Maxime Ripard wrote:
Hi,
I'm not sure what you mean there. The fixed factor clocks only take a
single parent, and you provided two.
True, I that's actually some stupid leftover. As men
From: Rafael J. Wysocki
Since it is possible to obtain a pointer to struct dbs_governor
from a pointer to the struct governor embedded in it via
container_of(), the second argument of cpufreq_governor_init()
is not necessary. Accordingly, cpufreq_governor_dbs() doesn't
need its second argument e
From: Rafael J. Wysocki
For the ondemand and conservative governors (generally, governors
that use the common code in cpufreq_governor.c), there are two static
data structures representing the governor, the struct governor
structure (the interface to the cpufreq core) and the struct
common_dbs_da
From: Rafael J. Wysocki
Do not pass struct dbs_data pointers to the family of functions
implementing governor operations in cpufreq_governor.c as they can
take that pointer from policy->governor by themselves.
The cpufreq_governor_init() case is slightly more complicated, since
policy->governor
From: Rafael J. Wysocki
Since it is possible to obtain a pointer to struct dbs_governor
from a pointer to the struct governor embedded in it with the help
of container_of(), the additional gov pointer in struct dbs_data
isn't really necessary.
Drop that pointer and make the code using it reach t
From: Rafael J. Wysocki
If the ondemand and conservative governors cannot use per-policy
tunables (CPUFREQ_HAVE_GOVERNOR_PER_POLICY is not set in the cpufreq
driver), all policy objects point to the same single dbs_data object.
Additionally, that object is pointed to by a global pointer hidden in
Hi,
A few days ago I looked at the common code used by the ondemand and conservative
governors because of the deadlock issue that Viresh has addressed recently
(http://marc.info/?l=linux-pm&m=145450832814058&w=4) and it occurred to me
that the whole thing was really too tangled and might be made e
From: Rafael J. Wysocki
The preprocessor magic used for setting the default cpufreq governor
(and for using the performance governor as a fallback one for that
matter) is really nasty, so replace it with __weak functions and
overrides.
Signed-off-by: Rafael J. Wysocki
---
drivers/cpufreq/cpufr
On Thu, Feb 04, 2016 at 12:15:50AM +0200, Felipe Balbi wrote:
>> Since I've now been bitten by this several times: Is there any sort of best
>> practice for integrating git with MUAs? What I'm doing right now is
>> cut-and-paste from mutt to get the to/cc/in-reply-to headers right, and
>> that's su
From: Rafael J. Wysocki
The struct policy_dbs_info objects representing per-policy governor
data are not accessible directly from the corresponding policy
objects. To access them, one has to get a pointer to the
struct cpu_dbs_info of policy->cpu and use the "shared" field of
that which isn't re
On Wed, Feb 03, 2016 at 03:11:56PM -0500, Boris Ostrovsky wrote:
> On 02/03/2016 01:55 PM, Luis R. Rodriguez wrote:
> >I saw no considerations for the recommendations I had made last on your v1:
> >
> >https://lkml.kernel.org/r/CAB=NE6XPA0YzbnM8=rspkkai6d3gkxxo00gr0vzuyoyzny6...@mail.gmail.com
> >
From: Rafael J. Wysocki
Since policy->cpu is always passed as the second argument to
dbs_check_cpu(), it is not really necessary to pass it, because
the function can obtain that value via its first argument just fine.
Signed-off-by: Rafael J. Wysocki
---
drivers/cpufreq/cpufreq_conservative.c
From: Rafael J. Wysocki
Every governor relying on the common code in cpufreq_governor.c
has to provide its own mutex in struct common_dbs_data. However,
those mutexes are never used at the same time and doing it this
way makes it rather difficult to follow the code. Moreover,
if two governor mo
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Kent Overstreet
commit 627ccd20b4ad3ba836472468208e2ac4dfadbf03 upstream.
Previously, it would only scan the entire disk if it was star
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Larry Finger
commit d4d60b4caaa5926e1b243070770968f05656107a upstream.
Two of the module parameters are listed with incorrect default v
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: =?UTF-8?q?Aur=C3=A9lien=20Francillon?=
commit dd0d0d4de582a6a61c032332c91f4f4cb2bab569 upstream.
Without i8042.nomux=1 the Elantech tou
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Uri Mashiach
commit e47301b06d5a65678690f04c2248fd181db1e59a upstream.
Fix the below Oops when trying to modprobe wlcore_spi.
The oops
I hadn't noticed that one - my testcase didn't encounter any issues on
AMD. Anyways, it's probably best to revert that change as well. I'll add
that in for a v2.
Bruce
>>> On 2/3/2016 at 04:18 PM, Nadav Amit wrote:
> Oops.
>
> Anyhow, I see my patch has done a similar change in init_vmcb() , so
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Larry Finger
commit 7503efbd82c15c4070ad1344e5169d3634b4 upstream.
Two of the module parameter descriptions show incorrect default
On Thu, 2016-02-04 at 00:29 +0100, Jason A. Donenfeld wrote:
> This patch adds a variable 'a' which indicates that the 'p',
> 'f', and 's' options should be toggled on or off depending on
> whether or not those parameters are actually valid inside the
> passed sockaddr.
trivia:
> diff --git a/lib
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: "Darrick J. Wong"
commit 96f859d52bcb1c6ea6f3388d39862bf7143e2f30 upstream.
Because struct xfs_agfl is 36 bytes long and has a 64-bit i
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Andrew Gabbasov
commit ad402b265ecf6fa22d04043b41444cdfcdf4f52d upstream.
udf_CS0toUTF8 function stops the conversion when the output b
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Christoph Biedl
commit 3460baa620685c20f5ee19afb6d99d26150c382c upstream.
Commit 36e097a8a297 ("PCI: Split out bridge window override o
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Andrew Gabbasov
commit bb00c898ad1ce40c4bb422a8207ae562e9aea7ae upstream.
If a name contains at least some characters with Unicode valu
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Larry Finger
commit b68d0ae7e58624c33f2eddab471fee55db27dbf9 upstream.
This driver fails to copy the module parameter for software encr
sunxi_pmx_set accepts pin number and then calculates offset by
subtracting pin_base from it. sunxi_pinctrl_gpio_get, on the other hand,
gets offset so we have to convert it to pin number so we won't get
negative value in sunxi_pmx_set.
This was only used on A10 so far, where there is only one GPIO
Add the corresponding device node for R_PIO on H3 to the dtsi. Support
for the controller was added in earlier commit.
Signed-off-by: Krzysztof Adamski
---
arch/arm/boot/dts/sun8i-h3.dtsi | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi b/arch/arm
H3 has additional PIO controller similar to what we can find on A23.
It's a 12 pin port, described in H3 Datasheet rev 1.1, pages 345-350.
Signed-off-by: Krzysztof Adamski
---
.../bindings/pinctrl/allwinner,sunxi-pinctrl.txt | 1 +
drivers/pinctrl/sunxi/Kconfig | 4 +
Em Mon, Jan 25, 2016 at 09:56:00AM +, Wang Nan escreveu:
> From: He Kuang
>
> This patch is useful when trying to pass a perf event to BPF map.
> Before this patch we are unable to pass an event with config term to
> BPF maps. For example:
>
> # perf record -a -e cycles/no-inherit,period=0x
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Oren Givon
commit 006bda75d81fd27a583a3b310e9444fea2aa6ef2 upstream.
Update and fix some 7265 PCI IDs entries.
Signed-off-by: Oren Giv
This patch adds support for APB0 in H3. It seems to be compatible with
earlier SOCs. apb0 gates controls R_ block peripherals (R_PIO, R_IR,
etc).
Signed-off-by: Krzysztof Adamski
---
Documentation/devicetree/bindings/clock/sunxi.txt | 1 +
drivers/clk/sunxi/clk-simple-gates.c | 2 ++
On Tue, 2 Feb 2016, Dmitry Vyukov wrote:
> If the following program run in a parallel loop, eventually it leaves
> hanged uninterruptable tasks on mmap_sem.
I am now able to reproduce the issue and will be looking into it.
[ .. snip .. ]
> // autogenerated by syzkaller (http://github.com/google/
This patch series is extension of my original single patch with the same
subject. It adds support for R_PIO so that GPIO port L can be used in H3
based devices. It was tested on OrangePi PC where PL is connected amount
others to an onboard led, a switch, an IR receiver and some VCC
controllers.
Pa
APB0 is bearly mentioned in H3 User Manual and it is only setup in the
Allwinners kernel dump for CIR. I have verified experimentally that the
gate for R_PIO exists and works, though. There are probably other gates
there but I don't know their order right now and I don't have access to
their periph
On 2016-02-03 06:04, Thierry Reding wrote:
> On Wed, Jan 27, 2016 at 06:46:50PM -0800, Stefan Agner wrote:
> [...]
>> On 2015-11-18 18:42, Stefan Agner wrote:
> [...]
>> > diff --git a/drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c
> [...]
>> > @@ -89,6 +91,15 @@ static void fsl_dcu_drm_crtc_mode_set_n
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vegard Nossum
commit 9f2dfda2f2f1c6181c3732c16b85c59ab2d195e0 upstream.
An inverted return value check in hostfs_mknod() caused the fun
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vegard Nossum
commit 0754fb298f2f2719f0393491d010d46cfb25d043 upstream.
I was seeing some really weird behaviour where piping UML's out
Sorry for spamming. The correct fix appears to reload the DRs (set
KVM_DEBUGREG_RELOAD) in kvm_arch_vcpu_load .
(for me it works)
Regards,
Nadav
Nadav Amit wrote:
> I think the problem lies here:
>
>/*
> * If the guest has used debug registers, at least dr7
> * will
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Mikulas Patocka
commit 385277bfb57faac44e92497104ba542cdd82d5fe upstream.
When there is an error copying a chunk dm-snapshot can incorr
The PAPR defines four valid header values for the first byte of a
CRQ message. Namely, an unused/empty message (0x00), a valid
command/response entry (0x80), a valid initialization entry (0xC0),
and a transport event (0xFF). Define these values as enums and use
them in the code in place of their ma
The enum values for VIOSRP_LINUX_FORMAT and VIOSRP_INLINE_FORMAT are
off by one. They are currently defined as 0x06 and 0x07 respetively.
These values are defined in PAPR correctly as 0x05 and 0x06. This
inconsistency has gone unnoticed as neither enum is currently used.
The possible future support
Hi,
On 02/03/2016 10:50 PM, Rafael J. Wysocki wrote:
> On Wed, Feb 3, 2016 at 6:20 PM, Juri Lelli wrote:
>> On 03/02/16 21:40, Viresh Kumar wrote:
>>> On 03-02-16, 15:54, Juri Lelli wrote:
Ouch, I've just got this executing -f basic on Juno. :(
It happens with the hotplug_1_by_1 test.
>
The root node of the OF device tree is exported as of_root. No need
to look up the root by path name. Instead just get a reference
directly via of_root.
Signed-off-by: Tyrel Datwyler
---
drivers/scsi/ibmvscsi/ibmvscsi.c | 14 ++
1 file changed, 6 insertions(+), 8 deletions(-)
diff -
A VIOSRP_HOST_CONFIG_TYPE management datagram (MAD) has existed in
the code for some time. From what information I've gathered from
Brian King this was likely implemented on the host side in a SLES 9
based VIOS, which is no longer supported anywhere. Further, it is
not defined in PAPR or supported
Add defines for mad version and mad os_type, and replace the magic
numbers in set_adapter_info() accordingly.
Signed-off-by: Tyrel Datwyler
---
drivers/scsi/ibmvscsi/ibmvscsi.c | 4 ++--
drivers/scsi/ibmvscsi/viosrp.h | 2 ++
2 files changed, 4 insertions(+), 2 deletions(-)
diff --git a/drive
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Grygorii Strashko
commit 8ff0ef996ca00028519c70e8d51d32bd37eb51dc upstream.
On -RT and if kernel is booting with "threadirqs" cmd line
The values returned by the show functions for the host os_type,
mad_version, and partition_number attributes get their values
directly from the madapter_info struct whose associated fields are
__be32 typed. Added endian conversion to ensure these values are
sane on LE platforms.
Signed-off-by: Tyr
This patch adds a variable 'a' which indicates that the 'p',
'f', and 's' options should be toggled on or off depending on
whether or not those parameters are actually valid inside the
passed sockaddr.
Signed-off-by: Jason A. Donenfeld
---
Documentation/printk-formats.txt | 6 --
lib/vsprin
Fixed up a couple spots that were out of line with the PAPR in regards
to its defined VSCSI protocol. Did away with some magic numbers directly
in the code. Fixed a minor endian issue.
Tyrel Datwyler (6):
ibmvscsi: Correct values for several viosrp_crq_format enums
ibmvscsi: Add and use enums
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Ard Biesheuvel
commit bcb7825a77f41c7dd91da6f7ac10b928156a322e upstream.
The normalization pass in the sorting routine of the relative
Em Mon, Jan 25, 2016 at 09:55:56AM +, Wang Nan escreveu:
> bpf__config_obj() is introduced as a core API to config BPF object
> after loading. One configuration option of maps is introduced. After
> this patch BPF object can accept configuration like:
>
> maps:my_map.value=1234
>
> (maps.my_
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Dave Chinner
commit 7d6a13f023567d573ac362502bb702eda716e654 upstream.
When we do dquot readahead in log recovery, we do not use a veri
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Dave Chinner
commit b79f4a1c68bb99152d0785ee4ea3ab4396cdacc6 upstream.
When we do inode readahead in log recovery, we do can do the
rea
Hi Dmitry,
On 02/03/2016 08:26 AM, Dmitry Vyukov wrote:
> On Wed, Feb 3, 2016 at 5:10 PM, Dmitry Vyukov wrote:
>> Hello,
>>
>> The following program causes tty_struct memory leak:
>>
>> // autogenerated by syzkaller (http://github.com/google/syzkaller)
>> #include
>> #include
>> #include
>> #i
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Benjamin Tissoires
commit 6544a1df11c48c8413071aac3316792e4678fbfb upstream.
When using a protocol v2 or v3 hardware, elantech uses the
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Vinod Koul
commit a1068045883ed4a18363a4ebad0c3d55e473b716 upstream.
The detection of direction for compress was only taking into accou
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Roman Volkov
commit f9eccf24615672896dc13251410c3f2f33a14f95 upstream.
The vt8500 clocksource driver declares itself as capable to hand
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Jeff Layton
commit 7f3697e24dc3820b10f445a4a7d914fc356012d1 upstream.
Dmitry reported that he was able to reproduce the WARN_ON_ONCE th
On Mon, 2016-02-01 at 21:29 +0800, Shawn Guo wrote:
[snip]
> > + stmpe_touchscreen {
>
> Shouldn't the node name be generic as just touchscreen? Or at least,
> hyphen instead of underscore should be used in node name.
This one is actually as per binding document example:
Documentati
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Takashi Iwai
commit 030e2c78d3a91dd0d27fef37e91950dde333eba1 upstream.
snd_seq_ioctl_remove_events() calls snd_seq_fifo_clear()
uncondi
On Thu, Feb 4, 2016 at 12:05 AM, Joe Perches wrote:
>
> Doesn't this needs the mask tested?
>
> sa->sin6_flowinfo & IPV6_FLOWINFO_MASK
Good catch. Fixing and will submit another.
>
> given the use of bool, the != 0 are unnecessary.
True.
> Other than that, looks good to me.
Gr
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Helge Deller
commit e60fc5aa608eb38b47ba4ee058f306f739eb70a0 upstream.
On a 64bit kernel build the compiler aligns the _sifields union
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Ulrich Weigand
commit a61674bdfc7c2bf909c4010699607b62b69b7bec upstream.
GCC 6 will include changes to generated code with -mcmodel=lar
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Minchan Kim
commit f68b992bbb474641881932c61c92dcfa6f5b3689 upstream.
During my compaction-related stuff, I encountered a bug
with ball
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Minchan Kim
commit 21ea9fb69e7c4b1b1559c3e410943d3ff248ffcb upstream.
In balloon_page_dequeue, pages_lock should cover the loop
(ie, li
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Linus Walleij
commit 0bcb7efdff63564e80fe84dd36a9fbdfbf6697a4 upstream.
commit 4956e10903fd ("ARM: 6244/1: mmci: add variant data and d
3.16.7-ckt24 -stable review patch. If anyone has any objections, please let me
know.
---8<
From: Mans Rullgard
commit 2895b2cad6e7a95104cf396e5330054453382ae1 upstream.
Cyclic transfer callbacks rely on block completion interrupts w
201 - 300 of 1474 matches
Mail list logo