linux-toradex.git, branch v4.9.3

Linux 4.9.3

2017-01-12T10:41:42+00:00

usb: gadget: composite: always set ep->mult to a sensible value

2017-01-12T10:39:46+00:00

commit eaa496ffaaf19591fe471a36cef366146eeb9153 upstream.

ep->mult is supposed to be set to Isochronous and
Interrupt Endapoint's multiplier value. This value
is computed from different places depending on the
link speed.

If we're dealing with HighSpeed, then it's part of
bits [12:11] of wMaxPacketSize. This case wasn't
taken into consideration before.

While at that, also make sure the ep->mult defaults
to one so drivers can use it unconditionally and
assume they'll never multiply ep->maxpacket to zero.

Signed-off-by: Felipe Balbi 
Signed-off-by: Greg Kroah-Hartman

Revert "usb: gadget: composite: always set ep->mult to a sensible value"

2017-01-12T10:39:46+00:00

This reverts commit eab1c4e2d0ad4509ccb8476a604074547dc202e0 which is
commit eaa496ffaaf19591fe471a36cef366146eeb9153 upstream as it was
incorrectly backported.

Reported-by: Bin Liu 
Cc: Felipe Balbi 
Signed-off-by: Greg Kroah-Hartman

Revert "rtlwifi: Fix enter/exit power_save"

2017-01-12T10:39:45+00:00

This reverts commit 98068574928f499b30f136ff57ef9a03cc575a36, which is
commit ba9f93f82abafe2552eac942ebb11c2df4f8dd7f upstream as it causes
problems.

Reported-by: Dmitry Osipenko 
Cc: Ping-Ke Shih 
Cc: Larry Finger 
Cc: Kalle Valo 
Signed-off-by: Greg Kroah-Hartman gregkh@linuxfoundation.org

tick/broadcast: Prevent NULL pointer dereference

2017-01-12T10:39:45+00:00

commit c1a9eeb938b5433947e5ea22f89baff3182e7075 upstream.

When a disfunctional timer, e.g. dummy timer, is installed, the tick core
tries to setup the broadcast timer.

If no broadcast device is installed, the kernel crashes with a NULL pointer
dereference in tick_broadcast_setup_oneshot() because the function has no
sanity check.

Reported-by: Mason 
Signed-off-by: Thomas Gleixner 
Cc: Mark Rutland 
Cc: Anna-Maria Gleixner 
Cc: Richard Cochran 
Cc: Sebastian Andrzej Siewior 
Cc: Daniel Lezcano 
Cc: Peter Zijlstra ,
Cc: Sebastian Frias 
Cc: Thibaud Cornic 
Cc: Robin Murphy 
Link: http://lkml.kernel.org/r/1147ef90-7877-e4d2-bb2b-5c4fa8d3144b@free.fr
Signed-off-by: Greg Kroah-Hartman

clocksource/dummy_timer: Move hotplug callback after the real timers

2017-01-12T10:39:45+00:00

commit 9bf11ecce5a2758e5a097c2f3a13d08552d0d6f9 upstream.

When the dummy timer callback is invoked before the real timer callbacks,
then it tries to install that timer for the starting CPU. If the platform
does not have a broadcast timer installed the installation fails with a
kernel crash. The crash happens due to a unconditional deference of the non
available broadcast device. This needs to be fixed in the timer core code.

But even when this is fixed in the core code then installing the dummy
timer before the real timers is a pointless exercise.

Move it to the end of the callback list.

Fixes: 00c1d17aab51 ("clocksource/dummy_timer: Convert to hotplug state machine")
Reported-and-tested-by: Mason 
Signed-off-by: Thomas Gleixner 
Cc: Mark Rutland 
Cc: Anna-Maria Gleixner 
Cc: Richard Cochran 
Cc: Sebastian Andrzej Siewior 
Cc: Daniel Lezcano 
Cc: Peter Zijlstra ,
Cc: Sebastian Frias 
Cc: Thibaud Cornic 
Cc: Robin Murphy 
Link: http://lkml.kernel.org/r/1147ef90-7877-e4d2-bb2b-5c4fa8d3144b@free.fr
Signed-off-by: Greg Kroah-Hartman

xfs: fix max_retries _show and _store functions

2017-01-12T10:39:45+00:00

commit ff97f2399edac1e0fb3fa7851d5fbcbdf04717cf upstream.

max_retries _show and _store functions should test against cfg->max_retries,
not cfg->retry_timeout

Signed-off-by: Carlos Maiolino 
Reviewed-by: Eric Sandeen 
Signed-off-by: Darrick J. Wong 
Cc: Christoph Hellwig 
Signed-off-by: Greg Kroah-Hartman

xfs: fix crash and data corruption due to removal of busy COW extents

2017-01-12T10:39:45+00:00

commit a1b7a4dea6166cf46be895bce4aac67ea5160fe8 upstream.

There is a race window between write_cache_pages calling
clear_page_dirty_for_io and XFS calling set_page_writeback, in which
the mapping for an inode is tagged neither as dirty, nor as writeback.

If the COW shrinker hits in exactly that window we'll remove the delayed
COW extents and writepages trying to write it back, which in release
kernels will manifest as corruption of the bmap btree, and in debug
kernels will trip the ASSERT about now calling xfs_bmapi_write with the
COWFORK flag for holes.  A complex customer load manages to hit this
window fairly reliably, probably by always having COW writeback in flight
while the cow shrinker runs.

This patch adds another check for having the I_DIRTY_PAGES flag set,
which is still set during this race window.  While this fixes the problem
I'm still not overly happy about the way the COW shrinker works as it
still seems a bit fragile.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Darrick J. Wong 
Cc: Christoph Hellwig 
Signed-off-by: Greg Kroah-Hartman

xfs: use the actual AG length when reserving blocks

2017-01-12T10:39:44+00:00

commit 20e73b000bcded44a91b79429d8fa743247602ad upstream.

We need to use the actual AG length when making per-AG reservations,
since we could otherwise end up reserving more blocks out of the last
AG than there are actual blocks.

Complained-about-by: Brian Foster 
Signed-off-by: Darrick J. Wong 
Reviewed-by: Christoph Hellwig 
Cc: Christoph Hellwig 
Signed-off-by: Greg Kroah-Hartman

xfs: fix double-cleanup when CUI recovery fails

2017-01-12T10:39:44+00:00

commit 7a21272b088894070391a94fdd1c67014020fa1d upstream.

Dan Carpenter reported a double-free of rcur if _defer_finish fails
while we're recovering CUI items.  Fix the error recovery to prevent
this.

Reported-by: Dan Carpenter 
Signed-off-by: Darrick J. Wong 
Cc: Christoph Hellwig 
Signed-off-by: Greg Kroah-Hartman