3.4.64-stable review
Subsystems (18)
Greg Kroah-Hartman
maintainercover 3.4.64-stable review
This is the start of the stable review cycle for the 3.4.64 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 Tue Oct 1 19:11:47 UTC 2013. 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.4.64-rc1.gz
and the diffstat can be found below.
thanks,
greg k-h
-------------
Pseudo-Shortlog of commits:
Greg Kroah-Hartman <[email protected]>
Linux 3.4.64-rc1
Daniel Santos <[email protected]>
kernel-doc: bugfix - multi-line macros
Ben Hutchings <[email protected]>
sfc: Fix efx_rx_buf_offset() for recycled pages
Andi Kleen <[email protected]>
perf tools: Handle JITed code in shared memory
Lino Sanfilippo <[email protected]>
fanotify: dont merge permission events
Peter Zijlstra <[email protected]>
perf: Fix perf_cgroup_switch for sw-events
Peter Zijlstra <[email protected]>
perf: Clarify perf_cpu_context::active_pmu usage by renaming it to ::unique_pmu
Li Zefan <[email protected]>
cgroup: fail if monitored file and event_control are in different cgroup
Alex Deucher <[email protected]>
drm/radeon/atom: workaround vbios bug in transmitter table on rs880 (v2)
Alex Deucher <[email protected]>
drm/radeon: fix handling of variable sized arrays for router objects
Alex Deucher <[email protected]>
drm/radeon: fix resume on some rs4xx boards (v2)
Alex Deucher <[email protected]>
drm/radeon: update line buffer allocation for dce6
Alex Deucher <[email protected]>
drm/radeon: update line buffer allocation for dce4.1/5
Alex Deucher <[email protected]>
drm/radeon: fix endian bugs in hw i2c atom routines
Alex Deucher <[email protected]>
drm/radeon: fix LCD record parsing
Ben Skeggs <[email protected]>
drm/ttm: fix the tt_populated check in ttm_tt_destroy()
Kees Cook <[email protected]>
HID: logitech-dj: validate output report details
Kees Cook <[email protected]>
HID: zeroplus: validate output report details
Kees Cook <[email protected]>
HID: provide a helper for validating hid reports
Daisuke Nishimura <[email protected]>
sched/fair: Fix small race where child->se.parent,cfs_rq might point to invalid ones
Stanislaw Gruszka <[email protected]>
rt2800: fix wrong TX power compensation
Fabio Porcedda <[email protected]>
net: usb: cdc_ether: Use wwan interface for Telit modules
Greg Kroah-Hartman <[email protected]>
Revert "sctp: fix call to SCTP_CMD_PROCESS_SACK in sctp_cmd_interpreter()"
-------------
Diffstat:
Makefile | 4 +-- drivers/gpu/drm/radeon/atombios_dp.c | 6 ++-- drivers/gpu/drm/radeon/atombios_encoders.c | 8 +++-- drivers/gpu/drm/radeon/atombios_i2c.c | 4 ++- drivers/gpu/drm/radeon/evergreen.c | 25 ++++++++++--- drivers/gpu/drm/radeon/evergreend.h | 4 +++ drivers/gpu/drm/radeon/radeon_atombios.c | 13 ++++--- drivers/gpu/drm/radeon/rs400.c | 9 +++-- drivers/gpu/drm/radeon/si.c | 23 +++++++++--- drivers/gpu/drm/radeon/sid.h | 4 +++ drivers/gpu/drm/ttm/ttm_tt.c | 2 +- drivers/hid/hid-core.c | 58 ++++++++++++++++++++++++++++++ drivers/hid/hid-logitech-dj.c | 10 ++++-- drivers/hid/hid-zpff.c | 18 +++------- drivers/net/ethernet/sfc/rx.c | 3 +- drivers/net/usb/cdc_ether.c | 5 +++ drivers/net/wireless/rt2x00/rt2800lib.c | 7 ++++ fs/notify/fanotify/fanotify.c | 6 ++++ include/linux/hid.h | 4 +++ include/linux/perf_event.h | 2 +- kernel/cgroup.c | 11 ++++++ kernel/events/core.c | 21 ++++++----- kernel/sched/fair.c | 14 +++++--- net/sctp/sm_sideeffect.c | 3 +- scripts/kernel-doc | 3 ++ tools/perf/util/map.c | 1 + 26 files changed, 211 insertions(+), 57 deletions(-)
Greg Kroah-Hartman
maintainerPATCH 1/22 Revert "sctp: fix call to SCTP_CMD_PROCESS_SACK in sctp_cmd_interpreter()"
3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Greg Kroah-Hartman <[email protected]>
This reverts commit c2f5b7507ac5d808f29287d77ee6148358d7fbfe which is commit f6e80abeab928b7c47cc1fbf53df13b4398a2bec.
Michal writes:
Mainline commit f6e80abe was introduced in v3.7-rc2 as a follow-up fix to commit
edfee033 sctp: check src addr when processing SACK to update transport state
(from v3.7-rc1) which changed the interpretation of third argument to sctp_cmd_process_sack() and sctp_outq_sack(). But as commit edfee033 has never been backported to stable branches, backport of commit f6e80abe actually breaks the code rather than fixing it.
--- net/sctp/sm_sideeffect.c | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-)
net/sctp/sm_sideeffect.c +1 -2
@@ -1610,9 +1610,8 @@ static int sctp_cmd_interpreter(sctp_eve asoc->outqueue.outstanding_bytes; sackh.num_gap_ack_blocks =0 ; sackh.num_dup_tsns =0 ; - chunk->subh.sack_hdr = &sackh;sctp_add_cmd_sf (commands,SCTP_CMD_PROCESS_SACK , -SCTP_CHUNK (chunk)); +SCTP_SACKH (&sackh));break ;case SCTP_CMD_DISCARD_PACKET :
Greg Kroah-Hartman
maintainerPATCH 2/22 net: usb: cdc_ether: Use wwan interface for Telit modules
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Fabio Porcedda <[email protected]>
commit 0092820407901a0b2c4e343e85f96bb7abfcded1 upstream.
--- drivers/net/usb/cdc_ether.c | 5 +++++ 1 file changed, 5 insertions(+)
drivers/net/usb/cdc_ether.c +5 -0
@@ -618,6 +618,11 @@ static const struct usb_device_id produc .bInterfaceProtocol = USB_CDC_PROTO_NONE, .driver_info = (unsigned long)&wwan_info, }, { +/* Telit modules */ +USB_VENDOR_AND_INTERFACE_INFO (0x1bc7 ,USB_CLASS_COMM , + USB_CDC_SUBCLASS_ETHERNET, USB_CDC_PROTO_NONE), + .driver_info = (kernel_ulong_t) &wwan_info, +}, {USB_INTERFACE_INFO (USB_CLASS_COMM ,USB_CDC_SUBCLASS_ETHERNET ,USB_CDC_PROTO_NONE ), .driver_info = (unsigned long) &cdc_info,
Greg Kroah-Hartman
maintainerPATCH 3/22 rt2800: fix wrong TX power compensation
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Stanislaw Gruszka <[email protected]>
commit 6e956da2027c767859128b9bfef085cf2a8e233b upstream.
We should not do temperature compensation on devices without EXTERNAL_TX_ALC bit set (called DynamicTxAgcControl on vendor driver). Such devices can have totally bogus TSSI parameters on the EEPROM, but still threaded by us as valid and result doing wrong TX power calculations.
This fix inability to connect to AP on slightly longer distance on some Ralink chips/devices.
--- drivers/net/wireless/rt2x00/rt2800lib.c | 7 +++++++ 1 file changed, 7 insertions(+)
drivers/net/wireless/rt2x00/rt2800lib.c +7 -0
@@ -2161,6 +2161,13 @@ static int rt2800_get_gain_calibration_dint i;/* +* First check if temperature compensation is supported. +*/ +rt2x00_eeprom_read (rt2x00dev,EEPROM_NIC_CONF1 , &eeprom); +if (!rt2x00_get_field16 (eeprom,EEPROM_NIC_CONF1_EXTERNAL_TX_ALC )) +return 0 ; + +/* * Read TSSI boundaries for temperature compensation from * the EEPROM. *
Greg Kroah-Hartman
maintainerPATCH 4/22 sched/fair: Fix small race where child->se.parent,cfs_rq might point to invalid ones
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daisuke Nishimura <[email protected]>
commit 6c9a27f5da9609fca46cb2b183724531b48f71ad upstream.
There is a small race between copy_process() and cgroup_attach_task() where child->se.parent,cfs_rq points to invalid (old) ones.
parent doing fork() | someone moving the parent to another cgroup
-------------------------------+---------------------------------------------
copy_process()
+ dup_task_struct()
-> parent->se is copied to child->se.
se.parent,cfs_rq of them point to old ones.
cgroup_attach_task()
+ cgroup_task_migrate()
-> parent->cgroup is updated.
+ cpu_cgroup_attach()
+ sched_move_task()
+ task_move_group_fair() +- set_task_rq()
-> se.parent,cfs_rq of parent
are updated.
+ cgroup_fork()
-> parent->cgroup is copied to child->cgroup. (*1)
+ sched_fork()
+ task_fork_fair()
-> se.parent,cfs_rq of child are accessed
while they point to old ones. (*2)
In the worst case, this bug can lead to "use-after-free" and cause a panic, because it's new cgroup's refcount that is incremented at (*1), so the old cgroup(and related data) can be freed before (*2).
In fact, a panic caused by this bug was originally caught in RHEL6.4.
BUG: unable to handle kernel NULL pointer dereference at (null)
IP: [<ffffffff81051e3e>] sched_slice+0x6e/0xa0
[...]
Call Trace:
[<ffffffff81051f25>] place_entity+0x75/0xa0
[<ffffffff81056a3a>] task_fork_fair+0xaa/0x160
[<ffffffff81063c0b>] sched_fork+0x6b/0x140
[<ffffffff8106c3c2>] copy_process+0x5b2/0x1450
[<ffffffff81063b49>] ? wake_up_new_task+0xd9/0x130
[<ffffffff8106d2f4>] do_fork+0x94/0x460
[<ffffffff81072a9e>] ? sys_wait4+0xae/0x100
[<ffffffff81009598>] sys_clone+0x28/0x30
[<ffffffff8100b393>] stub_clone+0x13/0x20
[<ffffffff8100b072>] ? system_call_fastpath+0x16/0x1b--- kernel/sched/fair.c | 14 +++++++++----- 1 file changed, 9 insertions(+), 5 deletions(-)
kernel/sched/fair.c +9 -5
@@ -5190,11 +5190,15 @@ static void task_fork_fair(struct task_s cfs_rq =task_cfs_rq (current); curr = cfs_rq->curr; -if (unlikely (task_cpu (p) != this_cpu)) { -rcu_read_lock (); -__set_task_cpu (p, this_cpu); -rcu_read_unlock (); - } +/* +* Not only the cpu but also the task_group of the parent might have +* been changed after parent->se.parent,cfs_rq were copied to +* child->se.parent,cfs_rq. So call __set_task_cpu() to make those +* of child point to valid ones. +*/ +rcu_read_lock (); +__set_task_cpu (p, this_cpu); +rcu_read_unlock ();update_curr (cfs_rq);
Greg Kroah-Hartman
maintainerPATCH 5/22 HID: provide a helper for validating hid reports
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kees Cook <[email protected]>
commit 331415ff16a12147d57d5c953f3a961b7ede348b upstream.
Many drivers need to validate the characteristics of their HID report during initialization to avoid misusing the reports. This adds a common helper to perform validation of the report exisitng, the field existing, and the expected number of values within the field.
--- drivers/hid/hid-core.c | 58 +++++++++++++++++++++++++++++++++++++++++++++++++ include/linux/hid.h | 4 +++ 2 files changed, 62 insertions(+)
drivers/hid/hid-core.c +58 -0
@@ -821,6 +821,64 @@ static int search(__s32 *array, __s32 vareturn -1 ; } +static const char *const hid_report_names[] = { +"HID_INPUT_REPORT" , +"HID_OUTPUT_REPORT" , +"HID_FEATURE_REPORT" , +}; +/** +* hid_validate_values - validate existing device report's value indexes +* +* @device: hid device +* @type: which report type to examine +* @id: which report ID to examine (0 for first) +* @field_index: which report field to examine +* @report_counts: expected number of values +* +* Validate the number of values in a given field of a given report, after +* parsing. +*/ +struct hid_report *hid_validate_values (struct hid_device *hid, +unsigned int type,unsigned int id, +unsigned int field_index, +unsigned int report_counts) +{ +struct hid_report *report; + +if (type >HID_FEATURE_REPORT ) { +hid_err (hid,"invalid HID report type %u\n" , type); +return NULL ; + } + +if (id >=HID_MAX_IDS ) { +hid_err (hid,"invalid HID report id %u\n" , id); +return NULL ; + } + +/* +* Explicitly not using hid_get_report() here since it depends on +* ->numbered being checked, which may not always be the case when +* drivers go to access report values. +*/ + report = hid->report_enum[type].report_id_hash[id]; +if (!report) { +hid_err (hid,"missing %s %u\n" , hid_report_names[type], id); +return NULL ; + } +if (report->maxfield <= field_index) { +hid_err (hid,"not enough fields in %s %u\n" , + hid_report_names[type], id); +return NULL ; + } +if (report->field[field_index]->report_count < report_counts) { +hid_err (hid,"not enough values in %s %u field %u\n" , + hid_report_names[type], id, field_index); +return NULL ; + } +return report; +} +EXPORT_SYMBOL_GPL (hid_validate_values); +/** * hid_match_report - check if driver's raw_event should be called *
include/linux/hid.h +4 -0
@@ -737,6 +737,10 @@ void hid_output_report(struct hid_reportstruct hid_device *hid_allocate_device (void );struct hid_report *hid_register_report (struct hid_device *device,unsigned type,unsigned id);int hid_parse_report (struct hid_device *hid,__u8 *start,unsigned size); +struct hid_report *hid_validate_values (struct hid_device *hid, +unsigned int type,unsigned int id, +unsigned int field_index, +unsigned int report_counts);int hid_check_keys_pressed (struct hid_device *hid);int hid_connect (struct hid_device *hid,unsigned int connect_mask);void hid_disconnect (struct hid_device *hid);
Greg Kroah-Hartman
maintainerPATCH 6/22 HID: zeroplus: validate output report details
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kees Cook <[email protected]>
commit 78214e81a1bf43740ce89bb5efda78eac2f8ef83 upstream.
The zeroplus HID driver was not checking the size of allocated values in fields it used. A HID device could send a malicious output report that would cause the driver to write beyond the output report allocation during initialization, causing a heap overflow:
[ 1442.728680] usb 1-1: New USB device found, idVendor=0c12, idProduct=0005 ... [ 1466.243173] BUG kmalloc-192 (Tainted: G W ): Redzone overwritten
CVE-2013-2889
--- drivers/hid/hid-zpff.c | 18 +++++------------- 1 file changed, 5 insertions(+), 13 deletions(-)
drivers/hid/hid-zpff.c +5 -13
@@ -70,21 +70,13 @@ static int zpff_init(struct hid_device *struct hid_report *report;struct hid_input *hidinput =list_entry (hid->inputs.next, struct hid_input, list); -struct list_head *report_list = - &hid->report_enum[HID_OUTPUT_REPORT ].report_list;struct input_dev *dev = hidinput->input; -int error; +int i, error; -if (list_empty (report_list)) { -hid_err (hid,"no output report found\n" ); -return -ENODEV ; - } - - report = list_entry(report_list->next, struct hid_report, list); - -if (report->maxfield <4 ) { -hid_err (hid,"not enough fields in report\n" ); -return -ENODEV ; +for (i =0 ; i <4 ; i++) { + report =hid_validate_values (hid,HID_OUTPUT_REPORT ,0 , i,1 ); +if (!report) +return -ENODEV ; } zpff =kzalloc (sizeof (struct zpff_device ),GFP_KERNEL );
Greg Kroah-Hartman
maintainerPATCH 7/22 HID: logitech-dj: validate output report details
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Kees Cook <[email protected]>
commit 297502abb32e225fb23801fcdb0e4f6f8e17099a upstream.
A HID device could send a malicious output report that would cause the logitech-dj HID driver to leak kernel memory contents to the device, or trigger a NULL dereference during initialization:
[ 304.424553] usb 1-1: New USB device found, idVendor=046d, idProduct=c52b ... [ 304.780467] BUG: unable to handle kernel NULL pointer dereference at 0000000000000028 [ 304.781409] IP: [<ffffffff815d50aa>] logi_dj_recv_send_report.isra.11+0x1a/0x90
CVE-2013-2895
--- drivers/hid/hid-logitech-dj.c | 10 ++++++++-- 1 file changed, 8 insertions(+), 2 deletions(-)
drivers/hid/hid-logitech-dj.c +8 -2
@@ -454,7 +454,7 @@ static int logi_dj_recv_send_report(strustruct hid_report *report;struct hid_report_enum *output_report_enum;u8 *data = (u8 *)(&dj_report->device_index); -int i; +unsigned int i; output_report_enum = &hdev->report_enum[HID_OUTPUT_REPORT ]; report = output_report_enum->report_id_hash[REPORT_ID_DJ_SHORT ];
@@ -464,7 +464,7 @@ static int logi_dj_recv_send_report(strureturn -ENODEV ; } -for (i =0 ; i < report->field[0 ]->report_count; i++) +for (i =0 ; i <DJREPORT_SHORT_LENGTH -1 ; i++) report->field[0 ]->value[i] = data[i];usbhid_submit_report (hdev, report,USB_DIR_OUT );
@@ -783,6 +783,12 @@ static int logi_dj_probe(struct hid_devi goto hid_parse_fail; } +if (!hid_validate_values (hdev,HID_OUTPUT_REPORT ,REPORT_ID_DJ_SHORT , +0 ,DJREPORT_SHORT_LENGTH -1 )) { + retval = -ENODEV ; + goto hid_parse_fail; + } +/* Starts the usb device and connects to upper interfaces hiddev and * hidraw */ retval =hid_hw_start (hdev,HID_CONNECT_DEFAULT );
Greg Kroah-Hartman
maintainerPATCH 8/22 drm/ttm: fix the tt_populated check in ttm_tt_destroy()
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ben Skeggs <[email protected]>
commit 182b17c8dc4e83aab000ce86587b6810e515da87 upstream.
After a vmalloc failure in ttm_dma_tt_alloc_page_directory(), ttm_dma_tt_init() will call ttm_tt_destroy() to cleanup, and end up inside the driver's unpopulate() hook when populate() has never yet been called.
On nouveau, the first issue to be hit because of this is that dma_address[] may be a NULL pointer. After working around this, ttm_pool_unpopulate() may potentially hit the same issue with the pages[] array.
It seems to make more sense to avoid calling unpopulate on already unpopulated TTMs than to add checks to all the implementations.
--- drivers/gpu/drm/ttm/ttm_tt.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-)
drivers/gpu/drm/ttm/ttm_tt.c +1 -1
@@ -170,7 +170,7 @@ void ttm_tt_destroy(struct ttm_tt *ttm)ttm_tt_unbind (ttm); } -if (likely (ttm->pages !=NULL )) { +if (ttm->state == tt_unbound) { ttm->bdev->driver->ttm_tt_unpopulate (ttm); }
Greg Kroah-Hartman
maintainerPATCH 9/22 drm/radeon: fix LCD record parsing
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit 95663948ba22a4be8b99acd67fbf83e86ddffba4 upstream.
If the LCD table contains an EDID record, properly account for the edid size when walking through the records.
This should fix error messages about unknown LCD records.
--- drivers/gpu/drm/radeon/radeon_atombios.c | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-)
drivers/gpu/drm/radeon/radeon_atombios.c +3 -1
@@ -1622,7 +1622,9 @@ struct radeon_encoder_atom_dig *radeon_akfree (edid); } } - record +=sizeof (ATOM_FAKE_EDID_PATCH_RECORD ); + record += fake_edid_record->ucFakeEDIDLength ? + fake_edid_record->ucFakeEDIDLength +2 : +sizeof (ATOM_FAKE_EDID_PATCH_RECORD );break ;case LCD_PANEL_RESOLUTION_RECORD_TYPE : panel_res_record = (ATOM_PANEL_RESOLUTION_PATCH_RECORD *)record;
Greg Kroah-Hartman
maintainerPATCH 10/22 drm/radeon: fix endian bugs in hw i2c atom routines
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit 4543eda52113d1e2cc0e9bf416f79597e6ef1ec7 upstream.
Need to swap the data fetched over i2c properly. This is the same fix as the endian fix for aux channel transactions.
--- drivers/gpu/drm/radeon/atombios_dp.c | 6 +++--- drivers/gpu/drm/radeon/atombios_i2c.c | 4 +++- 2 files changed, 6 insertions(+), 4 deletions(-)
drivers/gpu/drm/radeon/atombios_dp.c +3 -3
@@ -51,7 +51,7 @@ static char *pre_emph_names[] = {* or from atom. Note that atom operates on * dw units. */ -static void radeon_copy_swap (u8 *dst,u8 *src,u8 num_bytes,bool to_le) +void radeon_atom_copy_swap (u8 *dst,u8 *src,u8 num_bytes,bool to_le) {#ifdef __BIG_ENDIANu8 src_tmp[20 ], dst_tmp[20 ];/* used for byteswapping */
@@ -101,7 +101,7 @@ static int radeon_process_aux_ch(struct base = (unsigned char *)(rdev->mode_info.atom_context->scratch +1 ); -radeon_copy_swap (base, send, send_bytes, true); +radeon_atom_copy_swap (base, send, send_bytes, true); args.v1.lpAuxRequest =cpu_to_le16 ((u16)(0 +4 )); args.v1.lpDataOut =cpu_to_le16 ((u16)(16 +4 ));
@@ -138,7 +138,7 @@ static int radeon_process_aux_ch(struct recv_bytes = recv_size;if (recv && recv_size) -radeon_copy_swap (recv, base +16 , recv_bytes, false); +radeon_atom_copy_swap (recv, base +16 , recv_bytes, false);return recv_bytes; }
drivers/gpu/drm/radeon/atombios_i2c.c +3 -1
@@ -27,6 +27,8 @@#include "radeon.h" #include "atom.h" +extern void radeon_atom_copy_swap (u8 *dst,u8 *src,u8 num_bytes,bool to_le); +#define TARGET_HW_I2C_CLOCK 50/* these are a limitation of ProcessI2cChannelTransaction not the hw */
@@ -77,7 +79,7 @@ static int radeon_process_i2c_ch(struct }if (!(flags &HW_I2C_WRITE )) -memcpy (buf, base, num); +radeon_atom_copy_swap (buf, base, num, false);return 0 ; }
Greg Kroah-Hartman
maintainerPATCH 11/22 drm/radeon: update line buffer allocation for dce4.1/5
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit 0b31e02363b0db4e7931561bc6c141436e729d9f upstream.
We need to allocate line buffer to each display when setting up the watermarks. Failure to do so can lead to a blank screen. This fixes blank screen problems on dce4.1/5 asics.
Based on an initial fix from:
Jay Cornwall <[email protected]>
--- drivers/gpu/drm/radeon/evergreen.c | 25 +++++++++++++++++++++---- drivers/gpu/drm/radeon/evergreend.h | 4 ++++ 2 files changed, 25 insertions(+), 4 deletions(-)
drivers/gpu/drm/radeon/evergreen.c +21 -4
@@ -534,7 +534,8 @@ static u32 evergreen_line_buffer_adjust(struct drm_display_mode *mode, struct drm_display_mode *other_mode) { - u32 tmp; + u32 tmp, buffer_alloc, i; +u32 pipe_offset = radeon_crtc->crtc_id *0x20 ;/* * Line Buffer Setup * There are 3 line buffers, each one shared by 2 display controllers.
@@ -557,18 +558,34 @@ static u32 evergreen_line_buffer_adjust(* non-linked crtcs for maximum line buffer allocation. */ if (radeon_crtc->base.enabled && mode) { -if (other_mode) +if (other_mode) { tmp =0 ;/* 1/2 */ -else + buffer_alloc =1 ; + }else { tmp =2 ;/* whole */ - }else + buffer_alloc =2 ; + } + }else { tmp =0 ; + buffer_alloc =0 ; + }/* second controller of the pair uses second half of the lb */ if (radeon_crtc->crtc_id %2 ) tmp +=4 ;WREG32 (DC_LB_MEMORY_SPLIT + radeon_crtc->crtc_offset, tmp); +if (ASIC_IS_DCE41 (rdev) ||ASIC_IS_DCE5 (rdev)) { +WREG32 (PIPE0_DMIF_BUFFER_CONTROL + pipe_offset, +DMIF_BUFFERS_ALLOCATED (buffer_alloc)); +for (i =0 ; i < rdev->usec_timeout; i++) { +if (RREG32 (PIPE0_DMIF_BUFFER_CONTROL + pipe_offset) & +DMIF_BUFFERS_ALLOCATED_COMPLETED ) +break ; +udelay (1 ); + } + } +if (radeon_crtc->base.enabled && mode) {switch (tmp) {case 0 :
drivers/gpu/drm/radeon/evergreend.h +4 -0
@@ -472,6 +472,10 @@# define LATENCY_LOW_WATERMARK (x) ((x) << 0)# define LATENCY_HIGH_WATERMARK (x) ((x) << 16) +#define PIPE0_DMIF_BUFFER_CONTROL 0x0ca0 +# define DMIF_BUFFERS_ALLOCATED (x) ((x) << 0) +# define DMIF_BUFFERS_ALLOCATED_COMPLETED (1 << 4) +#define IH_RB_CNTL 0x3e00# define IH_RB_ENABLE (1 << 0)# define IH_IB_SIZE (x) ((x) << 1)/* log2 */
Greg Kroah-Hartman
maintainerPATCH 12/22 drm/radeon: update line buffer allocation for dce6
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit 290d24576ccf1aa0373d2185cedfe262d0d4952a upstream.
We need to allocate line buffer to each display when setting up the watermarks. Failure to do so can lead to a blank screen. This fixes blank screen problems on dce6 asics.
Fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=64850
Based on an initial fix from:
Jay Cornwall <[email protected]>
--- drivers/gpu/drm/radeon/si.c | 23 +++++++++++++++++++---- drivers/gpu/drm/radeon/sid.h | 4 ++++ 2 files changed, 23 insertions(+), 4 deletions(-)
drivers/gpu/drm/radeon/si.c +19 -4
@@ -411,7 +411,8 @@ static u32 dce6_line_buffer_adjust(strucstruct drm_display_mode *mode, struct drm_display_mode *other_mode) { - u32 tmp; + u32 tmp, buffer_alloc, i; +u32 pipe_offset = radeon_crtc->crtc_id *0x20 ;/* * Line Buffer Setup * There are 3 line buffers, each one shared by 2 display controllers.
@@ -426,16 +427,30 @@ static u32 dce6_line_buffer_adjust(struc* non-linked crtcs for maximum line buffer allocation. */ if (radeon_crtc->base.enabled && mode) { -if (other_mode) +if (other_mode) { tmp =0 ;/* 1/2 */ -else + buffer_alloc =1 ; + }else { tmp =2 ;/* whole */ - }else + buffer_alloc =2 ; + } + }else { tmp =0 ; + buffer_alloc =0 ; + }WREG32 (DC_LB_MEMORY_SPLIT + radeon_crtc->crtc_offset,DC_LB_MEMORY_CONFIG (tmp)); +WREG32 (PIPE0_DMIF_BUFFER_CONTROL + pipe_offset, +DMIF_BUFFERS_ALLOCATED (buffer_alloc)); +for (i =0 ; i < rdev->usec_timeout; i++) { +if (RREG32 (PIPE0_DMIF_BUFFER_CONTROL + pipe_offset) & +DMIF_BUFFERS_ALLOCATED_COMPLETED ) +break ; +udelay (1 ); + } +if (radeon_crtc->base.enabled && mode) {switch (tmp) {case 0 :
drivers/gpu/drm/radeon/sid.h +4 -0
@@ -57,6 +57,10 @@#define DMIF_ADDR_CALC 0xC00 +#define PIPE0_DMIF_BUFFER_CONTROL 0x0ca0 +# define DMIF_BUFFERS_ALLOCATED (x) ((x) << 0) +# define DMIF_BUFFERS_ALLOCATED_COMPLETED (1 << 4) +#define SRBM_STATUS 0xE50#define CC_SYS_RB_BACKEND_DISABLE 0xe80
Greg Kroah-Hartman
maintainerPATCH 13/22 drm/radeon: fix resume on some rs4xx boards (v2)
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit acf88deb8ddbb73acd1c3fa32fde51af9153227f upstream.
Setting MC_MISC_CNTL.GART_INDEX_REG_EN causes hangs on some boards on resume. The systems seem to work fine without touching this bit so leave it as is.
v2: read-modify-write the GART_INDEX_REG_EN bit. I suspect the problem is that we are losing the other settings in the register.
fixes:
https://bugs.freedesktop.org/show_bug.cgi?id=52952
--- drivers/gpu/drm/radeon/rs400.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
drivers/gpu/drm/radeon/rs400.c +6 -3
@@ -174,10 +174,13 @@ int rs400_gart_enable(struct radeon_devi/* FIXME: according to doc we should set HIDE_MMCFG_BAR=0, * AGPMODE30=0 & AGP30ENHANCED=0 in NB_CNTL */ if ((rdev->family ==CHIP_RS690 ) || (rdev->family ==CHIP_RS740 )) { -WREG32_MC (RS480_MC_MISC_CNTL , - (RS480_GART_INDEX_REG_EN |RS690_BLOCK_GFX_D3_EN )); + tmp =RREG32_MC (RS480_MC_MISC_CNTL ); + tmp |=RS480_GART_INDEX_REG_EN |RS690_BLOCK_GFX_D3_EN ; +WREG32_MC (RS480_MC_MISC_CNTL , tmp); }else { -WREG32_MC (RS480_MC_MISC_CNTL ,RS480_GART_INDEX_REG_EN ); + tmp =RREG32_MC (RS480_MC_MISC_CNTL ); + tmp |=RS480_GART_INDEX_REG_EN ; +WREG32_MC (RS480_MC_MISC_CNTL , tmp); }/* Enable gart */ WREG32_MC (RS480_AGP_ADDRESS_SPACE_SIZE , (RS480_GART_EN | size_reg));
Greg Kroah-Hartman
maintainerPATCH 14/22 drm/radeon: fix handling of variable sized arrays for router objects
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit fb93df1c2d8b3b1fb16d6ee9e32554e0c038815d upstream.
The table has the following format:
typedef struct _ATOM_SRC_DST_TABLE_FOR_ONE_OBJECT //usSrcDstTableOffset pointing to this structure
{
UCHAR ucNumberOfSrc; USHORT usSrcObjectID[1]; UCHAR ucNumberOfDst; USHORT usDstObjectID[1];
}ATOM_SRC_DST_TABLE_FOR_ONE_OBJECT;
usSrcObjectID[] and usDstObjectID[] are variably sized, so we can't access them directly. Use pointers and update the offset appropriately when accessing the Dst members.
--- drivers/gpu/drm/radeon/radeon_atombios.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
drivers/gpu/drm/radeon/radeon_atombios.c +6 -3
@@ -715,13 +715,16 @@ bool radeon_get_atom_connector_info_from (ATOM_SRC_DST_TABLE_FOR_ONE_OBJECT *) (ctx->bios + data_offset +le16_to_cpu (router_obj->asObjects[k].usSrcDstTableOffset)); +u8 *num_dst_objs = (u8 *) + ((u8 *)router_src_dst_table +1 + + (router_src_dst_table->ucNumberOfSrc *2 )); +u16 *dst_objs = (u16 *)(num_dst_objs +1 );int enum_id; router.router_id = router_obj_id; -for (enum_id =0 ; enum_id < router_src_dst_table->ucNumberOfDst; - enum_id++) { +for (enum_id =0 ; enum_id < (*num_dst_objs); enum_id++) {if (le16_to_cpu (path->usConnObjectId) == -le16_to_cpu (router_src_dst_table->usDstObjectID[enum_id])) +le16_to_cpu (dst_objs[enum_id]))break ; }
Greg Kroah-Hartman
maintainerPATCH 15/22 drm/radeon/atom: workaround vbios bug in transmitter table on rs880 (v2)
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Alex Deucher <[email protected]>
commit 91f3a6aaf280294b07c05dfe606e6c27b7ba3c72 upstream.
The OUTPUT_ENABLE action jumps past the point in the coder where the data_offset is set on certain rs780 cards. This worked previously because the OUTPUT_ENABLE action is always called immediately after the ENABLE action so the data_offset remained set. In 6f8bbaf568c7f2c497558bfd04654c0b9841ad57 (drm/radeon/atom: initialize more atom interpretor elements to 0), we explictly reset data_offset to 0 between atom calls which then caused this to fail. The fix is to just skip calling the OUTPUT_ENABLE action on the problematic chipsets. The ENABLE action does the same thing and more. Ultimately, we could probably drop the OUTPUT_ENABLE action all together on DCE3 asics.
fixes:
https://bugzilla.kernel.org/show_bug.cgi?id=60791
v2: only rs880 seems to be affected
--- drivers/gpu/drm/radeon/atombios_encoders.c | 8 ++++++-- 1 file changed, 6 insertions(+), 2 deletions(-)
drivers/gpu/drm/radeon/atombios_encoders.c +6 -2
@@ -1425,8 +1425,12 @@ radeon_atom_encoder_dpms_dig(struct drm_atombios_dig_encoder_setup (encoder,ATOM_ENABLE ,0 );atombios_dig_transmitter_setup (encoder,ATOM_TRANSMITTER_ACTION_SETUP ,0 ,0 );atombios_dig_transmitter_setup (encoder,ATOM_TRANSMITTER_ACTION_ENABLE ,0 ,0 ); -/* some early dce3.2 boards have a bug in their transmitter control table */ -if ((rdev->family !=CHIP_RV710 ) && (rdev->family !=CHIP_RV730 )) +/* some dce3.x boards have a bug in their transmitter control table. +* ACTION_ENABLE_OUTPUT can probably be dropped since ACTION_ENABLE +* does the same thing and more. +*/ +if ((rdev->family !=CHIP_RV710 ) && (rdev->family !=CHIP_RV730 ) && + (rdev->family !=CHIP_RS880 ))atombios_dig_transmitter_setup (encoder,ATOM_TRANSMITTER_ACTION_ENABLE_OUTPUT ,0 ,0 ); }if (ENCODER_MODE_IS_DP (atombios_get_encoder_mode (encoder)) && connector) {
Greg Kroah-Hartman
maintainerPATCH 16/22 cgroup: fail if monitored file and event_control are in different cgroup
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Li Zefan <[email protected]>
commit f169007b2773f285e098cb84c74aac0154d65ff7 upstream.
If we pass fd of memory.usage_in_bytes of cgroup A to cgroup.event_control of cgroup B, then we won't get memory usage notification from A but B!
What's worse, if A and B are in different mount hierarchy, we'll end up accessing NULL pointer!
Disallow this kind of invalid usage.
--- kernel/cgroup.c | 11 +++++++++++ 1 file changed, 11 insertions(+)
kernel/cgroup.c +11 -0
@@ -3476,6 +3476,7 @@ static int cgroup_write_event_control(st const char *buffer) {struct cgroup_event *event =NULL ; +struct cgroup *cgrp_cfile;unsigned int efd, cfd;struct file *efile =NULL ;struct file *cfile =NULL ;
@@ -3531,6 +3532,16 @@ static int cgroup_write_event_control(st goto fail; } +/* +* The file to be monitored must be in the same cgroup as +* cgroup.event_control is. +*/ + cgrp_cfile =__d_cgrp (cfile->f_dentry->d_parent); +if (cgrp_cfile != cgrp) { + ret = -EINVAL ; + goto fail; + } +if (!event->cft->register_event || !event->cft->unregister_event) { ret = -EINVAL ; goto fail;
Greg Kroah-Hartman
maintainerPATCH 17/22 perf: Clarify perf_cpu_context::active_pmu usage by renaming it to ::unique_pmu
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peter Zijlstra <[email protected]>
commit 3f1f33206c16c7b3839d71372bc2ac3f305aa802 upstream.
Stephane thought the perf_cpu_context::active_pmu name confusing and suggested using 'unique_pmu' instead.
This pointer is a pointer to a 'random' pmu sharing the cpuctx instance, therefore limiting a for_each_pmu loop to those where cpuctx->unique_pmu matches the pmu we get a loop over unique cpuctx instances.
--- include/linux/perf_event.h | 2 +- kernel/events/core.c | 12 ++++++------ 2 files changed, 7 insertions(+), 7 deletions(-)
include/linux/perf_event.h +1 -1
@@ -1063,7 +1063,7 @@ struct perf_cpu_context {int exclusive;struct list_head rotation_list;int jiffies_interval; -struct pmu *active_pmu; +struct pmu *unique_pmu;struct perf_cgroup *cgrp; };
kernel/events/core.c +6 -6
@@ -4332,7 +4332,7 @@ static void perf_event_task_event(structrcu_read_lock ();list_for_each_entry_rcu (pmu, &pmus, entry) { cpuctx =get_cpu_ptr (pmu->pmu_cpu_context); -if (cpuctx->active_pmu != pmu) +if (cpuctx->unique_pmu != pmu) goto next;perf_event_task_ctx (&cpuctx->ctx, task_event);
@@ -4478,7 +4478,7 @@ static void perf_event_comm_event(structrcu_read_lock ();list_for_each_entry_rcu (pmu, &pmus, entry) { cpuctx =get_cpu_ptr (pmu->pmu_cpu_context); -if (cpuctx->active_pmu != pmu) +if (cpuctx->unique_pmu != pmu) goto next;perf_event_comm_ctx (&cpuctx->ctx, comm_event);
@@ -4674,7 +4674,7 @@ got_name:rcu_read_lock ();list_for_each_entry_rcu (pmu, &pmus, entry) { cpuctx =get_cpu_ptr (pmu->pmu_cpu_context); -if (cpuctx->active_pmu != pmu) +if (cpuctx->unique_pmu != pmu) goto next;perf_event_mmap_ctx (&cpuctx->ctx, mmap_event, vma->vm_flags &VM_EXEC );
@@ -5750,8 +5750,8 @@ static void update_pmu_context(struct pm cpuctx =per_cpu_ptr (pmu->pmu_cpu_context, cpu); -if (cpuctx->active_pmu == old_pmu) - cpuctx->active_pmu = pmu; +if (cpuctx->unique_pmu == old_pmu) + cpuctx->unique_pmu = pmu; } }
@@ -5886,7 +5886,7 @@ skip_type: cpuctx->ctx.pmu = pmu; cpuctx->jiffies_interval =1 ;INIT_LIST_HEAD (&cpuctx->rotation_list); - cpuctx->active_pmu = pmu; + cpuctx->unique_pmu = pmu; } got_cpu_context:
Greg Kroah-Hartman
maintainerPATCH 18/22 perf: Fix perf_cgroup_switch for sw-events
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Peter Zijlstra <[email protected]>
commit 95cf59ea72331d0093010543b8951bb43f262cac upstream.
Jiri reported that he could trigger the WARN_ON_ONCE() in perf_cgroup_switch() using sw-events. This is because sw-events share a cpuctx with multiple PMUs.
Use the ->unique_pmu pointer to limit the pmu iteration to unique cpuctx instances.
--- kernel/events/core.c | 9 ++++++--- 1 file changed, 6 insertions(+), 3 deletions(-)
kernel/events/core.c +6 -3
@@ -368,6 +368,8 @@ void perf_cgroup_switch(struct task_strulist_for_each_entry_rcu (pmu, &pmus, entry) { cpuctx =this_cpu_ptr (pmu->pmu_cpu_context); +if (cpuctx->unique_pmu != pmu) +continue ;/* ensure we process each cpuctx once */ /* * perf_cgroup_events says at least one
@@ -391,9 +393,10 @@ void perf_cgroup_switch(struct task_struif (mode &PERF_CGROUP_SWIN ) {WARN_ON_ONCE (cpuctx->cgrp); -/* set cgrp before ctxsw in to -* allow event_filter_match() to not -* have to pass task around +/* +* set cgrp before ctxsw in to allow +* event_filter_match() to not have to pass +* task around */ cpuctx->cgrp =perf_cgroup_from_task (task);cpu_ctx_sched_in (cpuctx,EVENT_ALL , task);
Greg Kroah-Hartman
maintainerPATCH 19/22 fanotify: dont merge permission events
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Lino Sanfilippo <[email protected]>
commit 03a1cec1f17ac1a6041996b3e40f96b5a2f90e1b upstream.
Boyd Yang reported a problem for the case that multiple threads of the same thread group are waiting for a reponse for a permission event.
In this case it is possible that some of the threads are never woken up, even if the response for the event has been received
(see http://marc.info/?l=linux-kernel&m=131822913806350&w=2).
The reason is that we are currently merging permission events if they belong to the same thread group. But we are not prepared to wake up more than one waiter for each event. We do
wait_event(group->fanotify_data.access_waitq, event->response ||
atomic_read(&group->fanotify_data.bypass_perm));
and after that
event->response = 0;
which is the reason that even if we woke up all waiters for the same event some of them may see event->response being already set 0 again, then go back to sleep and block forever.
With this patch we avoid that more than one thread is waiting for a response by not merging permission events for the same thread group any more.
--- fs/notify/fanotify/fanotify.c | 6 ++++++ 1 file changed, 6 insertions(+)
fs/notify/fanotify/fanotify.c +6 -0
@@ -18,6 +18,12 @@ static bool should_merge(struct fsnotify old->tgid == new->tgid) {switch (old->data_type) {case (FSNOTIFY_EVENT_PATH ): +#ifdef CONFIG_FANOTIFY_ACCESS_PERMISSIONS +/* dont merge two permission events */ +if ((old->mask &FAN_ALL_PERM_EVENTS ) && + (new->mask &FAN_ALL_PERM_EVENTS )) +return false; +#endif if ((old->path.mnt == new->path.mnt) && (old->path.dentry == new->path.dentry))return true;
Greg Kroah-Hartman
maintainerPATCH 20/22 perf tools: Handle JITed code in shared memory
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Andi Kleen <[email protected]>
commit 89365e6c9ad4c0e090e4c6a4b67a3ce319381d89 upstream.
Need to check for /dev/zero.
Most likely more strings are missing too.
--- tools/perf/util/map.c | 1 + 1 file changed, 1 insertion(+)
tools/perf/util/map.c +1 -0
@@ -16,6 +16,7 @@ const char *map_type__name[MAP__NR_TYPESstatic inline int is_anon_memory (const char *filename) {return !strcmp (filename,"//anon" ) || + !strcmp (filename,"/dev/zero (deleted)" ) || !strcmp (filename,"/anon_hugepage (deleted)" ); }
Greg Kroah-Hartman
maintainerPATCH 21/22 sfc: Fix efx_rx_buf_offset() for recycled pages
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Ben Hutchings <[email protected]>
This bug fix is only for stable branches older than 3.10. The bug was fixed upstream by commit 2768935a4660 ('sfc: reuse pages to avoid DMA mapping/unmapping costs'), but that change is totally unsuitable for stable.
Commit b590ace09d51 ('sfc: Fix efx_rx_buf_offset() in the presence of swiotlb') added an explicit page_offset member to struct efx_rx_buffer, which must be set consistently with the u.page and dma_addr fields. However, it failed to add the necessary assignment in efx_resurrect_rx_buffer(). It also did not correct the calculation of efx_rx_buffer::dma_addr in efx_resurrect_rx_buffer(), which assumes that DMA-mapping a page will result in a page-aligned DMA address (exactly what swiotlb violates).
Add the assignment of efx_rx_buffer::page_offset and change the calculation of dma_addr to make use of it.
--- drivers/net/ethernet/sfc/rx.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
drivers/net/ethernet/sfc/rx.c +2 -1
@@ -311,8 +311,9 @@ static void efx_resurrect_rx_buffer(stru index = rx_queue->added_count & rx_queue->ptr_mask; new_buf =efx_rx_buffer (rx_queue, index); - new_buf->dma_addr = rx_buf->dma_addr ^ (PAGE_SIZE >>1 ); new_buf->u.page = rx_buf->u.page; + new_buf->page_offset = rx_buf->page_offset ^ (PAGE_SIZE >>1 ); + new_buf->dma_addr = state->dma_addr + new_buf->page_offset; new_buf->len = rx_buf->len; new_buf->flags =EFX_RX_BUF_PAGE ; ++rx_queue->added_count;
Greg Kroah-Hartman
maintainerPATCH 22/22 kernel-doc: bugfix - multi-line macros
In reply to Greg Kroah-Hartman3.4-stable review patch. If anyone has any objections, please let me know.
------------------
From: Daniel Santos <[email protected]>
commit 654784284430bf2739985914b65e09c7c35a7273 upstream.
Prior to this patch the following code breaks:
/**
* multiline_example - this breaks kernel-doc
*/
#define multiline_example( \
myparam)
Producing this error:
Error(somefile.h:983): cannot understand prototype: 'multiline_example( \ '
This patch fixes the issue by appending all lines ending in a blackslash (optionally followed by whitespace), removing the backslash and any whitespace after it prior to appending (just like the C pre-processor would).
This fixes a break in kerel-doc introduced by the additions to rbtree.h.
--- scripts/kernel-doc | 3 +++ 1 file changed, 3 insertions(+)
scripts/kernel-doc +3 -0
@@ -2045,6 +2045,9 @@ sub process_file($) { $section_counter = 0; while (<IN>) { + while (s/\\\s*$//) { + $_ .= <IN>; + } if ($state == 0) { if (/$doc_start/o) { $state = 1; # next line is always the function name
Quoted 5 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.4.64 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.
Quoted 7 lines
Responses should be made by Tue Oct 1 19:11:47 UTC 2013. 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.4.64-rc1.gzand the diffstat can be found below.
Build test results:
total: 103 pass: 89 skipped: 10 fail: 4
qemu:
microblaze, mips, mips64, ppc, sh, sparc, x86, x86_64 pass. arm, sparc64 skipped
Same results as with 3.4.63.
Guenter
Greg Kroah-Hartman
maintainerQuoted 14 lines · Guenter Roeck
Quoted 5 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.4.64 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.
Quoted 7 lines
Responses should be made by Tue Oct 1 19:11:47 UTC 2013. 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.4.64-rc1.gzand the diffstat can be found below.
Quoted 8 lines
Build test results:
total: 103 pass: 89 skipped: 10 fail: 4qemu:
microblaze, mips, mips64, ppc, sh, sparc, x86, x86_64 pass. arm, sparc64 skippedSame results as with 3.4.63.
Nice, thanks for testing and letting me know.
greg k-h
Quoted 8 lines · Greg Kroah-Hartman
This is the start of the stable review cycle for the 3.4.64 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 Tue Oct 1 19:11:47 UTC 2013. 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.4.64-rc1.gzand the diffstat can be found below.
thanks,
greg k-h
3.4.64-rc1 applied cleanly to 3.4.63
Compiled and booted on the following systems:
Samsung Series 9 900X4C Intel Corei5
HP ProBook 6475b AMD A10-4600M APU with Radeon(tm) HD Graphics
dmesgs look good. No regressions compared to the previous dmesgs for this release. dmesg emerg, crit, alert, err are clean. No regressions in warn.
Cross-compile testing: HP Compaq dc7700 SFF desktop: x86-64 Intel Core-i2:
Cross-compile tests results:
alpha: defconfig passed
arm: defconfig passed
arm64: not applicable
blackfin: defconfig passed
c6x: dsk6455_defconfig passed - defconfig isn't supported
mips: defconfig passed
mipsel: defconfig passed
powerpc: wii_defconfig passed
sh: defconfig passed
sparc: defconfig passed
tile: tilegx_defconfig passed
-- Shuah
Signature · 4 lines
Shuah Khan Senior Linux Kernel Developer - Open Source Group Samsung Research America(Silicon Valley) [email protected] | (970) 672-0658