4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit fd2d2b191fe75825c4c7a6f12f3fef35aaed7dd7 upstream.
Signed-off-by: Al Viro
Signed-off-by: Greg Kroah-Hartman
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 43403eabf558d2800b429cd886e996fd555aa542 upstream.
Signed-off-by: Al Viro
Signed-off-by: Greg Kroah-Hartman
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 1c109fabbd51863475cd12ac206bdd249aee35af upstream.
get_user_ex(x, ptr) should zero x on failure. It's not a lot of a leak
(at most we are leaking
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit acb2505d0119033a80c85ac8d02dccae41271667 upstream.
... that should zero on faults. Also remove the helpful
logics wrt range truncation copied from
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit e33d1f6f72cc82fcfc3d1fb20c9e3ad83b1928fa upstream.
Signed-off-by: Al Viro
Signed-off-by: Greg Kroah-Hartman
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit aace880feea38875fbc919761b77e5732a3659ef upstream.
Signed-off-by: Al Viro
Signed-off-by: Greg Kroah-Hartman
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 2561d309dfd1555e781484af757ed0115035ddb3 upstream.
it should clear the destination even when access_ok() fails.
Signed-off-by: Al Viro
On Thu, 2016-09-22 at 20:56 +0200, Thomas Gleixner wrote:
> On Thu, 22 Sep 2016, Tim Chen wrote:
> >
> > On Wed, 2016-09-21 at 22:30 +0200, Rafael J. Wysocki wrote:
> > >
> > > My current understanding is that we need to rebuild sched domains
> > > after setting the priorities,
> > No, that's
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lee Jones
commit 7e9d2850a8db4e0d85a20bb692198bf2cc4be3b7 upstream.
The STiH4{07,10} platform contains some interconnect clocks which are used
by various IPs. If this
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Daney
commit 1423661fed2c40d6d71b5e2e3aa390f85157f9d5 upstream.
The ethtool_ops .get_regs function attempts to read the nonexistent
register
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Andrew Donnellan
commit 6f38a8b9a45833495dc878c335c5431cd98a16ed upstream.
When cxl removes a vPHB, it's possible that the pci_controller may be freed
before all
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Icenowy Zheng
commit 486095fae3a8a6b1ae07c51844699d9bd5cfbebc upstream.
PG8, PG9 is said to be the CTS/RTS pins for UART1 according to the A23/33
datasheets. However, the
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Daniele Palmas
commit f190fd92458da3e869b4e2c6289e2c617490ae53 upstream.
This patch adds support for Infineon flashloader 0x8087/0x0801.
The flashloader is used in Telit
From: Markus Elfring
Date: Thu, 22 Sep 2016 14:30:12 +0200
Adjust jump labels according to the current Linux coding style convention.
Signed-off-by: Markus Elfring
---
drivers/gpu/drm/ttm/ttm_page_alloc.c | 10 --
1 file
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Ard Biesheuvel
commit 0bd2223594a4dcddc1e34b15774a3a4776f7749e upstream.
When calling .import() on a cryptd ahash_request, the structure members
that describe the
Hello,
I just spent three hours studying TOT scheduler code, and I am leaning
towards that this patch being no longer relevant (or being never
relevant, really).
If it ever fixed a real issue, I think it fixed it incorrectly. However, I would
love to understand what exactly we were seeing and why
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mikulas Patocka
commit a5d60783df61fbb67b7596b8a0f6b4b2e05251d5 upstream.
Move log_one_block()'s atomic_inc(>io_blocks) before bio_alloc() to
fix a bug that the target
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Pawel Moll
commit b928466b2169e061822daad48ecf55b005445547 upstream.
The code setting XP watchpoint comparator and mask registers should, in
order to be fully compliant
On Thu, Sep 22, 2016 at 04:40:50PM +0200, Oliver Neukum wrote:
> OK. Strange. Please do
>
> dmesg -c
> echo 9 > /proc/sysrq-trigger
> modprobe cdc_acm
> echo "module cdc_acm +mpf" > /sys/kernel/debug/dynamic_debug/control
>
> [plug your device in]
>
> and provide the full output of dmesg after
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Pawel Moll
commit b7c1beb278e8e3dc664ed3df3fc786db126120a9 upstream.
Fuzzing the CCN perf driver revealed a small but definitely dangerous
mistake in the event setup code.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lee Jones
commit 78567f135d9bbbaf4538f63656d3e4d957c35fe9 upstream.
The STiH4{07,10} platform contains some interconnect clocks which are used
by various IPs. If these
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Pawel Moll
commit 4e486cba285ff06a1f28f0fc2991dde1482d1dcf upstream.
The "Miscellaneous Node" fell through cracks of node initialisation,
as its ID is shared with HN-I.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: James Hartley
commit a32ac2912f97d7ea9b67eb67bb4aa30b9156a88e upstream.
A previous patch attempted to fix the pinmuxes for mfio 84 - 89, but it
omitted a change to
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mukesh Ojha
commit a9cbf0b2195b695cbcaa4e2770948c212e9a upstream.
In a situation, where Linux kernel gets notified about duplicate error log
from OPAL, it is
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Tejun Heo
commit df6a58c5c5aa8ecb1e088ecead3fa33ae70181f1 upstream.
kernfs_notify_workfn() sends out file modified events for the
scheduled kernfs_nodes. Because the
From: Markus Elfring
Date: Thu, 22 Sep 2016 19:00:01 +0200
Several update suggestions were taken into account
from static source code analysis.
Markus Elfring (14):
Use kmalloc_array() in two functions
Rename a jump label in ttm_alloc_new_pages()
Rename jump
On Wed, 2016-09-21 at 22:33 +0200, Rafael J. Wysocki wrote:
> On Wed, Sep 21, 2016 at 9:19 PM, Srinivas Pandruvada
> wrote:
> >
> > From: Tim Chen
> >
> > Some Intel cores in a package can be boosted to a higher turbo frequency
>
Hi Laura,
> Running with KASAN produces some messages:
>
> BUG: KASAN: use-after-free in ti_st_send_frame+0x9c/0x16c at addr
> ffc064868fe8
> Read of size 1 by task kworker/u17:1/1266
>
>
>
> Hardware name: HiKey Development Board (DT)
> Workqueue: hci0 hci_cmd_work
> Call trace:
> []
On 09/22/2016 09:34 AM, Thomas Gleixner wrote:
On Thu, 22 Sep 2016, Peter Zijlstra wrote:
I'd leave out the TO part entirely (or only mention it in changelogs).
That is, I'd call the futex ops: FUTEX_LOCK and FUTEX_UNLOCK.
That brings me to a different question:
How is user space going to
On 09/22/16 19:28, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.22 release.
> There are 118 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
Greg,
did you
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 8ae95ed4ae5fc7c3391ed668b2014c9e2079533b upstream.
Acked-by: James Hogan
Signed-off-by: Al Viro
removed a space after a cast to obtain the coding style.
Signed-off-by: Jannik Becher
---
drivers/staging/wlan-ng/p80211req.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/staging/wlan-ng/p80211req.c
b/drivers/staging/wlan-ng/p80211req.c
On Thu, Sep 22, 2016 at 02:04:27PM -0500, Tom Lendacky wrote:
> That's not what I mean here. If the BIOS sets the SMEE bit in the
> SYS_CFG msr then, even if the encryption bit is never used, there is
> still a reduction in physical address space.
I thought that reduction is the reservation of
Commit-ID: dc6db24d2476cd09c0ecf2b8d80313539f737a89
Gitweb: http://git.kernel.org/tip/dc6db24d2476cd09c0ecf2b8d80313539f737a89
Author: Gu Zheng
AuthorDate: Thu, 25 Aug 2016 16:35:18 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 21 Sep
Commit-ID: 8e089eaa1999def4bb954caa91941f29b0672b6a
Gitweb: http://git.kernel.org/tip/8e089eaa1999def4bb954caa91941f29b0672b6a
Author: Dou Liyang
AuthorDate: Thu, 25 Aug 2016 16:35:19 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 21
Commit-ID: 8ad893faf2eaedb710a3073afbb5d569df2c3e41
Gitweb: http://git.kernel.org/tip/8ad893faf2eaedb710a3073afbb5d569df2c3e41
Author: Gu Zheng
AuthorDate: Thu, 25 Aug 2016 16:35:17 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 21 Sep
Commit-ID: 2532fc318db0e1fe68e01407ee27634c76916e44
Gitweb: http://git.kernel.org/tip/2532fc318db0e1fe68e01407ee27634c76916e44
Author: Tang Chen
AuthorDate: Thu, 25 Aug 2016 16:35:14 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 21 Sep
On 09/22/2016 11:12 AM, Dave Hansen wrote:
> On 09/22/2016 09:29 AM, Gerald Schaefer wrote:
>> static void dissolve_free_huge_page(struct page *page)
>> {
>> +struct page *head = compound_head(page);
>> +struct hstate *h = page_hstate(head);
>> +int nid = page_to_nid(head);
>> +
>>
On Thu, Sep 22, 2016 at 07:28:01PM +0200, Thomas Gleixner wrote:
> I'm not blaming you, but I blame the responsible persons inside your
> company who task you with that and expect that I'm going to do their work
> of explaining to you how that code works.
> @Arnd, @Mark: I'm starting to get
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johan Hovold
commit 153b58ea932b2d0642fa5cd41c93bb0555f3f09b upstream.
The gpmc ranges property for NAND at CS0 was being overridden by later
includes that defined gpmc
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Gregor Boirie
commit 171c0091837c81ed5c949fec6966bb5afff2d1cf upstream.
7985e7c100 ("iio: Introduce a new fractional value type") introduced a
new IIO_VAL_FRACTIONAL
This is the start of the stable review cycle for the 4.4.22 release.
There are 118 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be made by Sat Sep 24 17:29:17 UTC 2016.
Anything
Hi Ying,
On Tue, Sep 20, 2016 at 10:01:30AM +0800, Huang, Ying wrote:
> It appears all patches other than [10/10] in the series is used by the
> last patch [10/10], directly or indirectly. And Without [10/10], they
> don't make much sense. So you suggest me to use one large patch?
> Something
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mateusz Guzik
commit 5efc244346f9f338765da3d592f7947b0afdc4b5 upstream.
Prior to the change the function would blindly deference mm, exe_file
and exe_file->f_inode, each of
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Biggers
commit 163ae1c6ad6299b19e22b4a35d5ab24a89791a98 upstream.
On an ext4 or f2fs filesystem with file encryption supported, a user
could set an encryption policy
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nicholas Piggin
commit cc7786d3ee7e3c979799db834b528db2c0834c2e upstream.
tabort_syscall runs with RI=1, so a nested recoverable machine
check will load the paca into r13
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jason Gunthorpe
commit d1e09f304a1d9651c5059ebfeb696dc2effc9b32 upstream.
Fixes an oops that might happen if uverbs_close races with
remove_one.
Both contexts
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Jon Paul Maloy
commit c7cad0d6f70cd4ce8644ffe528a4df1cdc2e77f5 upstream.
In commit 5cbb28a4bf65c7e4 ("tipc: linearize arriving NAME_DISTR
and LINK_PROTO buffers") we
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Zefan Li
commit 06f4e94898918bcad00cdd4d349313a439d6911e upstream.
A new task inherits cpus_allowed and mems_allowed masks from its parent,
but if someone changes cpuset's
On Thu, Sep 22, 2016 at 08:13:01PM +0200, Boris Brezillon wrote:
> So, there are 2 different problems here:
> 1/ the board no longer boots because of commit 87248991a1de and a
>missing entry in the voltage table
> 2/ claiming the PWM pins at probe time can cause glitches
> I'm currently
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Olof Johansson
commit 1c500840934a138bd6b13556c210516e9301fbee upstream.
In at least one known setup, the chip comes up in a state where reading
the chip ID returns garbage
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lars-Peter Clausen
commit 7d3cc21dab5313a02f2f3ca8164529b828a030d1 upstream.
The data buffer for captured mode for the ad799x driver is allocated in the
update_scan_mode()
From: Markus Elfring
Date: Thu, 22 Sep 2016 14:00:31 +0200
* Multiplications for the size determination of memory allocations
indicated that array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Suzuki K Poulose
commit 293f293637b55db4f9f522a5a72514e98a541076 upstream.
On arm/arm64, we depend on the kvm_unmap_hva* callbacks (via
mmu_notifiers::invalidate_*) to
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Chen-Yu Tsai
commit b53e7d000d9e6e9fd2c6eb6b82d2783c67fd599e upstream.
The bootloader (U-boot) sometimes uses this timer for various delays.
It uses it as a ongoing counter, and
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Caesar Wang
commit 543852af8e5902aee8f7c72c89e1513663e0f696 upstream.
SARADC controller needs to be reset before programming it, otherwise
it will not function properly.
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Walleij
commit 7ac61a062f3147dc23e3f12b9dfe7c4dd35f9cb8 upstream.
Any readings from the raw interface of the KXSD9 driver will
return an empty string, because
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Anders Darander
commit c2ab447454d498e709d9011c0f2d2945ee321f9b upstream.
The driver always assumes that an input device has been created when
reading channel 3. This
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Vignesh R
commit 90c43ec6997a892448f1f86180a515f59cafd8a3 upstream.
It is possible that two or more ADC channels can be simultaneously
requested for raw samples, in which case
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Vignesh R
commit 7175cce1c3f1d8c8840d2004f78f96a3904249b5 upstream.
Now that open delay and sample delay for each channel is configurable
via DT, the default IDLE_TIMEOUT
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Emanuel Czirai
commit d1992996753132e2dafe955cccb2fb0714d3cfc4 upstream.
AMD F12h machines have an erratum which can cause DIV/IDIV to behave
unpredictably. The
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mike Snitzer
commit 299f6230bc6d0ccd5f95bb0fb865d80a9c7d5ccc upstream.
v4.8-rc3 commit 99f3c90d0d ("dm flakey: error READ bios during the
down_interval") overlooked the
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alison Schofield
commit f8adf645db03345af2d9a8b6095b02327ea50885 upstream.
Use the iio_pollfunc_store_time parameter during triggered buffer
set-up to get valid
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Chuck Lever
commit 885848186fbc2d1d8fb6d2fdc2156638ae289a46 upstream.
nfsd4_release_lockowner finds a lock owner that has no lock state,
and drops cl_lock. Then
On Wed, Sep 21, 2016 at 8:43 PM, Qiang Zhao wrote:
> On Mon, Sep 22, 2016 at 2:19 AM, Leo Li wrote:
>> -Original Message-
>> From: Leo Li [mailto:pku@gmail.com]
>> Sent: Thursday, September 22, 2016 2:19 AM
>> To: Qiang Zhao
>> Cc: Scott Wood
Commit-ID: fd74da217df7d4bd25e95411da64e0b92762842e
Gitweb: http://git.kernel.org/tip/fd74da217df7d4bd25e95411da64e0b92762842e
Author: Dou Liyang
AuthorDate: Thu, 25 Aug 2016 16:35:20 +0800
Committer: Thomas Gleixner
CommitDate: Wed, 21
On 09/22/2016 12:21 AM, Davidlohr Bueso wrote:
On Sun, 18 Sep 2016, Manfred Spraul wrote:
Just as with msgrcv (along with the rest of sysvipc since a few years
ago), perform the security checks without holding the ipc object
lock.
Thinking about it: isn't this wrong?
CPU1:
* msgrcv()
*
Em Thu, Sep 22, 2016 at 01:23:04PM -0500, Paul Clarke escreveu:
> On 09/22/2016 12:50 PM, Vineet Gupta wrote:
> >On 09/22/2016 12:56 AM, Peter Zijlstra wrote:
> >>On Wed, Sep 21, 2016 at 07:43:28PM -0500, Paul Clarke wrote:
> >>>On 09/20/2016 03:56 PM, Vineet Gupta wrote:
> On 09/01/2016 01:33
On Thu, Sep 22, 2016 at 08:50:54AM +0200, Richard Weinberger wrote:
> ...otherwise an user can enable encryption for certain files even
> when the filesystem is unable to support it.
> Such a case would be a filesystem created by mkfs.ext4's default
> settings, 1KiB block size. Ext4 supports
On 09/22/2016 02:11 PM, Borislav Petkov wrote:
> On Thu, Sep 22, 2016 at 02:04:27PM -0500, Tom Lendacky wrote:
>> That's not what I mean here. If the BIOS sets the SMEE bit in the
>> SYS_CFG msr then, even if the encryption bit is never used, there is
>> still a reduction in physical address
Under swapping load on huge tmpfs, /proc/meminfo's Committed_AS grows
bigger and bigger: just a cosmetic issue for most users, but disabling
for those who run without overcommit (/proc/sys/vm/overcommit_memory 2).
shmem_uncharge() was forgetting to unaccount __vm_enough_memory's charge,
and
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit facc432faa59414bd7c60c307ff1645154a66c98 upstream.
The napi_synchronize() function is defined twice: The definition
for SMP builds waits for other CPUs to
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 9ad18b75c2f6e4a78ce204e79f37781f8815c0fa upstream.
both for access_ok() failures and for faults halfway through
Signed-off-by: Al Viro
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit b615e3c74621e06cd97f86373ca90d43d6d998aa upstream.
Signed-off-by: Al Viro
Signed-off-by: Greg Kroah-Hartman
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit c2f18fa4cbb3ad92e033a24efa27583978ce9600 upstream.
* should zero on any failure
* __get_user() should use __copy_from_user(), not copy_from_user()
On Thu, 22 Sep 2016, Tim Chen wrote:
> On Wed, 2016-09-21 at 22:30 +0200, Rafael J. Wysocki wrote:
> > My current understanding is that we need to rebuild sched domains
> > after setting the priorities,
>
> No, that's not true. We need to rebuild the sched domains only
> when the sched domain
From: Markus Elfring
Date: Thu, 22 Sep 2016 14:48:39 +0200
* Multiplications for the size determination of memory allocations
indicated that array data structure should be processed.
Thus use the corresponding function "kmalloc_array".
This issue was
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit e69d700535ac43a18032b3c399c69bf4639e89a2 upstream.
Signed-off-by: Al Viro
Signed-off-by: Greg Kroah-Hartman
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 8f035983dd826d7e04f67b28acf8e2f08c347e41 upstream.
Signed-off-by: Al Viro
Signed-off-by: Greg Kroah-Hartman
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit c6852389228df9fb3067f94f3b651de2a7921b36 upstream.
It could be done in exception-handling bits in __get_user_b() et.al.,
but the surgery involved would
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Colin Ian King
commit 5dba4b14bafe801083d01e1f400816df7e5a8f2e upstream.
A recent fix to iio_buffer_read_first_n_outer removed ret from being set by
a return from
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Linus Torvalds
commit 166c5a6ef765653848161e6f4af81c05e4b3ecf6 upstream.
In commit e45708976aea ("drm/dp-helper: Move the legacy helpers to
gma500") the legacy
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alan Stern
commit 08c5cd37480f59ea39682f4585d92269be6b1424 upstream.
Some full-speed mceusb infrared transceivers contain invalid endpoint
descriptors for their
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 8630c32275bac2de6ffb8aea9d9b11663e7ad28e upstream.
really ugly, but apparently avr32 compilers turns access_ok() into
something so bad that they want it
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Wei Yongjun
commit 751eb6b6042a596b0080967c1a529a9fe98dac1d upstream.
In general, when DAD detected IPv6 duplicate address, ifp->state
will be set to
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Yoshihiro Shimoda
commit 519d8bd4b5d3d82c413eac5bb42b106bb4b9ec15 upstream.
The previous driver is possible to stop the transfer wrongly.
For example:
1) An
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Mason
commit cbd60aa7cd17d81a434234268c55192862147439 upstream.
We use a btrfs_log_ctx structure to pass information into the
tree log commit, and get error values out. It
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Balbir Singh
commit 135e8c9250dd5c8c9aae5984fde6f230d0cbfeaf upstream.
The origin of the issue I've seen is related to
a missing memory barrier between check for
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Mathias Nyman
commit bcf42aa60c2832510b9be0f30c090bfd35bb172d upstream.
The stop endpoint command has its own 5 second timeout timer.
If the timeout function is
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Miklos Szeredi
commit 8fba54aebbdf1f999738121922e74bf796ad60ee upstream.
When reading from a loop device backed by a fuse file it deadlocks on
lock_page().
This is
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Clemens Gruber
commit 6f3c4fb6d05e63c9c6d8968302491c3a5457be61 upstream.
Problems with the signal integrity of the high speed USB data lines or
noise on reference
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Johannes Berg
commit 4d0bd46a4d55383f7b925e6cf7865a77e0f0e020 upstream.
This reverts commit 3d5fdff46c4b2b9534fa2f9fc78e90a48e0ff724.
Ben Hutchings pointed out that
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Guoqing Jiang
commit 47a7b0dc04c9746812820b6e60553cc77bbc upstream.
The md-cluster is compiled as module by default,
if it is compiled by built-in way, then we can't
make
On 09/22/2016 12:07 PM, Borislav Petkov wrote:
> On Thu, Sep 22, 2016 at 05:05:54PM +0200, Paolo Bonzini wrote:
>> Which paragraph?
>
> "Linux relies on BIOS to set this bit if BIOS has determined that the
> reduction in the physical address space as a result of enabling memory
> encryption..."
>
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Felix Fietkau
commit 7711aaf08ad3fc4d0e937eec1de0a63620444ce7 upstream.
A station pointer can be passed to the driver on tx, before it has been
marked as associated. Since
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git sched/core
head: a18a579e5f84daa74f64b1f1b652b4a6a8d6f8b4
commit: 9af6528ee9b682df7f29dbee86fbba0b67eab944 [44/47] sched/core: Optimize
__schedule()
config: x86_64-randconfig-s1-09230134 (attached as .config)
compiler: gcc-4.4
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arnd Bergmann
commit 00affcac69c7aae6c2cfcbc71f724e1c16d0b445 upstream.
gcc warns about the 'found' variable possibly being used uninitialized:
drivers/soc/qcom/spm.c: In
On 09/22/2016 09:59 AM, Borislav Petkov wrote:
> On Thu, Sep 22, 2016 at 04:45:51PM +0200, Paolo Bonzini wrote:
>> The main difference between the SME and SEV encryption, from the point
>> of view of the kernel, is that real-mode always writes unencrypted in
>> SME and always writes encrypted in
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Al Viro
commit 2e29f50ad5e23db37dde9be71410d95d50241ecd upstream.
a) should not leave crap on fault
b) should _not_ require access_ok() in any cases.
Signed-off-by:
Krzysztof Kozlowski writes:
> On Thu, Sep 22, 2016 at 06:48:35PM +0200, Wolfgang Wiedmeyer wrote:
>> This allows to reboot the device into recovery mode and into the download
>> mode of the bootloader.
>
> Which bootloader? Probably UBoot... or Samsung stock one? Could you put
> that information
1001 - 1100 of 2556 matches
Mail list logo