3.10.35-stable review
Greg Kroah-Hartman
maintainercover 3.10.35-stable review
This is the start of the stable review cycle for the 3.10.35 release. There are 22 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 Sun Mar 30 17:30:55 UTC 2014. Anything received after that time might be too late.
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.10.35-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 3.10.35-rc1
Gerald Schaefer <[email protected]>
sched/autogroup: Fix race with task_groups list
Michele Baldessari <[email protected]>
e100: Fix "disabling already-disabled device" warning
Sarah Sharp <[email protected]>
xhci: Fix resume issues on Renesas chips in Samsung laptops
Ping Cheng <[email protected]>
Input: wacom - make sure touch_max is set for touch devices
Marcelo Tosatti <[email protected]>
KVM: VMX: fix use after free of vmx->loaded_vmcs
Marcelo Tosatti <[email protected]>
KVM: x86: handle invalid root_hpa everywhere
Marcelo Tosatti <[email protected]>
KVM: MMU: handle invalid root_hpa at __direct_map
Hans de Goede <[email protected]>
Input: elantech - improve clickpad detection
Rob Herring <[email protected]>
ARM: highbank: avoid L2 cache smc calls when PL310 is not present
Rob Herring <[email protected]>
ARM: move outer_cache declaration out of ifdef
Markus Pargmann <[email protected]>
regulator: core: Replace direct ops->disable usage
Dan Carpenter <[email protected]>
p54: clamp properly instead of just truncating
Ben Hutchings <[email protected]>
deb-pkg: Fix cross-building linux-headers package
Alexei Starovoitov <[email protected]>
x86: bpf_jit: support negative offsets
Stephen Warren <[email protected]>
ASoC: max98090: make REVISION_ID readable
Josh Durgin <[email protected]>
libceph: resend all writes after the osdmap loses the full flag
Josh Durgin <[email protected]>
libceph: block I/O when PAUSE or FULL osd map flags are set
Dan Carpenter <[email protected]>
media: cx18: check for allocation failure in cx18_read_eeprom()
Dan Carpenter <[email protected]>
media: dw2102: some missing unlocks on error
Dan Carpenter <[email protected]>
media: cxusb: unlock on error in cxusb_i2c_xfer()
Vaibhav Nagarnaik <[email protected]>
tracing: Fix array size mismatch in format string
Charles Keepax <[email protected]>
ALSA: compress: Pass through return value of open ops callback
-------------
Diffstat:
Makefile | 4 +-- arch/arm/include/asm/outercache.h | 4 +-- arch/arm/mach-highbank/highbank.c | 13 ++++---- arch/x86/kvm/mmu.c | 12 ++++++++ arch/x86/kvm/paging_tmpl.h | 8 +++++ arch/x86/kvm/vmx.c | 2 +- arch/x86/net/bpf_jit.S | 2 +- drivers/input/mouse/elantech.c | 45 ++++++++++++++++++++++++++-- drivers/input/tablet/wacom_sys.c | 7 +++-- drivers/media/pci/cx18/cx18-driver.c | 5 +++- drivers/media/usb/dvb-usb/cxusb.c | 21 +++++++++---- drivers/media/usb/dvb-usb/dw2102.c | 52 ++++++++++++++++++++++---------- drivers/net/ethernet/intel/e100.c | 2 +- drivers/net/wireless/p54/txrx.c | 2 +- drivers/regulator/core.c | 34 ++++++++------------- drivers/usb/host/xhci-pci.c | 5 ++++ include/linux/ceph/osd_client.h | 1 + include/linux/ftrace_event.h | 4 --- include/trace/ftrace.h | 7 ++--- kernel/sched/auto_group.c | 3 +- kernel/trace/trace_events.c | 6 ---- kernel/trace/trace_export.c | 7 ++--- net/ceph/osd_client.c | 57 +++++++++++++++++++++++++++++++----- scripts/package/builddeb | 9 +++--- sound/core/compress_offload.c | 2 +- sound/soc/codecs/max98090.c | 1 + 26 files changed, 216 insertions(+), 99 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/22 ALSA: compress: Pass through return value of open ops callback
3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Charles Keepax <[email protected]>
commit 749d32237bf39e6576dd95bfdf24e4378e51716c upstream.
The snd_compr_open function would always return 0 even if the compressed ops open function failed, obviously this is incorrect. Looks like this was introduced by a small typo in:
commit a0830dbd4e42b38aefdf3fb61ba5019a1a99ea85
ALSA: Add a reference counter to card instance
This patch returns the value from the compressed op as it should.
--- sound/core/compress_offload.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
sound/core/compress_offload.c +1 -1
@@ -133,7 +133,7 @@ static int snd_compr_open(struct inode *kfree (data); }snd_card_unref (compr->card); -return 0 ; +return ret; }static int snd_compr_free (struct inode *inode,struct file *f)
Greg Kroah-Hartman
maintainerPATCH 2/22 tracing: Fix array size mismatch in format string
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Vaibhav Nagarnaik <[email protected]>
commit 87291347c49dc40aa339f587b209618201c2e527 upstream.
In event format strings, the array size is reported in two locations. One in array subscript and then via the "size:" attribute. The values reported there have a mismatch.
For e.g., in sched:sched_switch the prev_comm and next_comm character arrays have subscript values as [32] where as the actual field size is 16.
name: sched_switch
ID: 301
format:
field:unsigned short common_type; offset:0; size:2; signed:0;
field:unsigned char common_flags; offset:2; size:1; signed:0;
field:unsigned char common_preempt_count; offset:3; size:1;signed:0;
field:int common_pid; offset:4; size:4; signed:1;
field:char prev_comm[32]; offset:8; size:16; signed:1;
field:pid_t prev_pid; offset:24; size:4; signed:1;
field:int prev_prio; offset:28; size:4; signed:1;
field:long prev_state; offset:32; size:8; signed:1;
field:char next_comm[32]; offset:40; size:16; signed:1;
field:pid_t next_pid; offset:56; size:4; signed:1;
field:int next_prio; offset:60; size:4; signed:1;After bisection, the following commit was blamed:
92edca0 tracing: Use direct field, type and system names
This commit removes the duplication of strings for field->name and field->type assuming that all the strings passed in __trace_define_field() are immutable. This is not true for arrays, where the type string is created in event_storage variable and field->type for all array fields points to event_storage.
Use __stringify() to create a string constant for the type string.
Also, get rid of event_storage and event_storage_mutex that are not needed anymore.
also, an added benefit is that this reduces the overhead of events a bit more:
text data bss dec hex filename
8424787 2036472 1302528 11763787 b3804b vmlinux
8420814 2036408 1302528 11759750 b37086 vmlinux.patched
--- include/linux/ftrace_event.h | 4 ---- include/trace/ftrace.h | 7 ++----- kernel/trace/trace_events.c | 6 ------ kernel/trace/trace_export.c | 7 ++----- 4 files changed, 4 insertions(+), 20 deletions(-)
include/linux/ftrace_event.h +0 -4
@@ -325,10 +325,6 @@ enum { FILTER_TRACE_FN, }; -#define EVENT_STORAGE_SIZE 128 -extern struct mutex event_storage_mutex; -extern char event_storage[EVENT_STORAGE_SIZE ]; -extern int trace_event_raw_init (struct ftrace_event_call *call); extern int trace_define_field(struct ftrace_event_call *call, const char *type, const char *name, int offset, int size,
include/trace/ftrace.h +2 -5
@@ -299,15 +299,12 @@ static struct trace_event_functions ftra#undef __array#define __array (type, item, len) \ do { \ - mutex_lock(&event_storage_mutex); \ + char *type_str = #type"["__stringify(len)"]"; \ BUILD_BUG_ON(len > MAX_FILTER_STR_VAL); \ - snprintf(event_storage, sizeof(event_storage), \ - "%s[%d]", #type, len); \ - ret = trace_define_field(event_call, event_storage, #item, \ + ret = trace_define_field(event_call, type_str, #item, \ offsetof(typeof(field), item), \ sizeof(field.item), \ is_signed_type(type), FILTER_OTHER); \ - mutex_unlock(&event_storage_mutex); \ if (ret) \ return ret; \ } while (0);
kernel/trace/trace_events.c +0 -6
@@ -27,12 +27,6 @@DEFINE_MUTEX (event_mutex); -DEFINE_MUTEX (event_storage_mutex); -EXPORT_SYMBOL_GPL (event_storage_mutex); - -char event_storage[EVENT_STORAGE_SIZE ]; -EXPORT_SYMBOL_GPL (event_storage); -LIST_HEAD (ftrace_events);static LIST_HEAD (ftrace_common_fields);
kernel/trace/trace_export.c +2 -5
@@ -95,15 +95,12 @@ static void __always_unused ____ftrace_c#undef __array#define __array (type, item, len) \ do { \ + char *type_str = #type"["__stringify(len)"]"; \ BUILD_BUG_ON(len > MAX_FILTER_STR_VAL); \ - mutex_lock(&event_storage_mutex); \ - snprintf(event_storage, sizeof(event_storage), \ - "%s[%d]", #type, len); \ - ret = trace_define_field(event_call, event_storage, #item, \ + ret = trace_define_field(event_call, type_str, #item, \ offsetof(typeof(field), item), \ sizeof(field.item), \ is_signed_type(type), filter_type); \ - mutex_unlock(&event_storage_mutex); \ if (ret) \ return ret; \ } while (0);
Greg Kroah-Hartman
maintainerPATCH 3/22 media: cxusb: unlock on error in cxusb_i2c_xfer()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit 1cdbcc5db4e6d51ce9bb1313195167cada9aa6e9 upstream.
We recently introduced some new error paths which are missing their unlocks.
--- drivers/media/usb/dvb-usb/cxusb.c | 21 ++++++++++++++++----- 1 file changed, 16 insertions(+), 5 deletions(-)
drivers/media/usb/dvb-usb/cxusb.c +16 -5
@@ -149,6 +149,7 @@ static int cxusb_i2c_xfer(struct i2c_ada int num) {struct dvb_usb_device *d =i2c_get_adapdata (adap); +int ret;int i;if (mutex_lock_interruptible (&d->i2c_mutex) <0 )
@@ -173,7 +174,8 @@ static int cxusb_i2c_xfer(struct i2c_adaif (1 + msg[i].len >sizeof (ibuf)) {warn ("i2c rd: len=%d is too big!\n" , msg[i].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } obuf[0 ] =0 ; obuf[1 ] = msg[i].len;
@@ -193,12 +195,14 @@ static int cxusb_i2c_xfer(struct i2c_adaif (3 + msg[i].len >sizeof (obuf)) {warn ("i2c wr: len=%d is too big!\n" , msg[i].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; }if (1 + msg[i +1 ].len >sizeof (ibuf)) {warn ("i2c rd: len=%d is too big!\n" , msg[i +1 ].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } obuf[0 ] = msg[i].len; obuf[1 ] = msg[i+1 ].len;
@@ -223,7 +227,8 @@ static int cxusb_i2c_xfer(struct i2c_adaif (2 + msg[i].len >sizeof (obuf)) {warn ("i2c wr: len=%d is too big!\n" , msg[i].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } obuf[0 ] = msg[i].addr; obuf[1 ] = msg[i].len;
@@ -237,8 +242,14 @@ static int cxusb_i2c_xfer(struct i2c_ada } } +if (i == num) + ret = num; +else + ret = -EREMOTEIO ; + +unlock:mutex_unlock (&d->i2c_mutex); -return i == num ? num : -EREMOTEIO ; +return ret; }static u32 cxusb_i2c_func (struct i2c_adapter *adapter)
Greg Kroah-Hartman
maintainerPATCH 4/22 media: dw2102: some missing unlocks on error
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit 324ed533bf0b23c309b805272c4ffcc5d51493a6 upstream.
We recently introduced some new error paths but the unlocks are missing.
--- drivers/media/usb/dvb-usb/dw2102.c | 52 +++++++++++++++++++++++++------------ 1 file changed, 36 insertions(+), 16 deletions(-)
drivers/media/usb/dvb-usb/dw2102.c +36 -16
@@ -301,6 +301,7 @@ static int dw2102_serit_i2c_transfer(strstatic int dw2102_earda_i2c_transfer (struct i2c_adapter *adap,struct i2c_msg msg[],int num) {struct dvb_usb_device *d =i2c_get_adapdata (adap); +int ret;if (!d)return -ENODEV ;
@@ -316,7 +317,8 @@ static int dw2102_earda_i2c_transfer(strif (2 + msg[1 ].len >sizeof (ibuf)) {warn ("i2c rd: len=%d is too big!\n" , msg[1 ].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } obuf[0 ] = msg[0 ].addr <<1 ;
@@ -340,7 +342,8 @@ static int dw2102_earda_i2c_transfer(strif (2 + msg[0 ].len >sizeof (obuf)) {warn ("i2c wr: len=%d is too big!\n" , msg[1 ].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } obuf[0 ] = msg[0 ].addr <<1 ;
@@ -357,7 +360,8 @@ static int dw2102_earda_i2c_transfer(strif (2 + msg[0 ].len >sizeof (obuf)) {warn ("i2c wr: len=%d is too big!\n" , msg[1 ].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } obuf[0 ] = msg[0 ].addr <<1 ;
@@ -386,15 +390,17 @@ static int dw2102_earda_i2c_transfer(strbreak ; } + ret = num; +unlock:mutex_unlock (&d->i2c_mutex); -return num; +return ret; }static int dw2104_i2c_transfer (struct i2c_adapter *adap,struct i2c_msg msg[],int num) {struct dvb_usb_device *d =i2c_get_adapdata (adap); -int len, i, j; +int len, i, j, ret;if (!d)return -ENODEV ;
@@ -430,7 +436,8 @@ static int dw2104_i2c_transfer(struct i2if (2 + msg[j].len >sizeof (ibuf)) {warn ("i2c rd: len=%d is too big!\n" , msg[j].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } dw210x_op_rw(d->udev, 0xc3,
@@ -466,7 +473,8 @@ static int dw2104_i2c_transfer(struct i2if (2 + msg[j].len >sizeof (obuf)) {warn ("i2c wr: len=%d is too big!\n" , msg[j].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } obuf[0 ] = msg[j].addr <<1 ;
@@ -481,15 +489,18 @@ static int dw2104_i2c_transfer(struct i2 } } + ret = num; +unlock:mutex_unlock (&d->i2c_mutex); -return num; +return ret; }static int dw3101_i2c_transfer (struct i2c_adapter *adap,struct i2c_msg msg[],int num) {struct dvb_usb_device *d =i2c_get_adapdata (adap); +int ret;int i;if (!d)
@@ -506,7 +517,8 @@ static int dw3101_i2c_transfer(struct i2if (2 + msg[1 ].len >sizeof (ibuf)) {warn ("i2c rd: len=%d is too big!\n" , msg[1 ].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } obuf[0 ] = msg[0 ].addr <<1 ; obuf[1 ] = msg[0 ].len;
@@ -530,7 +542,8 @@ static int dw3101_i2c_transfer(struct i2if (2 + msg[0 ].len >sizeof (obuf)) {warn ("i2c wr: len=%d is too big!\n" , msg[0 ].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } obuf[0 ] = msg[0 ].addr <<1 ; obuf[1 ] = msg[0 ].len;
@@ -556,9 +569,11 @@ static int dw3101_i2c_transfer(struct i2 msg[i].flags == 0 ? ">>>" : "<<<");debug_dump (msg[i].buf, msg[i].len, deb_xfer); } + ret = num; +unlock:mutex_unlock (&d->i2c_mutex); -return num; +return ret; } static int s6x0_i2c_transfer(struct i2c_adapter *adap, struct i2c_msg msg[],
@@ -566,7 +581,7 @@ static int s6x0_i2c_transfer(struct i2c_ {struct dvb_usb_device *d =i2c_get_adapdata (adap);struct usb_device *udev; -int len, i, j; +int len, i, j, ret;if (!d)return -ENODEV ;
@@ -618,7 +633,8 @@ static int s6x0_i2c_transfer(struct i2c_if (msg[j].len >sizeof (ibuf)) {warn ("i2c rd: len=%d is too big!\n" , msg[j].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } dw210x_op_rw(d->udev, 0x91, 0, 0,
@@ -652,7 +668,8 @@ static int s6x0_i2c_transfer(struct i2c_if (2 + msg[j].len >sizeof (obuf)) {warn ("i2c wr: len=%d is too big!\n" , msg[j].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } obuf[0 ] = msg[j +1 ].len;
@@ -671,7 +688,8 @@ static int s6x0_i2c_transfer(struct i2c_if (2 + msg[j].len >sizeof (obuf)) {warn ("i2c wr: len=%d is too big!\n" , msg[j].len); -return -EOPNOTSUPP ; + ret = -EOPNOTSUPP ; + goto unlock; } obuf[0 ] = msg[j].len +1 ; obuf[1 ] = (msg[j].addr <<1 );
@@ -685,9 +703,11 @@ static int s6x0_i2c_transfer(struct i2c_ } } } + ret = num; +unlock:mutex_unlock (&d->i2c_mutex); -return num; +return ret; } static int su3000_i2c_transfer(struct i2c_adapter *adap, struct i2c_msg msg[],
Greg Kroah-Hartman
maintainerPATCH 5/22 media: cx18: check for allocation failure in cx18_read_eeprom()
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit e351bf25fa373a3de0be2141b962c5c3c27006a2 upstream.
It upsets static checkers when we don't check for allocation failure. I moved the memset() of "tv" earlier so we don't use uninitialized data on error.
--- drivers/media/pci/cx18/cx18-driver.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-)
drivers/media/pci/cx18/cx18-driver.c +4 -1
@@ -327,13 +327,16 @@ void cx18_read_eeprom(struct cx18 *cx, sstruct i2c_client *c;u8 eedata[256 ]; +memset (tv,0 ,sizeof (*tv)); + c =kzalloc (sizeof (*c),GFP_KERNEL ); +if (!c) +return ;strlcpy (c->name,"cx18 tveeprom tmp" ,sizeof (c->name)); c->adapter = &cx->i2c_adap[0 ]; c->addr =0xa0 >>1 ; -memset (tv,0 ,sizeof (*tv));if (tveeprom_read (c, eedata,sizeof (eedata))) goto ret;
Greg Kroah-Hartman
maintainerPATCH 6/22 libceph: block I/O when PAUSE or FULL osd map flags are set
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Durgin <[email protected]>
commit d29adb34a94715174c88ca93e8aba955850c9bde upstream.
The PAUSEWR and PAUSERD flags are meant to stop the cluster from processing writes and reads, respectively. The FULL flag is set when the cluster determines that it is out of space, and will no longer process writes. PAUSEWR and PAUSERD are purely client-side settings already implemented in userspace clients. The osd does nothing special with these flags.
When the FULL flag is set, however, the osd responds to all writes with -ENOSPC. For cephfs, this makes sense, but for rbd the block layer translates this into EIO. If a cluster goes from full to non-full quickly, a filesystem on top of rbd will not behave well, since some writes succeed while others get EIO.
Fix this by blocking any writes when the FULL flag is set in the osd client. This is the same strategy used by userspace, so apply it by default. A follow-on patch makes this configurable.
__map_request() is called to re-target osd requests in case the available osds changed. Add a paused field to a ceph_osd_request, and set it whenever an appropriate osd map flag is set. Avoid queueing paused requests in __map_request(), but force them to be resent if they become unpaused.
Also subscribe to the next osd map from the monitor if any of these flags are set, so paused requests can be unblocked as soon as possible.
--- include/linux/ceph/osd_client.h | 1 + net/ceph/osd_client.c | 29 +++++++++++++++++++++++++++-- 2 files changed, 28 insertions(+), 2 deletions(-)
include/linux/ceph/osd_client.h +1 -0
@@ -138,6 +138,7 @@ struct ceph_osd_request {__le64 *r_request_pool;void *r_request_pgid;__le32 *r_request_attempts; +bool r_paused;struct ceph_eversion *r_request_reassert_version;int r_result;
net/ceph/osd_client.c +27 -2
@@ -1225,6 +1225,22 @@ void ceph_osdc_set_request_linger(structEXPORT_SYMBOL (ceph_osdc_set_request_linger);/* +* Returns whether a request should be blocked from being sent +* based on the current osdmap and osd_client settings. +* +* Caller should hold map_sem for read. +*/ +static bool __req_should_be_paused (struct ceph_osd_client *osdc, +struct ceph_osd_request *req) +{ +bool pauserd =ceph_osdmap_flag (osdc->osdmap,CEPH_OSDMAP_PAUSERD ); +bool pausewr =ceph_osdmap_flag (osdc->osdmap,CEPH_OSDMAP_PAUSEWR ) || +ceph_osdmap_flag (osdc->osdmap,CEPH_OSDMAP_FULL ); +return (req->r_flags &CEPH_OSD_FLAG_READ && pauserd) || + (req->r_flags &CEPH_OSD_FLAG_WRITE && pausewr); +} + +/* * Pick an osd (the first 'up' osd in the pg), allocate the osd struct * (as needed), and set the request r_osd appropriately. If there is * no up osd, set r_osd to NULL. Move the request to the appropriate list
@@ -1241,6 +1257,7 @@ static int __map_request(struct ceph_osdint acting[CEPH_PG_MAX_SIZE ];int o =-1 , num =0 ;int err; +bool was_paused;dout ("map_request %p tid %lld\n" , req, req->r_tid); err = ceph_calc_ceph_pg(&pgid, req->r_oid, osdc->osdmap,
@@ -1257,12 +1274,18 @@ static int __map_request(struct ceph_osd num = err; } + was_paused = req->r_paused; + req->r_paused =__req_should_be_paused (osdc, req); +if (was_paused && !req->r_paused) + force_resend =1 ; +if ((!force_resend && req->r_osd && req->r_osd->o_osd == o && req->r_sent >= req->r_osd->o_incarnation && req->r_num_pg_osds == num &&memcmp (req->r_pg_osds, acting,sizeof (acting[0 ])*num) ==0 ) || - (req->r_osd ==NULL && o ==-1 )) + (req->r_osd ==NULL && o ==-1 ) || + req->r_paused)return 0 ;/* no change */ dout("map_request tid %llu pgid %lld.%x osd%d (was osd%d)\n",
@@ -1797,7 +1820,9 @@ done:* we find out when we are no longer full and stop returning * ENOSPC. */ -if (ceph_osdmap_flag (osdc->osdmap,CEPH_OSDMAP_FULL )) +if (ceph_osdmap_flag (osdc->osdmap,CEPH_OSDMAP_FULL ) || +ceph_osdmap_flag (osdc->osdmap,CEPH_OSDMAP_PAUSERD ) || +ceph_osdmap_flag (osdc->osdmap,CEPH_OSDMAP_PAUSEWR ))ceph_monc_request_next_osdmap (&osdc->client->monc);mutex_lock (&osdc->request_mutex);
Greg Kroah-Hartman
maintainerPATCH 7/22 libceph: resend all writes after the osdmap loses the full flag
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Josh Durgin <[email protected]>
commit 9a1ea2dbff11547a8e664f143c1ffefc586a577a upstream.
With the current full handling, there is a race between osds and clients getting the first map marked full. If the osd wins, it will return -ENOSPC to any writes, but the client may already have writes in flight. This results in the client getting the error and propagating it up the stack. For rbd, the block layer turns this into EIO, which can cause corruption in filesystems above it.
To avoid this race, osds are being changed to drop writes that came from clients with an osdmap older than the last osdmap marked full. In order for this to work, clients must resend all writes after they encounter a full -> not full transition in the osdmap. osds will wait for an updated map instead of processing a request from a client with a newer map, so resent writes will not be dropped by the osd unless there is another not full -> full transition.
This approach requires both osds and clients to be fixed to avoid the race. Old clients talking to osds with this fix may hang instead of returning EIO and potentially corrupting an fs. New clients talking to old osds have the same behavior as before if they encounter this race.
--- net/ceph/osd_client.c | 28 ++++++++++++++++++++++------ 1 file changed, 22 insertions(+), 6 deletions(-)
net/ceph/osd_client.c +22 -6
@@ -1629,14 +1629,17 @@ static void reset_changed_osds(struct ce* * Caller should hold map_sem for read. */ -static void kick_requests (struct ceph_osd_client *osdc,int force_resend) +static void kick_requests (struct ceph_osd_client *osdc,bool force_resend, +bool force_resend_writes) {struct ceph_osd_request *req, *nreq;struct rb_node *p;int needmap =0 ;int err; +bool force_resend_req; -dout ("kick_requests %s\n" , force_resend ?" (force resend)" :"" ); +dout ("kick_requests %s %s\n" , force_resend ?" (force resend)" :"" , + force_resend_writes ?" (force resend writes)" :"" );mutex_lock (&osdc->request_mutex);for (p =rb_first (&osdc->requests); p; ) { req = rb_entry(p, struct ceph_osd_request, r_node);
@@ -1661,7 +1664,10 @@ static void kick_requests(struct ceph_oscontinue ; } - err =__map_request (osdc, req, force_resend); + force_resend_req = force_resend || + (force_resend_writes && + req->r_flags &CEPH_OSD_FLAG_WRITE ); + err =__map_request (osdc, req, force_resend_req);if (err <0 )continue ;/* error */ if (req->r_osd ==NULL ) {
@@ -1681,7 +1687,8 @@ static void kick_requests(struct ceph_os r_linger_item) {dout ("linger req=%p req->r_osd=%p\n" , req, req->r_osd); - err =__map_request (osdc, req, force_resend); + err =__map_request (osdc, req, + force_resend || force_resend_writes);dout ("__map_request returned %d\n" , err);if (err ==0 )continue ;/* no change and no osd was specified */
@@ -1723,6 +1730,7 @@ void ceph_osdc_handle_map(struct ceph_osstruct ceph_osdmap *newmap =NULL , *oldmap;int err;struct ceph_fsid fsid; +bool was_full;dout ("handle_map have %u\n" , osdc->osdmap ? osdc->osdmap->epoch :0 ); p = msg->front.iov_base;
@@ -1736,6 +1744,8 @@ void ceph_osdc_handle_map(struct ceph_osdown_write (&osdc->map_sem); + was_full =ceph_osdmap_flag (osdc->osdmap,CEPH_OSDMAP_FULL ); +/* incremental maps */ ceph_decode_32_safe (&p, end, nr_maps, bad);dout (" %d inc maps\n" , nr_maps);
@@ -1760,7 +1770,10 @@ void ceph_osdc_handle_map(struct ceph_osceph_osdmap_destroy (osdc->osdmap); osdc->osdmap = newmap; } -kick_requests (osdc,0 ); + was_full = was_full || +ceph_osdmap_flag (osdc->osdmap, +CEPH_OSDMAP_FULL ); +kick_requests (osdc,0 , was_full); }else {dout ("ignoring incremental map %u len %d\n" , epoch, maplen);
@@ -1803,7 +1816,10 @@ void ceph_osdc_handle_map(struct ceph_os skipped_map =1 ;ceph_osdmap_destroy (oldmap); } -kick_requests (osdc, skipped_map); + was_full = was_full || +ceph_osdmap_flag (osdc->osdmap, +CEPH_OSDMAP_FULL ); +kick_requests (osdc, skipped_map, was_full); } p += maplen; nr_maps--;
Greg Kroah-Hartman
maintainerPATCH 8/22 ASoC: max98090: make REVISION_ID readable
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stephen Warren <[email protected]>
commit e126a646f77fdd66978785cb0a3a5e46b07aee2e upstream.
The REVISION_ID register is not currently marked readable. snd_soc_read() refuses to read the register, and hence probe() fails.
--- sound/soc/codecs/max98090.c | 1 + 1 file changed, 1 insertion(+)
sound/soc/codecs/max98090.c +1 -0
@@ -336,6 +336,7 @@ static bool max98090_readable_register(scase M98090_REG_RECORD_TDM_SLOT :case M98090_REG_SAMPLE_RATE : case M98090_REG_DMIC34_BIQUAD_BASE ... M98090_REG_DMIC34_BIQUAD_BASE + 0x0E: +case M98090_REG_REVISION_ID :return true;default :return false;
Greg Kroah-Hartman
maintainerPATCH 9/22 x86: bpf_jit: support negative offsets
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alexei Starovoitov <[email protected]>
commit fdfaf64e75397567257e1051931f9a3377360665 upstream.
Commit a998d4342337 claimed to introduce negative offset support to x86 jit, but it couldn't be working, since at the time of the execution of LD+ABS or LD+IND instructions via call into bpf_internal_load_pointer_neg_helper() the %edx (3rd argument of this func) had junk value instead of access size in bytes (1 or 2 or 4).
Store size into %edx instead of %ecx (what original commit intended to do)
--- arch/x86/net/bpf_jit.S | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/net/bpf_jit.S +1 -1
@@ -140,7 +140,7 @@ bpf_slow_path_byte_msh: push %r9; \ push SKBDATA; \ /* rsi already has offset */ \ - mov $SIZE,%ecx; /* size */ \ + mov $SIZE,%edx; /* size */ \ call bpf_internal_load_pointer_neg_helper; \ test %rax,%rax; \ pop SKBDATA; \
Greg Kroah-Hartman
maintainerPATCH 10/22 deb-pkg: Fix cross-building linux-headers package
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ben Hutchings <[email protected]>
commit f8ce239dfc7ba9add41d9ecdc5e7810738f839fa upstream.
builddeb generates a control file that says the linux-headers package can only be built for the build system primary architecture. This breaks cross-building configurations. We should use $debarch for this instead.
Since $debarch is not yet set when generating the control file, set
Architecture: any and use control file variables to fill in the description.
--- scripts/package/builddeb | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-)
scripts/package/builddeb +4 -5
@@ -62,7 +62,7 @@ create_package() { fi # Create the package - dpkg-gencontrol -isp $forcearch -p$pname -P"$pdir" + dpkg-gencontrol -isp $forcearch -Vkernel:debarch="${debarch:-$(dpkg --print-architecture)}" -p$pname -P"$pdir" dpkg --build "$pdir" .. }
@@ -252,15 +252,14 @@ mkdir -p "$destdir" (cd $objtree; tar -c -f - -T "$objtree/debian/hdrobjfiles") | (cd $destdir; tar -xf -) ln -sf "/usr/src/linux-headers-$version" "$kernel_headers_dir/lib/modules/$version/build" rm -f "$objtree/debian/hdrsrcfiles" "$objtree/debian/hdrobjfiles" -arch=$(dpkg --print-architecture) cat <<EOF >> debian/control Package: $kernel_headers_packagename Provides: linux-headers, linux-headers-2.6 -Architecture: $arch -Description: Linux kernel headers for $KERNELRELEASE on $arch - This package provides kernel header files for $KERNELRELEASE on $arch +Architecture: any +Description: Linux kernel headers for $KERNELRELEASE on \${kernel:debarch} + This package provides kernel header files for $KERNELRELEASE on \${kernel:debarch} . This is useful for people who need to build external modules EOF
Greg Kroah-Hartman
maintainerPATCH 11/22 p54: clamp properly instead of just truncating
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Dan Carpenter <[email protected]>
commit 608cfbe4abaf76e9d732efd7ed1cfa3998163d91 upstream.
The call to clamp_t() first truncates the variable signed 8 bit and as a result, the actual clamp is a no-op.
--- drivers/net/wireless/p54/txrx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/wireless/p54/txrx.c +1 -1
@@ -587,7 +587,7 @@ static void p54_rx_stats(struct p54_comm chan = priv->curchan;if (chan) {struct survey_info *survey = &priv->survey[chan->hw_value]; - survey->noise =clamp_t (s8, priv->noise,-128 ,127 ); + survey->noise =clamp (priv->noise,-128 ,127 ); survey->channel_time = priv->survey_raw.active; survey->channel_time_tx = priv->survey_raw.tx; survey->channel_time_busy = priv->survey_raw.tx +
Greg Kroah-Hartman
maintainerPATCH 12/22 regulator: core: Replace direct ops->disable usage
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Markus Pargmann <[email protected]>
commit 66fda75f47dc583f1c187556e9a2c082dd64f8c6 upstream.
There are many places where ops->disable is called directly. Instead we should use _regulator_do_disable() which also handles gpio regulators.
To be able to use the wrapper function from _regulator_force_disable(), I moved the _notifier_call_chain() call from _regulator_do_disable() to _regulator_disable(). This way, _regulator_force_disable() can use different flags for _notifier_call_chain() without calling it twice.
--- drivers/regulator/core.c | 34 +++++++++++++--------------------- 1 file changed, 13 insertions(+), 21 deletions(-)
drivers/regulator/core.c +13 -21
@@ -1712,8 +1712,6 @@ static int _regulator_do_disable(structtrace_regulator_disable_complete (rdev_get_name (rdev)); -_notifier_call_chain (rdev,REGULATOR_EVENT_DISABLE , -NULL );return 0 ; }
@@ -1737,6 +1735,8 @@ static int _regulator_disable(struct regrdev_err (rdev,"failed to disable\n" );return ret; } +_notifier_call_chain (rdev,REGULATOR_EVENT_DISABLE , +NULL ); } rdev->use_count =0 ;
@@ -1789,20 +1789,16 @@ static int _regulator_force_disable(stru {int ret =0 ; -/* force disable */ -if (rdev->desc->ops->disable) { -/* ah well, who wants to live forever... */ - ret = rdev->desc->ops->disable (rdev); -if (ret <0 ) { -rdev_err (rdev,"failed to force disable\n" ); -return ret; - } -/* notify other consumers that power has been forced off */ -_notifier_call_chain (rdev,REGULATOR_EVENT_FORCE_DISABLE | -REGULATOR_EVENT_DISABLE ,NULL ); + ret =_regulator_do_disable (rdev); +if (ret <0 ) { +rdev_err (rdev,"failed to force disable\n" ); +return ret; } -return ret; +_notifier_call_chain (rdev,REGULATOR_EVENT_FORCE_DISABLE | +REGULATOR_EVENT_DISABLE ,NULL ); + +return 0 ; }/**
@@ -3788,8 +3784,6 @@ int regulator_suspend_finish(void)mutex_lock (®ulator_list_mutex);list_for_each_entry (rdev, ®ulator_list, list) { -struct regulator_ops *ops = rdev->desc->ops; -mutex_lock (&rdev->mutex);if (rdev->use_count >0 || rdev->constraints->always_on) { error =_regulator_do_enable (rdev);
@@ -3798,12 +3792,10 @@ int regulator_suspend_finish(void) }else {if (!has_full_constraints) goto unlock; -if (!ops->disable) - goto unlock;if (!_regulator_is_enabled (rdev)) goto unlock; - error = ops->disable (rdev); + error =_regulator_do_disable (rdev);if (error) ret = error; }
@@ -3993,7 +3985,7 @@ static int __init regulator_init_complet ops = rdev->desc->ops; c = rdev->constraints; -if (!ops->disable || (c && c->always_on)) +if (c && c->always_on)continue ;mutex_lock (&rdev->mutex);
@@ -4014,7 +4006,7 @@ static int __init regulator_init_complet/* We log since this may kill the system if it * goes wrong. */ rdev_info (rdev,"disabling\n" ); - ret = ops->disable (rdev); + ret =_regulator_do_disable (rdev);if (ret !=0 ) {rdev_err (rdev,"couldn't disable: %d\n" , ret); }
Greg Kroah-Hartman
maintainerPATCH 13/22 ARM: move outer_cache declaration out of ifdef
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rob Herring <[email protected]>
commit 0b53c11d533a8f6688d73fad0baf67dd08ec1b90 upstream.
Move the outer_cache declaration of the CONFIG_OUTER_CACHE ifdef so that outer_cache can be used inside IS_ENABLED condition.
--- arch/arm/include/asm/outercache.h | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm/include/asm/outercache.h +2 -2
@@ -37,10 +37,10 @@ struct outer_cache_fns {void (*resume)(void ); }; -#ifdef CONFIG_OUTER_CACHE -extern struct outer_cache_fns outer_cache; +#ifdef CONFIG_OUTER_CACHE +static inline void outer_inv_range (phys_addr_t start,phys_addr_t end) {if (outer_cache.inv_range)
Greg Kroah-Hartman
maintainerPATCH 14/22 ARM: highbank: avoid L2 cache smc calls when PL310 is not present
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Rob Herring <[email protected]>
commit a56a5cf1f2ec895599eace0ac6eba1e4a489e4bf upstream.
While Midway firmware handles L2 smc calls as nops, the custom smc calls present a problem when running virtualized Midway guest. They aren't needed so just avoid calling them.
In the process, cleanup the L2X0 ifdefs and use IS_ENABLED instead.
--- arch/arm/mach-highbank/highbank.c | 13 ++++++------- 1 file changed, 6 insertions(+), 7 deletions(-)
arch/arm/mach-highbank/highbank.c +6 -7
@@ -65,14 +65,12 @@ void highbank_set_cpu_jump(int cpu, void HB_JUMP_TABLE_PHYS(cpu) + 15); } -#ifdef CONFIG_CACHE_L2X0 static void highbank_l2x0_disable (void ) {outer_flush_all ();/* Disable PL310 L2 Cache controller */ highbank_smc1 (0x102 ,0x0 ); } -#endif static void __init highbank_init_irq (void ) {
@@ -81,12 +79,13 @@ static void __init highbank_init_irq(voiif (of_find_compatible_node (NULL ,NULL ,"arm,cortex-a9" ))highbank_scu_map_io (); -#ifdef CONFIG_CACHE_L2X0 /* Enable PL310 L2 Cache controller */ -highbank_smc1 (0x102 ,0x1 ); -l2x0_of_init (0 , ~0UL ); - outer_cache.disable = highbank_l2x0_disable; -#endif +if (IS_ENABLED (CONFIG_CACHE_L2X0 ) && +of_find_compatible_node (NULL ,NULL ,"arm,pl310-cache" )) { +highbank_smc1 (0x102 ,0x1 ); +l2x0_of_init (0 , ~0UL ); + outer_cache.disable = highbank_l2x0_disable; + } }static void __init highbank_timer_init (void )
Greg Kroah-Hartman
maintainerPATCH 15/22 Input: elantech - improve clickpad detection
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Hans de Goede <[email protected]>
commit c15bdfd5b9831e4cab8cfc118243956e267dd30e upstream.
The current assumption in the elantech driver that hw version 3 touchpads are never clickpads and hw version 4 touchpads are always clickpads is wrong.
There are several bug reports for this, ie:
https://bugzilla.redhat.com/show_bug.cgi?id=1030802
http://superuser.com/questions/619582/right-elantech-touchpad-button-not-working-in-linux
I've spend a couple of hours wading through various bugzillas, launchpads and forum posts to create a list of fw-versions and capabilities for different laptop models to find a good method to differentiate between clickpads and versions with separate hardware buttons.
Which shows that a device being a clickpad is reliable indicated by bit 12 being set in the fw_version. I've included the gathered list inside the driver, so that we've this info at hand if we need to revisit this later.
--- drivers/input/mouse/elantech.c | 45 ++++++++++++++++++++++++++++++++++++++--- 1 file changed, 42 insertions(+), 3 deletions(-)
drivers/input/mouse/elantech.c +42 -3
@@ -486,6 +486,7 @@ static void elantech_input_sync_v4(strucunsigned char *packet = psmouse->packet;input_report_key (dev,BTN_LEFT , packet[0 ] &0x01 ); +input_report_key (dev,BTN_RIGHT , packet[0 ] &0x02 );input_mt_report_pointer_emulation (dev, true);input_sync (dev); }
@@ -954,6 +955,44 @@ static int elantech_get_resolution_v4(st }/* +* Advertise INPUT_PROP_BUTTONPAD for clickpads. The testing of bit 12 in +* fw_version for this is based on the following fw_version & caps table: +* +* Laptop-model: fw_version: caps: buttons: +* Acer S3 0x461f00 10, 13, 0e clickpad +* Acer S7-392 0x581f01 50, 17, 0d clickpad +* Acer V5-131 0x461f02 01, 16, 0c clickpad +* Acer V5-551 0x461f00 ? clickpad +* Asus K53SV 0x450f01 78, 15, 0c 2 hw buttons +* Asus G46VW 0x460f02 00, 18, 0c 2 hw buttons +* Asus G750JX 0x360f00 00, 16, 0c 2 hw buttons +* Asus UX31 0x361f00 20, 15, 0e clickpad +* Asus UX32VD 0x361f02 00, 15, 0e clickpad +* Avatar AVIU-145A2 0x361f00 ? clickpad +* Gigabyte U2442 0x450f01 58, 17, 0c 2 hw buttons +* Lenovo L430 0x350f02 b9, 15, 0c 2 hw buttons (*) +* Samsung NF210 0x150b00 78, 14, 0a 2 hw buttons +* Samsung NP770Z5E 0x575f01 10, 15, 0f clickpad +* Samsung NP700Z5B 0x361f06 21, 15, 0f clickpad +* Samsung NP900X3E-A02 0x575f03 ? clickpad +* Samsung NP-QX410 0x851b00 19, 14, 0c clickpad +* Samsung RC512 0x450f00 08, 15, 0c 2 hw buttons +* Samsung RF710 0x450f00 ? 2 hw buttons +* System76 Pangolin 0x250f01 ? 2 hw buttons +* (*) + 3 trackpoint buttons +*/ +static void elantech_set_buttonpad_prop (struct psmouse *psmouse) +{ +struct input_dev *dev = psmouse->dev; +struct elantech_data *etd = psmouse->private; + +if (etd->fw_version &0x001000 ) { +__set_bit (INPUT_PROP_BUTTONPAD , dev->propbit); +__clear_bit (BTN_RIGHT , dev->keybit); + } +} + +/* * Set the appropriate event bits for the input subsystem */ static int elantech_set_input_params (struct psmouse *psmouse)
@@ -996,6 +1035,8 @@ static int elantech_set_input_params(str__set_bit (INPUT_PROP_SEMI_MT , dev->propbit);/* fall through */ case 3 : +if (etd->hw_version ==3 ) +elantech_set_buttonpad_prop (psmouse);input_set_abs_params (dev,ABS_X , x_min, x_max,0 ,0 );input_set_abs_params (dev,ABS_Y , y_min, y_max,0 ,0 );if (etd->reports_pressure) {
@@ -1017,9 +1058,7 @@ static int elantech_set_input_params(str*/ psmouse_warn (psmouse,"couldn't query resolution data.\n" ); } -/* v4 is clickpad, with only one button. */ -__set_bit (INPUT_PROP_BUTTONPAD , dev->propbit); -__clear_bit (BTN_RIGHT , dev->keybit); +elantech_set_buttonpad_prop (psmouse);__set_bit (BTN_TOOL_QUADTAP , dev->keybit);/* For X to recognize me as touchpad. */ input_set_abs_params (dev,ABS_X , x_min, x_max,0 ,0 );
Greg Kroah-Hartman
maintainerPATCH 16/22 KVM: MMU: handle invalid root_hpa at __direct_map
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marcelo Tosatti <[email protected]>
commit 989c6b34f6a9480e397b170cc62237e89bf4fdb9 upstream.
It is possible for __direct_map to be called on invalid root_hpa (-1), two examples:
1) try_async_pf -> can_do_async_pf
-> vmx_interrupt_allowed -> nested_vmx_vmexit
2) vmx_handle_exit -> vmx_interrupt_allowed -> nested_vmx_vmexit
Then to load_vmcs12_host_state and kvm_mmu_reset_context.
Check for this possibility, let fault exception be regenerated.
BZ: https://bugzilla.redhat.com/show_bug.cgi?id=924916
--- arch/x86/kvm/mmu.c | 3 +++ 1 file changed, 3 insertions(+)
arch/x86/kvm/mmu.c +3 -0
@@ -2585,6 +2585,9 @@ static int __direct_map(struct kvm_vcpuint emulate =0 ;gfn_t pseudo_gfn; +if (!VALID_PAGE (vcpu->arch.mmu.root_hpa)) +return 0 ; +for_each_shadow_entry (vcpu, (u64 )gfn <<PAGE_SHIFT , iterator) {if (iterator.level == level) { mmu_set_spte(vcpu, iterator.sptep, ACC_ALL,
Greg Kroah-Hartman
maintainerPATCH 17/22 KVM: x86: handle invalid root_hpa everywhere
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marcelo Tosatti <[email protected]>
commit 37f6a4e237303549c8676dfe1fd1991ceab512eb upstream.
Rom Freiman <[email protected]> notes other code paths vulnerable to bug fixed by 989c6b34f6a9480e397b.
--- arch/x86/kvm/mmu.c | 9 +++++++++ arch/x86/kvm/paging_tmpl.h | 8 ++++++++ 2 files changed, 17 insertions(+)
arch/x86/kvm/mmu.c +9 -0
@@ -2751,6 +2751,9 @@ static bool fast_page_fault(struct kvm_vbool ret = false;u64 spte =0ull ; +if (!VALID_PAGE (vcpu->arch.mmu.root_hpa)) +return false; +if (!page_fault_can_be_fast (vcpu, error_code))return false;
@@ -3142,6 +3145,9 @@ static u64 walk_shadow_page_get_mmio_sptstruct kvm_shadow_walk_iterator iterator;u64 spte =0ull ; +if (!VALID_PAGE (vcpu->arch.mmu.root_hpa)) +return spte; +walk_shadow_page_lockless_begin (vcpu);for_each_shadow_entry_lockless (vcpu, addr, iterator, spte)if (!is_shadow_present_pte (spte))
@@ -4332,6 +4338,9 @@ int kvm_mmu_get_spte_hierarchy(struct kvu64 spte;int nr_sptes =0 ; +if (!VALID_PAGE (vcpu->arch.mmu.root_hpa)) +return nr_sptes; +walk_shadow_page_lockless_begin (vcpu);for_each_shadow_entry_lockless (vcpu, addr, iterator, spte) { sptes[iterator.level-1 ] = spte;
arch/x86/kvm/paging_tmpl.h +8 -0
@@ -423,6 +423,9 @@ static int FNAME(fetch)(struct kvm_vcpuif (FNAME (gpte_changed)(vcpu, gw, top_level)) goto out_gpte_changed; +if (!VALID_PAGE (vcpu->arch.mmu.root_hpa)) + goto out_gpte_changed; +for (shadow_walk_init (&it, vcpu, addr);shadow_walk_okay (&it) && it.level > gw->level;shadow_walk_next (&it)) {
@@ -671,6 +674,11 @@ static void FNAME(invlpg)(struct kvm_vcp*/ mmu_topup_memory_caches (vcpu); +if (!VALID_PAGE (vcpu->arch.mmu.root_hpa)) { +WARN_ON (1 ); +return ; + } +spin_lock (&vcpu->kvm->mmu_lock);for_each_shadow_entry (vcpu, gva, iterator) { level = iterator.level;
Greg Kroah-Hartman
maintainerPATCH 18/22 KVM: VMX: fix use after free of vmx->loaded_vmcs
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Marcelo Tosatti <[email protected]>
commit 26a865f4aa8e66a6d94958de7656f7f1b03c6c56 upstream.
After free_loaded_vmcs executes, the "loaded_vmcs" structure is kfreed, and now vmx->loaded_vmcs points to a kfreed area. Subsequent free_loaded_vmcs then attempts to manipulate vmx->loaded_vmcs.
Switch the order to avoid the problem.
https://bugzilla.redhat.com/show_bug.cgi?id=1047892
--- arch/x86/kvm/vmx.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
arch/x86/kvm/vmx.c +1 -1
@@ -7133,8 +7133,8 @@ static void vmx_free_vcpu(struct kvm_vcpstruct vcpu_vmx *vmx =to_vmx (vcpu);free_vpid (vmx); -free_nested (vmx);free_loaded_vmcs (vmx->loaded_vmcs); +free_nested (vmx);kfree (vmx->guest_msrs);kvm_vcpu_uninit (vcpu);kmem_cache_free (kvm_vcpu_cache, vmx);
Greg Kroah-Hartman
maintainerPATCH 19/22 Input: wacom - make sure touch_max is set for touch devices
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ping Cheng <[email protected]>
commit 1d0d6df02750b4a6f466768cbfbf860e24f4c8d4 upstream.
Old single touch Tablet PCs do not have touch_max set at wacom_features. Since touch device at lease supports one finger, assign touch_max to 1 when touch usage is defined in its HID Descriptor and touch_max is not pre-defined.
--- drivers/input/tablet/wacom_sys.c | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-)
drivers/input/tablet/wacom_sys.c +5 -2
@@ -339,7 +339,7 @@ static int wacom_parse_hid(struct usb_instruct usb_device *dev =interface_to_usbdev (intf);char limit =0 ;/* result has to be defined as int for some devices */ -int result =0 ; +int result =0 , touch_max =0 ;int i =0 , usage =WCM_UNDEFINED , finger =0 , pen =0 ;unsigned char *report;
@@ -386,7 +386,8 @@ static int wacom_parse_hid(struct usb_inif (usage ==WCM_DESKTOP ) {if (finger) { features->device_type =BTN_TOOL_FINGER ; - +/* touch device at least supports one touch point */ + touch_max =1 ;switch (features->type) {case TABLETPC2FG : features->pktlen =WACOM_PKGLEN_TPC2FG ;
@@ -539,6 +540,8 @@ static int wacom_parse_hid(struct usb_in } out: +if (!features->touch_max && touch_max) + features->touch_max = touch_max; result =0 ;kfree (report);return result;
Greg Kroah-Hartman
maintainerPATCH 20/22 xhci: Fix resume issues on Renesas chips in Samsung laptops
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Sarah Sharp <[email protected]>
commit 1aa9578c1a9450fb21501c4f549f5b1edb557e6d upstream.
Don Zickus <[email protected]> writes:
Some co-workers of mine bought Samsung laptops that had mostly usb3 ports. Those ports did not resume correctly (the driver would timeout communicating and fail). This led to frustration as suspend/resume is a common use for laptops.
Poking around, I applied the reset on resume quirk to this chipset and the resume started working. Reloading the xhci_hcd module had been the temporary workaround.
--- drivers/usb/host/xhci-pci.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/usb/host/xhci-pci.c +5 -0
@@ -113,6 +113,11 @@ static void xhci_pci_quirks(struct devicxhci_dbg (xhci,"QUIRK: Resetting on resume\n" ); xhci->quirks |=XHCI_TRUST_TX_LENGTH ; } +if (pdev->vendor ==PCI_VENDOR_ID_RENESAS && + pdev->device ==0x0015 && + pdev->subsystem_vendor ==PCI_VENDOR_ID_SAMSUNG && + pdev->subsystem_device ==0xc0cd ) + xhci->quirks |=XHCI_RESET_ON_RESUME ;if (pdev->vendor ==PCI_VENDOR_ID_VIA ) xhci->quirks |=XHCI_RESET_ON_RESUME ; }
Greg Kroah-Hartman
maintainerPATCH 21/22 e100: Fix "disabling already-disabled device" warning
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Michele Baldessari <[email protected]>
commit 2b6e0ca175fe4a20f21ba82b1e7ccc71029c4dd4 upstream.
In https://bugzilla.redhat.com/show_bug.cgi?id=994438 and
https://bugzilla.redhat.com/show_bug.cgi?id=970480 we received different reports of e100 throwing the following warning:
[<c06a0ba5>] ? pci_disable_device+0x85/0x90
[<c044a153>] warn_slowpath_fmt+0x33/0x40 [<c06a0ba5>] pci_disable_device+0x85/0x90 [<f7fdf7e0>] __e100_shutdown+0x80/0x120 [e100] [<c0476ca5>] ? check_preempt_curr+0x65/0x90 [<f7fdf8d6>] e100_suspend+0x16/0x30 [e100] [<c06a1ebb>] pci_legacy_suspend+0x2b/0xb0 [<c098fc0f>] ? wait_for_completion+0x1f/0xd0 [<c06a2d50>] ? pci_pm_poweroff+0xb0/0xb0 [<c06a2de4>] pci_pm_freeze+0x94/0xa0 [<c0767bb7>] dpm_run_callback+0x37/0x80 [<c076a204>] ? pm_wakeup_pending+0xc4/0x140 [<c0767f12>] __device_suspend+0xb2/0x1f0 [<c076806f>] async_suspend+0x1f/0x90 [<c04706e5>] async_run_entry_fn+0x35/0x140 [<c0478aef>] ? wake_up_process+0x1f/0x40 [<c0464495>] process_one_work+0x115/0x370 [<c0462645>] ? start_worker+0x25/0x30 [<c0464dc5>] ? manage_workers.isra.27+0x1a5/0x250 [<c0464f6e>] worker_thread+0xfe/0x330 [<c0464e70>] ? manage_workers.isra.27+0x250/0x250 [<c046a224>] kthread+0x94/0xa0 [<c0997f37>] ret_from_kernel_thread+0x1b/0x28 [<c046a190>] ? insert_kthread_work+0x30/0x30
This patch removes pci_disable_device() from __e100_shutdown(). pci_clear_master() is enough.
--- drivers/net/ethernet/intel/e100.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/net/ethernet/intel/e100.c +1 -1
@@ -3039,7 +3039,7 @@ static void __e100_shutdown(struct pci_d *enable_wake = false; } -pci_disable_device (pdev); +pci_clear_master (pdev); }static int __e100_power_off (struct pci_dev *pdev,bool wake)
Greg Kroah-Hartman
maintainerPATCH 22/22 sched/autogroup: Fix race with task_groups list
In reply to Greg Kroah-Hartman3.10-stable review patch. If anyone has any objections, please let me know.
------------------
From: Gerald Schaefer <[email protected]>
commit 41261b6a832ea0e788627f6a8707854423f9ff49 upstream.
In autogroup_create(), a tg is allocated and added to the task_groups list. If CONFIG_RT_GROUP_SCHED is set, this tg is then modified while on the list, without locking. This can race with someone walking the list, like __enable_runtime() during CPU unplug, and result in a use-after-free bug.
To fix this, move sched_online_group(), which adds the tg to the list, to the end of the autogroup_create() function after the modification.
--- kernel/sched/auto_group.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
kernel/sched/auto_group.c +1 -2
@@ -77,8 +77,6 @@ static inline struct autogroup *autogrouif (IS_ERR (tg)) goto out_free; -sched_online_group (tg, &root_task_group); -kref_init (&ag->kref);init_rwsem (&ag->lock); ag->id =atomic_inc_return (&autogroup_seq_nr);
@@ -98,6 +96,7 @@ static inline struct autogroup *autogrou#endif tg->autogroup = ag; +sched_online_group (tg, &root_task_group);return ag; out_free:
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.35 release. There are 22 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 Sun Mar 30 17:30:55 UTC 2014. Anything received after that time might be too late.
Build results:
total: 126 pass: 121 skipped: 4 fail: 1
qemu tests all passed.
Results are as expected.
Details are available at http://server.roeck-us.net:8010/builders.
Guenter
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.10.35 release. There are 22 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 Sun Mar 30 17:30:55 UTC 2014. Anything received after that time might be too late.
Quoted 8 lines
The whole patch series can be found in one patch at:
kernel.org/pub/linux/kernel/v3.0/stable-review/patch-3.10.35-rc1.gzand the diffstat can be found below.
thanks,
greg k-h
Compiled, and booted on my test systems. No regressions in dmesg.
-- Shuah
Signature · 4 lines
Shuah Khan Senior Linux Kernel Developer - Open Source Group Samsung Research America(Silicon Valley) [email protected] | (970) 672-0658