3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Oleksij Rempel
[ Upstream commit d66eaf9f89502971fddcb0de550b01fa6f409d83 ]
in some cases where device is attched to xhci port and do not responding,
for example ath9k_htc with stalled
Hm, after this pull request, 'perf top' started misbehaving on older
kernels:
┌─Error:┐
│The sys_perf_event_open() syscall returned with 22 (Invalid
argument) for event
Hi Guenter,
Thank you for your feedback, I will rewrite the drivers for IIO then.
Best regards,
William MARKEZANA
Direct : + 33 (0) 582 082 286
http://www.meas-spec.com
-Message d'origine-
De : Guenter Roeck [mailto:groe...@gmail.com] De la part de Guenter Roeck
Envoyé : mardi 10
* Arnaldo Carvalho de Melo wrote:
> From: Arnaldo Carvalho de Melo
>
> Hi Ingo,
>
> Please consider pulling,
>
> - Arnaldo
>
> The following changes since commit 72f4a11d2fb16792f5e5107922652366194cfd66:
>
> Merge tag 'perf-urgent-for-mingo' of
>
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Curt Brune
[ Upstream commit 93d783bcca69bfacc8dc739d8a050498402587b5 ]
In adt7470_write_word_data(), which writes two bytes using
i2c_smbus_write_byte_data(), the return codes are
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mateusz Krawczuk
[ Upstream commit 49ccc142f9cbc33fdda18e8fa90c1c5b4a79c0ad ]
regmap.h requires linux/err.h if CONFIG_REGMAP is not defined. Without it I get
error.
CC
Hi Jaegeuk, Chao,
On 09/10/2013 08:52 AM, Jaegeuk Kim wrote:
> Hi,
>
> At first, thank you for the report and please follow the email writing
> rules. :)
>
> Anyway, I agree to the below issue.
> One thing that I can think of is that we don't need to use the
> spin_lock, since we don't care
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Andrew Vagin
[ Upstream commit ed5467da0e369e65b247b99eb6403cb79172bcda ]
tracing_read_pipe zeros all fields bellow "seq". The declaration contains
a comment about that, but it doesn't
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Joe Perches
[ Upstream commit d9d10a30964504af834d8d250a0c76d4ae91eb1e ]
Signed-off-by: Joe Perches
Signed-off-by: David S. Miller
Signed-off-by: Steven Rostedt
---
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Theodore Ts'o
[ Upstream commit a34eb503742fd25155fd6cff6163daacead9fbc3 ]
When we try to allocate an inode, and there is a race between two
CPU's trying to grab the same inode, _and_
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Nicholas Bellinger
[ Upstream commit ee60bddba5a5f23e39598195d944aa0eb2d455e5 ]
This patch fixes spc_emulate_inquiry_std() to add trailing ASCII
spaces for INQUIRY vendor + model
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Martin K. Petersen"
[ Upstream commit 7562523e84ddc742fe1f9db8bd76b01acca89f6b ]
If a device has the skip_vpd_pages flag set we should simply fail the
scsi_get_vpd_page() call.
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 7b70176421993866e616f1cbc4d0dd4054f1bf78 ]
On Mon, 2013-07-29 at 08:30 -0700, Eric Dumazet wrote:
> On Mon, 2013-07-29 at 13:09 +0100, Luis Henriques
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit a0db856a95a29efb1c23db55c02d9f0ff4f0db48 ]
Make sure the reserved fields, and padding (if any), are
fully initialized.
Based upon a patch by Dan
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit ff862a4668dd6dba962b1d2d8bd344afa6375683 ]
This is inspired by a5cc68f3d6 "af_key: fix info leaks in notify
messages". There are some struct members
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Neil Horman
[ Upstream commit cf3c4c03060b688cbc389ebc5065ebcce5653e96 ]
Self explanitory dma_mapping_error addition to the 8139 driver, based on this:
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "sumit.sax...@lsi.com"
[ Upstream commit 6431f5d7c6025f8b007af06ea090de308f7e6881 ]
Problem: When Hardware IOMMU is on, megaraid_sas driver initialization fails
in kdump kernel with
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit 8cb3b9c3642c0263d48f31d525bcee7170eedc20 ]
The "pvc" struct has a hole after pvc.sap_family which is not cleared.
Signed-off-by: Dan Carpenter
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Hannes Frederic Sowa
[ Upstream commit 905a6f96a1b18e490a75f810d733ced93c39b0e5 ]
Otherwise we end up dereferencing the already freed net->ipv6.mrt pointer
which leads to a panic (from
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Tejun Heo
[ Upstream commit b22ce2785d97423846206cceec4efee0c4afd980 ]
If !PREEMPT, a kworker running work items back to back can hog CPU.
This becomes dangerous when a self-requeueing
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Neil Horman
[ Upstream commit 803075dba31c17af110e1d9a915fe7262165b213 ]
Recently we added an early quirk to detect 5500/5520 chipsets
with early revisions that had problems with irq
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Michal Tesar
[ Upstream commit 651e92716aaae60fc41b9652f54cb6803896e0da ]
Limit the min/max value passed to the
/proc/sys/net/ipv4/tcp_syn_retries.
Signed-off-by: Michal Tesar
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit 087d273caf4f7d3f2159256f255f1f432bc84a5b ]
This patch doesn't change the compiled code because ARC_HDR_SIZE is 4
and sizeof(int) is 4, but the intent
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Lan Tianyu
[ Upstream commit 016d5baad04269e8559332df05f89bd95b52d6ad ]
The _BIX method returns extended battery info as a package.
According the ACPI spec (ACPI 5, Section 10.2.2.2),
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "H.J. Lu"
[ Upstream commit eaa5a990191d204ba0f9d35dbe5505ec2cdd1460 ]
GCC will optimize mxcsr_feature_mask_init in arch/x86/kernel/i387.c:
memset(_scratch, 0,
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Li Zefan
[ Upstream commit 084457f284abf6789d90509ee11dae383842b23b ]
cgroup_cfts_commit() uses dget() to keep cgroup alive after cgroup_mutex
is dropped, but dget() won't prevent
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Oleg Nesterov
[ Upstream commit 8742f229b635bf1c1c84a3dfe5e47c814c20b5c8 ]
Ensure that user_namespace->parent chain can't grow too much.
Currently we use the hardroded 32 as limit.
On Fri, Sep 06, 2013 at 10:59:16PM -0700, Hugh Dickins wrote:
> Hit divide-by-0 in vmpressure_work_fn(): checking vmpr->scanned before
> taking the lock is not enough, we must check scanned afterwards too.
>
> Signed-off-by: Hugh Dickins
> Cc: sta...@vger.kernel.org
Hm... Just trying to
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit de1e0c40aceb9d5bff09c3a3b97b2f1b178af53f ]
The ->reserved field isn't cleared so we leak one byte of stack
information to userspace.
Signed-off-by: Dan
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Jiang Liu
[ Upstream commit 39a9b8ac9333e4268ecff7da6c9d1ab3823ff243 ]
On error recovery path of zram_init(), it leaks the zram device object
causing the failure. So change
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Jiang Liu
[ Upstream commit 5863e10b441e7ea4b492f930f1be180a97d026f3 ]
Use zram->init_lock to protect access to zram->meta, otherwise it
may cause invalid memory access if zram->meta
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Jiang Liu
[ Upstream commit 57ab048532c0d975538cebd4456491b5c34248f4 ]
zram_slot_free_notify() is free-running without any protection from
concurrent operations. So there are race
* Andi Kleen wrote:
> On Tue, Sep 10, 2013 at 04:52:12PM -0700, Andrew Morton wrote:
> > On Sat, 31 Aug 2013 20:22:23 +0200 Geert Uytterhoeven
> > wrote:
> >
> > > On Fri, Aug 16, 2013 at 11:17 PM, Andi Kleen wrote:
> > > > might_sleep is moving from linux/kernel.h to linux/sched.h, so any
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: =?UTF-8?q?Tomasz=20Mo=C5=84?=
[ Upstream commit 83e612f632c3897be29ef02e0472f6d63e258378 ]
Both type and pkt_len variables are in host endian and these should be in
Little Endian in
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Stanislaw Gruszka
[ Upstream commit e2288b66fe7ff0288382b2af671b4da558b44472 ]
Since we clear QUEUE_STARTED in rt2x00queue_stop_queue(), following
call to rt2x00queue_pause_queue()
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Jiang Liu
[ Upstream commit 12a7ad3b810e77137d0caf97a6dd97591e075b30 ]
Function valid_io_request() should verify the entire request are within
the zram device address range. Otherwise
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Johannes Berg
[ Upstream commit 6b0f32745dcfba01d7be33acd1b40306c7a914c6 ]
The duplicate retransmission detection code in mac80211
erroneously attempts to do the check for every frame,
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Johannes Berg
[ Upstream commit e13bae4f807401729b3f27c7e882a96b8b292809 ]
As reported in https://bugzilla.kernel.org/show_bug.cgi?id=60514,
the station loop never initialises 'sinfo'
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Jiang Liu
[ Upstream commit 65c484609a3b25c35e4edcd5f2c38f98f5226093 ]
When doing a patial write and the whole page is filled with zero,
zram_bvec_write() will free uncmem twice.
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Cho, Yu-Chen"
[ Upstream commit 178c059e7640aa8e50213400c6f3dde00189d979 ]
This patch adds support for Mediatek Bluetooth device
T: Bus=02 Lev=01 Prnt=01 Port=03 Cnt=01 Dev#= 2
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Jiang Liu
[ Upstream commit 6030ea9b35971a4200062f010341ab832e878ac9 ]
Memory for zram->disk object may have already been freed after returning
from destroy_device(zram), then it's
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Imre Deak
[ Upstream commit 77fa4cbd5fa389e28419bbe8ac491b5fdd54840d ]
Fix the typo introduced in
commit 1a2eb4604b85c5efb343da8a4dcf41288fcfca85
Author: Keith Packard
Date: Wed
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Emmanuel Grumbach
[ Upstream commit a1923f1d4723e5757cefdd60f7c7ab30e472007a ]
This SKU was missing in the list of supported devices
https://bugzilla.kernel.org/show_bug.cgi?id=60577
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?=
[ Upstream commit 079a036f4283e2b0e5c26080b8c5112bc0cc1831 ]
Without this patch the driver waits ~1 ms for the UART to become idle. At
115200n8 this
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Oleksij Rempel
[ Upstream commit dc2a87f519a4d8cb376ab54f22b6b98a943b51ce ]
Currently we configure harwdare and clock, only after
interface start. In this case, if we reload module or
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Jacob Keller
[ Upstream commit 1eb9ac14c34a948bf1538bfb9034e8ab29099a64 ]
This patch fixes an issue with the 82598EB device, where lldpad is causing Tx
Hangs on the card as soon as it
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Michal Kazior
[ Upstream commit a0ec570f4f69c4cb700d743a915096c2c8f56a99 ]
These two events were sent to the default network
namespace.
This caused AP mode in a non-default netns to
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Vinod Koul
[ Upstream commit a8d30608eaed6cc759b8e2e8a842591f797f ]
the return value of SNDRV_COMPRESS_VERSION always return default -ENOTTY as the
return value was never updated
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Johan Hovold
[ Upstream commit 40c24f2893ba0ba7df485871f6aac0c197ceef5b ]
Fix race in device-type detection introduced by commit 0eafe4de ("USB:
serial: mos7840: add support for
On Tuesday 10 September 2013 12:51 AM, Nishanth Menon wrote:
On 08/26/2013 12:36 AM, Keerthy wrote:
The Patch adds nodes for TPS659038 PMIC for DRA7 boards.
It is based on top of:
http://comments.gmane.org/gmane.linux.ports.arm.omap/102459.
Documentation:
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: =?UTF-8?q?Uwe=20Kleine-K=C3=B6nig?=
[ Upstream commit d970d7fe65adff5efe75b4a73c4ffc9be57089f7 ]
The handler needs to ack the pending events before actually handling them.
Otherwise a
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Catalin Marinas
[ Upstream commit bdae73cd374e28db544fdd9b77de689a36e3c129 ]
As of commit b9d4d42ad9 (ARM: Remove __ARCH_WANT_INTERRUPTS_ON_CTXSW on
pre-ARMv6 CPUs), the mm switching
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Johan Hovold
[ Upstream commit d8a083cc746664916d9d36ed9e4d08a29525f245 ]
Fix race in mos7840_get_reg which unconditionally manipulated the
control urb (which may already be in use) by
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Aaro Koskinen
[ Upstream commit fe956a1d4081ce1a959f87df397a15e252201f10 ]
slots-fan on G5 Xserve is always running at full speed with windfarm_rm31
driver, resulting in a very high
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Jakob Bornecrantz
[ Upstream commit 6e4dcff3adbf25acb87e74500a58e3c07bdec40f ]
This fixes the piglit test texturing/max-texture-size
causing the VM to die due to a too large SVGA
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Russell King
[ Upstream commit a5463cd3435475386cbbe7b06e01292ac169d36f ]
If kuser helpers are not provided by the kernel, disable user access to
the vectors page. With the kuser
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Russell King
[ Upstream commit b9b32bf70f2fb710b07c94e13afbc729afe221da ]
Use linker magic to create the vectors and vector stubs: we can tell the
linker to place them at an
Hello Linus,
Please pull battery-2.6 git tree to receive changes prepared for the v3.12
release. Here is what we have:
New drivers:
- APM X-Gene system reboot driver by Feng Kan and Loc Ho (APM).
- Qualcomm MSM reboot/poweroff driver by Abhimanyu Kapur (Codeaurora).
- Texas Instruments
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Russell King
[ Upstream commit f6f91b0d9fd971c630cef908dde8fe8795aefbf8 ]
Provide a kernel configuration option to allow the kernel user helpers
to be removed from the vector page,
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Russell King
[ Upstream commit 19accfd373847ac3d10623c5d20f948846299741 ]
Move the machine vector stubs into the page above the vector page,
which we can prevent from being visible to
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Russell King
[ Upstream commit e39e3f3ebfef03450cf7bfa7a974a8c61f7980c8 ]
FIQ should no longer copy the FIQ code into the user visible vector
page. Instead, it should use the hidden
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Russell King
[ Upstream commit 5b43e7a383d69381ffe53423e46dd0fafae07da3 ]
Poison the memory between each kuser helper. This ensures that any
branch between the kuser helpers will be
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Russell King
[ Upstream commit f928d4f2a86f46b030fa0850385b4391fc2b5918 ]
Fill the empty regions of the vectors page with an exception generating
instruction. This ensures that any
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: "Rick Farina (Zero_Chaos)"
[ Upstream commit fed1f1ed90bce42ea010e2904cbc04e7b8304940 ]
RT Systems makes many usb serial cables based on the ftdi_sio driver for
programming various
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Huang Rui
[ Upstream commit 1974d494dea05ea227cb42f5e918828801e237aa ]
Per dwc3 2.50a spec, the is_devspec bit is used to distinguish the
Device Endpoint-Specific Event or
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Felipe Balbi
[ Upstream commit cdcedd6981194e511cc206887db661d016069d68 ]
In case we fail our ->udc_start() callback, we
should be ready to accept another modprobe following
the failed
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Sergey Senozhatsky
[ Upstream commit a01c34f72e7cd2624570818f579b5ab464f93de2 ]
Fix a warning from lockdep caused by calling flush_work() for
uninitialized hotplug work. Initialize
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Al Viro
[ Upstream commit acfec9a5a892f98461f52ed5770de99a3e571ae2 ]
Eric Sandeen has found a nasty livelock in sget() - take a mount(2) about
to fail. The superblock is on
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Yinghai Lu
[ Upstream commit d5c78673b1b28467354c2c30c3d4f003666ff385 ]
On one sytem that mtrr range is more then 44bits, in dmesg we have
[0.00] MTRR default type: write-back
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: David Vrabel
[ Upstream commit 179fbd5a45f0d4034cc6fd37b8d367a3b79663c4 ]
Unbinding an event channel (either with the ioctl or when the evtchn
device is closed) may deadlock because
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Alex Deucher
[ Upstream commit 03ed8cf9b28d886c64c7e705c7bb1a365fd8fb95 ]
Hopefully avoid more quirks in the future due to bogus
vbios dac data.
Signed-off-by: Alex Deucher
Cc:
On 09/10/2013 04:23 PM, Javier Martinez Canillas wrote:
> On 09/10/2013 09:52 PM, Stephen Warren wrote:
>> On 09/10/2013 07:56 AM, Javier Martinez Canillas wrote:
>> ...
>>> The only thing that this patch tries to solve is when a driver expect to
>>> request
>>> a IRQ and it doesn't care if is a
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Alex Deucher
[ Upstream commit 42a21826dc54583cdb79cc8477732e911ac9c376 ]
The ProcessAuxChannel table on some rv635 boards assumes
the divmul members are initialized to 0 otherwise we
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Konstantin Khlebnikov
[ Upstream commit 7dcd2677ea912573d9ed4bcd629b0023b2d11505 ]
This patch fixes regression in power consumtion of sandy bridge gpu, which
exists since v3.6
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Dave Kleikamp
[ Upstream commit 44512449c0ab368889dd13ae0031fba74ee7e1d2 ]
NFSv4 reserves readdir cookie values 0-2 for special entries (. and ..),
but jfs allows a value of 2 for a
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mark Kettenis
[ Upstream commit cef1d00cd56f600121ad121875655ad410a001b8 ]
Noticed that my old Radeon 7500 hung after printing
drm: GPU not posted. posting now...
when it wasn't
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Hannes Reinecke
[ Upstream commit 6c182cd88d179cbbd06f4f8a8a19b6977940753f ]
When multipath needs to retry an ioctl the reference to the
current live table needs to be dropped.
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Mikulas Patocka
[ Upstream commit b1bf2de07271932326af847a3c6a01fdfd29d4be ]
Fix a boundary condition that caused failure for certain device sizes.
The problem is reported at
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Alex Deucher
[ Upstream commit 34be8c9af7b8728465963740fc11136ae90dfc36 ]
The atom interpreter expects data in LE format, so
swap the message buffer as apprioriate.
v2: properly
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Harshula Jayasuriya
[ Upstream commit e4daf1ffbe6cc3b12aab4d604e627829e93e9914 ]
The following call chain:
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit b2781e1021525649c0b33fffd005ef219da33926 ]
My static checker marks everything from ntohl() as untrusted and it
complains we could have an underflow
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Anton Blanchard
[ Upstream commit 0e0ed6406e61434d3f38fb58aa8464ec4722b77e ]
Module CRCs are implemented as absolute symbols that get resolved by
a linker script. We build an
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: NeilBrown
[ Upstream commit f94c0b6658c7edea8bc19d13be321e3860a3fa54 ]
If a device in a RAID4/5/6 is being replaced while another is being
recovered, then the writes to the replacement
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: NeilBrown
[ Upstream commit 0eb25bb027a100f5a9df8991f2f628e7d851bc1e ]
We always need to be careful when calling generic_make_request, as it
can start a chain of events which might
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Takashi Iwai
[ Upstream commit fb615499f0ad28ed74201c1cdfddf9e64e205424 ]
The recent commit to delay the release of kobject triggered NULL
dereferences of opti9xx drivers. The cause
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Takashi Iwai
[ Upstream commit d3d3835ce919438c00c5d1270d6f9d6ffea59d03 ]
Yet another entry, just use the existing fixup for this machine, too.
Reported-by: "Nathanael D. Noblet"
Cc:
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Tejun Heo
[ Upstream commit bb9696192826a7d9279caf872e95b41bc26c7eff ]
sata_inic162x never reached a state where it's reliable enough for
production use and data corruption is a
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Toshi Kani
[ Upstream commit d19f503e22316a84c39bc19445e0e4fdd49b3532 ]
device->driver_data needs to be cleared when releasing its data,
mem_device, in an error path of
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Russ Anderson
[ Upstream commit 21ea9f5ace3a7317cc3ba1fbc749758021a83136 ]
"cat /sys/devices/system/memory/memory*/removable" crashed the system.
The problem is that
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Trond Myklebust
[ Upstream commit 347e2233b7667e336d9f671f1a52dfa3f0416e2c ]
Some architectures, such as ARM-32 do not return the same base address
when you call kmap_atomic() twice on
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: David Vrabel
[ Upstream commit 3bc38cbceb85881a8eb789ee1aa56678038b1909 ]
If there are UNUSABLE regions in the machine memory map, dom0 will
attempt to map them 1:1 which is not
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Kevin Hilman
[ Upstream commit 3f0fa9a808f98fa10a18ba2a73f13d65fda990fb ]
The use of WARN_ON() needs the definitions from bug.h, without it
you can get:
include/linux/regmap.h: In
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Benjamin Herrenschmidt
[ Upstream commit f5f6cbb61610b7bf9d9d96db9c3979d62a424bab ]
/proc/powerpc/lparcfg is an ancient facility (though still actively used)
which allows access to
On Tue, Sep 10, 2013 at 10:00 PM, Joe Perches wrote:
> On Tue, 2013-09-10 at 21:41 -0700, Kees Cook wrote:
>> Make sure that format strings cannot leak into printk() calls from the
>> msgbuf string.
>
> printf(string);
> vs
> printf("%s", string);
>
> How does this help?
In the
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Dan Carpenter
[ Upstream commit 909bd5926d474e275599094acad986af79671ac9 ]
We want the data stored in "addr" and "qual", but the extra ampersands
mean we are copying stack data
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Paul Mackerras
[ Upstream commit bdbc29c19b2633b1d9c52638fb732bcde7a2031a ]
On 64-bit, __pa(_var) gets miscompiled by recent versions of
gcc as something like:
addis
Op 10 sep. 2013, om 22:14 heeft Joel Fernandes het volgende
geschreven:
> On 09/10/2013 02:39 PM, Koen Kooi wrote:
>>
>> Op 10 sep. 2013, om 21:24 heeft Joel Fernandes het volgende
>> geschreven:
>>
>>> Here are last few patches required to add EDMA and MMC/SPI support for
>>> AM33xx.
>>>
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Roland Dreier
[ Upstream commit 35dc248383bbab0a7203fca4d722875bc81ef091 ]
There is a nasty bug in the SCSI SG_IO ioctl that in some circumstances
leads to one process writing data
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Daniel Drake
[ Upstream commit 93dbc1b3b506e16c1f6d5b5dcfe756a85cb1dc58 ]
Being a low-level component, various drivers (e.g. olpc-battery) assume
that it is ok to communicate with the
3.6.11.9-rc1 stable review patch.
If anyone has any objections, please let me know.
--
From: Emmanuel Grumbach
[ Upstream commit eabc4ac5d7606a57ee2b7308cb7323ea8f60183b ]
As Arjan pointed out, we mustn't do anything related to PCI
configuration until the device is properly
1 - 100 of 1878 matches
Mail list logo
