3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Vyacheslav Dubeyko
commit 12f267a20aecf8b84a2a9069b9011f1661c779b4 upstream.
Change a u32 to loff_t hfsplus_file_truncate().
Signed-off-by: Vyacheslav Dubeyko
Cc: Christoph Hellwig
Commit-ID: 524eff183f51d080a83b348d0ea97c08b3607b9a
Gitweb: http://git.kernel.org/tip/524eff183f51d080a83b348d0ea97c08b3607b9a
Author: Jiri Olsa
AuthorDate: Mon, 6 May 2013 18:27:17 +0200
Committer: Ingo Molnar
CommitDate: Tue, 7 May 2013 13:17:28 +0200
perf: Fix EXIT event
Dne 7.5.2013 16:06, Yann E. MORIN napsal(a):
> It's strange that a kconfig-related change did not land in your tree
> before getting mainline...
It's quite simple. I wanted to look at the patch, but Andrew beat me to
it. I am not saying that I would have spotted the null pointer deref
myself :-).
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Krause
commit 5ae94c0d2f0bed41d6718be743985d61b7f5c47d upstream.
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Krause
commit 9b3e617f3df53822345a8573b6d358f6b9e5ed87 upstream.
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jiri Slaby
commit 37b7f3c76595e23257f61bd80b223de8658617ee upstream.
In commit b0de59b5733d ("TTY: do not update atime/mtime on read/write")
we removed timestamps from tty inodes to fix
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Jiri Slaby
commit b0de59b5733d18b0d1974a060860a8b5c1b36a2e upstream.
On http://vladz.devzero.fr/013_ptmx-timing.php, we can see how to find
out length of a password using timestamps of
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Konrad Rzeszutek Wilk
commit 66ff0fe9e7bda8aec99985b24daad03652f7304e upstream.
While we don't use the spinlock interrupt line (see for details
commit
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Krause
commit a5598bd9c087dc0efc250a5221e5d0e6f584ee88 upstream.
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Krause
commit 2d6fbfe733f35c6b355c216644e08e149c61b271 upstream.
The current code does not fill the msg_name member in case it is set.
It also does not set the msg_namelen
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Wei Yongjun
commit c802d759623acbd6e1ee9fbdabae89159a513913 upstream.
sizeof() when applied to a pointer typed expression gives the size of the
pointer, not that of the pointed data.
Commit-ID: 8527632dc95472adb571701e852479531c0567a2
Gitweb: http://git.kernel.org/tip/8527632dc95472adb571701e852479531c0567a2
Author: Paul Gortmaker
AuthorDate: Fri, 19 Apr 2013 15:10:50 -0400
Committer: Ingo Molnar
CommitDate: Tue, 7 May 2013 13:14:51 +0200
sched: Move
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Krause
commit d26d6504f23e803824e8ebd14e52d4fc0a0b09cb upstream.
The code in llcp_sock_recvmsg() does not initialize all the members of
struct sockaddr_nfc_llcp when filling the
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Krause
commit 4a184233f21645cf0b719366210ed445d1024d72 upstream.
The code in rose_recvmsg() does not initialize all of the members of
struct sockaddr_rose/full_sockaddr_rose
Commit-ID: 45ceebf77653975815d82fcf7cec0a164215ae11
Gitweb: http://git.kernel.org/tip/45ceebf77653975815d82fcf7cec0a164215ae11
Author: Paul Gortmaker
AuthorDate: Fri, 19 Apr 2013 15:10:49 -0400
Committer: Ingo Molnar
CommitDate: Tue, 7 May 2013 13:14:50 +0200
sched: Factor out load
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Vlad Yasevich
commit 4543fbefe6e06a9e40d9f2b28d688393a299f079 upstream.
A few drivers use dev_uc_sync/unsync to synchronize the
address lists from master down to slave/lower devices.
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: "niko...@redhat.com"
commit 69b0216ac255f523556fa3d4ff030d857eaaa37f upstream.
While the bonding module is unloading, it is considered that after
rtnl_link_unregister all bond devices
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Hannes Frederic Sowa
commit 31d1670e73f4911fe401273a8f576edc9c2b5fea upstream.
The limit of 0x3c00 is taken from the windows driver.
Suggested-by: Huang, Xiong
Cc: Huang, Xiong
Cc:
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: "niko...@redhat.com"
commit b6a5a7b9a528a8b4c8bec940b607c5dd9102b8cc upstream.
While enslaving a new device and after IFF_BONDING flag is set, in case
of failure it is not stripped from
On Mon, May 6, 2013 at 7:39 PM, Andy Lutomirski wrote:
> On Mon, May 6, 2013 at 4:04 PM, Jerome Glisse wrote:
>> On Mon, May 6, 2013 at 5:22 PM, Andy Lutomirski wrote:
>>> On Fri, May 3, 2013 at 4:00 PM, Andy Lutomirski wrote:
Signed-off-by: Andy Lutomirski
---
This needs
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Eric W. Biederman"
commit 0e82e7f6dfeec1013339612f74abc2cdd29d43d2 upstream.
It was reported that the following LSB test case failed
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Patrick McHardy
commit 124dff01afbdbff251f0385beca84ba1b9adda68 upstream.
Commit 130549fe ("netfilter: reset nf_trace in nf_reset") added code
to reset nf_trace in nf_reset(). This is
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Graf
commit 50bceae9bd3569d56744882f3012734d48a1d413 upstream.
If a TCP retransmission gets partially ACKed and collapsed multiple
times it is possible for the headroom to grow
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Krause
commit 60085c3d009b0df252547adb336d1ccca5ce52ec upstream.
The code in set_orig_addr() does not initialize all of the members of
struct sockaddr_tipc when filling the
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Vasily Averin
commit f0f6ee1f70c4eaab9d52cf7d255df4bd89f8d1c2 upstream.
currently cbq works incorrectly for limits > 10% real link bandwidth,
and practically does not work for limits >
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Balakumaran Kannan
commit 25fb6ca4ed9cad72f14f61629b68dc03c0d9713f upstream.
IPv6 Routing table becomes broken once we do ifdown, ifup of the loopback(lo)
interface. After down-up,
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Krause
commit c77a4b9cffb6215a15196ec499490d116dfad181 upstream.
For stream sockets the code misses to update the msg_namelen member
to 0 and therefore makes net/socket.c leak
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Wei Yongjun
commit 06848c10f720cbc20e3b784c0df24930b7304b93 upstream.
Fix to return a negative error code from the error handling
case instead of 0, as returned elsewhere in this
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Borkmann
commit 586c31f3bf04c290dc0a0de7fc91d20aa9a5ee53 upstream.
For sensitive data like keying material, it is common practice to zero
out keys before returning the memory
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet
commit 12fb3dd9dc3c64ba7d64cec977cca9b5fb7b1d4e upstream.
commit bd090dfc634d (tcp: tcp_replace_ts_recent() should not be called
from tcp_validate_incoming()) introduced a
Michal, All,
On Tue, May 07, 2013 at 03:47:18PM +0200, Michal Marek wrote:
> On 7.5.2013 15:21, Yann E. MORIN wrote:
> > Li, All,
> >
> > On Tue, May 07, 2013 at 10:40:59AM +0800, Li Zefan wrote:
> >> Searching PPC_EFIKA results segmentation fault, and it's because
> >> get_symbol_prop() returns
On Tue, May 07, 2013 at 10:30:47AM +0100, Ian Campbell wrote:
> On Mon, 2013-05-06 at 14:04 +0100, Konrad Rzeszutek Wilk wrote:
> > They are important structures and it is not clear at first
> > look what they are for.
> >
> > The xen_vcpu is a pointer. By default it points to the shared_info
> >
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Eric Dumazet
commit 97599dc792b45b1669c3cdb9a4b365aad0232f65 upstream.
Commit 4a94445c9a5c (net: Use ip_route_input_noref() in input path)
added a bug in IP defragmentation handling, as
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Linus Torvalds
commit 83f1b4ba917db5dc5a061a44b3403ddb6e783494 upstream.
Commit 257b5358b32f ("scm: Capture the full credentials of the scm
sender") changed the credentials passing code
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: "David S. Miller"
[ Commits f36391d2790d04993f48da6a45810033a2cdf847 and
f0af97070acbad5d6a361f485828223a4faaa0ee upstream. ]
As reported by Dave Kleikamp, when we emit cross calls to
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Mathias Krause
commit b860d3cc62877fad02863e2a08efff69a19382d2 upstream.
The L2TP code for IPv6 fails to initialize the l2tp_conn_id member of
struct sockaddr_l2tpip6 and therefore
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Steven Rostedt (Red Hat)"
commit d4ecbfc49b4b1d4b597fb5ba9e4fa25d62f105c5 upstream.
When gcc 4.6 on x86 is used, the function tracer will use the new
option -mfentry which does a call
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Steven Rostedt (Red Hat)"
commit 4df297129f622bdc18935c856f42b9ddd18f9f28 upstream.
Currently, the depth reported in the stack tracer stack_trace file
does not match the stack_max_size
On Thu, May 02, 2013 at 04:06:54PM +0200, Markus Trippelsdorf wrote:
> > Moo. I missed amd_e400_idle() returning early w/o enabling interrupts.
>
> This fixes the issue. Thanks.
Ditto.
Tested-by: Borislav Petkov
--
Regards/Gruss,
Boris.
Sent from a fat crate under my desk. Formatting is
Hi,
there is a NULL pointer dereference in xhci_free_dev if
xhci_alloc_dev timeouts while waiting for a slot. Fedora has several bugs
reporting this problem.
https://bugzilla.redhat.com/show_bug.cgi?id=957500
https://bugzilla.redhat.com/show_bug.cgi?id=959016
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Yinghai Lu
commit 545d6e189a41c94c11f55045a771118eccc9d9eb upstream.
Found problem on system that firmware that could handle pci aer.
Firmware get error reporting after pci injecting
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Tony Luck
commit d303e9e98fce56cdb3c6f2ac92f626fc2bd51c77 upstream.
Back 2010 during a revamp of the irq code some initializations
were moved from ia64_mca_init() to
On Mon, May 06, 2013 at 03:45:39PM -0700, Tejun Heo wrote:
> Changes since the last take[L] are
>
> * Unnecessary throtl_schedule_delayed_work() call dropped from 0007.
>
> * throtl_log() implement in 0021 forgot to print space after blkg
> path. Fixed.
>
> *
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Steven Rostedt (Red Hat)"
commit 87889501d0adfae10e3b0f0e6f2d7536eed9ae84 upstream.
Use the stack of stack_trace_call() instead of check_stack() as
the test pointer for max stack size.
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Michael Riesch
commit 88c5b5ce5cb57af6ca2a7cf4d5715fa320448ff9 upstream.
Signed-off-by: Michael Riesch
Cc: "David S. Miller"
Cc: Greg Kroah-Hartman
Cc: Jiri Benc
Cc: "Theodore Ts'o"
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dmitry Popov
commit d66954a066158781ccf9c13c91d0316970fe57b6 upstream.
There is a bug in cookie_v4_check (net/ipv4/syncookies.c):
flowi4_init_output(, 0, sk->sk_mark,
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ming Lei
commit f7db5e7660b122142410dcf36ba903c73d473250 upstream.
The inode->i_mutex isn't hold when updating filp->f_pos
in read()/write(), so the filp->f_pos might be read as
0 or 1
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Stephan Schreiber
commit 136f39ddc53db3bcee2befbe323a56d4fbf06da8 upstream.
The Linux Kernel contains some inline assembly source code which has
wrong asm register constraints in
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Ben Jencks
commit e7d3b6e22c871ba36d052ca99bc8ceca4d546a60 upstream.
Add the Apple 24" LED Cinema display to the supported devices.
Signed-off-by: Ben Jencks
Signed-off-by: Greg
On Tue, 2013-05-07 at 18:30 +0530, Amit Daniel Kachhap wrote:
> This code bifurcates exynos thermal implementation into common and sensor
> specific parts. The common thermal code interacts with core thermal layer and
> core cpufreq cooling parts and is independent of SOC specific driver. This
>
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Theodore Ts'o
commit d76a3a77113db020d9bb1e894822869410450bd9 upstream.
In the case where an inode has a very stale transaction id (tid) in
i_datasync_tid or i_sync_tid, it's possible
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dmitry Monakhov
commit 794446c6946513c684d448205fbd76fa35f38b72 upstream.
The following race is possible:
[kjournald2] other_task
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dmitry Monakhov
commit 5d3ee20855e28169d711b394857ee608a5023094 upstream.
It is incorrect to use list_for_each_entry_safe() for journal callback
traversial because ->next may be removed
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Michael Grzeschik
commit a9c174302b1590ef3ead485d804a303c5f89174b upstream.
The udc uses an shared dma memory space between hard and software. This
memory layout is described in
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Michael Grzeschik
commit 7ca2cd291fd84ae499390f227a255ccba2780a81 upstream.
In hardware_enqueue code adds one extra td with dma_pool_alloc if
mReq->req.zero is true. When _ep_nuke will
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: David Engraf
commit 51fd36f3fad8447c487137ae26b9d0b3ce77bb25 upstream.
One can trigger an overflow when using ktime_add_ns() on a 32bit
architecture not supporting CONFIG_KTIME_SCALAR.
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Daniel Lezcano
commit 0d97558901c446a989de202a5d9ae94ec53644e5 upstream.
The TIME_VALID flag is specified for the different states but
the time residency computation is not done, no tk
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: =?UTF-8?q?Bj=C3=B8rn=20Mork?=
commit a2a2d6c7f93e160b52a4ad0164db1f43f743ae0f upstream.
Adding support for a Mediatek based device labelled as
D-Link Model: DWM-156, H/W Ver: A7
Also
On Mon 2013-05-06 23:24:16, Arnd Bergmann wrote:
> On Monday 06 May 2013, Pavel Machek wrote:
> > On Mon 2013-05-06 15:45:22, Arnd Bergmann wrote:
> > > On Monday 06 May 2013, Pavel Machek wrote:
> > > >
> > > > Hi!
> > > >
> > > > Ping? Previous version was tested by Dinh, and this one is based
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Namhyung Kim
commit 39e30cd1537937d3c00ef87e865324e981434e5b upstream.
The first page was allocated separately, so no need to start from 0.
Link:
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Trond Myklebust
commit 8b6cc4d6f841d31f72fe7478453759166d366274 upstream.
A server shouldn't normally return NFS4ERR_GRACE if the client holds a
delegation, since no conflicting lock
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Li Zefan
commit 3ac1707a13a3da9cfc8f242a15b2fae6df2c5f88 upstream.
The 3rd parameter of flex_array_prealloc() is the number of elements,
not the index of the last element.
The effect
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Steven Rostedt (Red Hat)"
commit 7fe70b579c9e3daba71635e31b6189394e7b79d3 upstream.
ftrace_dump() had a lot of issues. What ftrace_dump() does, is when
ftrace_dump_on_oops is set (via
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Stephan Schreiber
commit de53e9caa4c6149ef4a78c2f83d7f5b655848767 upstream.
The Linux Kernel contains some inline assembly source code which has
wrong asm register constraints in
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Prarit Bhargava
commit 8f294b5a139ee4b75e890ad5b443c93d1e558a8b upstream.
The settimeofday01 test in the LTP testsuite effectively does
gettimeofday(current time);
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Dmitry Monakhov
commit 171a7f21a76a0958c225b97c00a97a10390d40ee upstream.
Signed-off-by: Dmitry Monakhov
Signed-off-by: "Theodore Ts'o"
Signed-off-by: Luis Henriques
---
From: Miklos Szeredi
The PID and the TGID of the process tringgering the mount are sent to the
daemon. Currently the global pid values are sent (ones valid in the initial pid
namespace) but this is wrong if the autofs daemon itself is not running in the
initial pid namespace.
So send the pid
From: Li Zefan
Searching PPC_EFIKA results segmentation fault, and it's because
get_symbol_prop() returns NULL.
In this case CONFIG_PPC_EFIKA is defined in arch/powerpc/platforms/
52xx/Kconfig, so it won't be parsed if ARCH!=PPC, but menuconfig
knows this symbol when it parses
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Hans de Goede
commit 1361bf4b9f9ef45e628a5b89e0fd9bedfdcb7104 upstream.
When usbfs receives a ctrl-request from userspace it calls check_ctrlrecip,
which for a request with
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Emmanuel Grumbach
commit 63b77bf489881747c5118476918cc8c29378ee63 upstream.
When the stations are being restored because of unassoc
RXON, the LQ cmd may not have been initialized
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Stanislaw Gruszka
commit 3309ccf7fcebceef540ebe90c65d2f94d745a45b upstream.
If on iwl_dump_nic_event_log() error occurs before that function
initialize buf, we process uninitiated
On Mon, May 06, 2013 at 03:46:12PM -0700, Tejun Heo wrote:
> With the recent updates, blk-throttle is finally ready for proper
> hierarchy support. Dispatching now honors service_queue->parent_sq
> and propagates correctly. The only thing missing is setting
> ->parent_sq correctly so that
On Tue, May 07, 2013 at 07:38:52PM +0800, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Fix to return -ENOMEM in the memory malloc of 'out' and 'img_swap' error
> handling case instead of 0, as done elsewhere in this function.
Applied, thanks. Please note my new e-mail address.
signature.asc
From: Sukadev Bhattiprolu
This patch enables autofs4 to work in a "container". oz_pgrp is converted from
pid_t to struct pid and this is stored at mount time based on the "pgrp=" option
or if the option is missing then the current pgrp.
The "pgrp=" option is interpreted in the PID namespace of
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Trond Myklebust
commit 1dfd89af8697a299e7982ae740d4695ecd917eef upstream.
After a server reboot, the reclaimer thread will recover all the existing
locks. For locks that are blocked,
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Theodore Ts'o
commit c5c72d814cf0f650010337c73638b25e6d14d2d4 upstream.
Commit fb0a387dcdc restricts block allocations for indirect-mapped
files to block groups less than
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Theodore Ts'o
commit 7f3e3c7cfcec148ccca9c0dd2dbfd7b00b7ac10f upstream.
Fox the Kconfig documentation for CONFIG_EXT4_DEBUG to match the
change made by commit a0b30c1229: ext4: use
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Namhyung Kim
commit 9f50afccfdc15d95d7331acddcb0f7703df089ae upstream.
The ftrace_graph_count can be decreased with a "!" pattern, so that
the enabled flag should be updated too.
Link:
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Federico Vaga
commit 5a65dcc04cda41f4122aacc37a5a348454645399 upstream.
The serial core uses device_find_child() but does not drop the reference to
the retrieved child after using it.
On Tue, 2013-05-07 at 10:42 +0200, Stanislaw Gruszka wrote:
> Can you explain why it is named passive_no_rx instead passive_no_tx ?
Emmanuel already commented on this, basically the error codes are all
for "I couldn't transmit this frame", so here we have "I couldn't
transmit this frame because
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Adrian Thomasset
commit 9f06d15f8db6946e41f73196a122b84a37938878 upstream.
The current ST Micro Connect Lite uses the FT4232H hi-speed quad USB
UART FTDI chip. It is also possible to
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Filippo Turato
commit d19bf5cedfd7d53854a3bd699c98b467b139833b upstream.
This adds PID for Olivetti Olicard 145 in option.c
Signed-off-by: Filippo Turato
Signed-off-by: Greg
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Alex A. Mihaylov"
commit 7e9dafd873034dd64ababcb858be424c4780ae13 upstream.
Some cards on Ralink RT30xx chipset not have correctly TX_MIXER_GAIN
value in them EEPROM/EFUSE. In this
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Tormod Volden
commit 671b4b2ba9266cbcfe7210a704e9ea487dcaa988 upstream.
Many cards based on CY7C68300A/B/C use the USB ID 04b4:6830 but only the
B and C variants (EZ-USB AT2LP) support
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Richard Cochran
commit cd4b04b4aaa3b0ec4d13a6f3d203b92eadbd upstream.
An early draft of the PHC patch series included an alarm in the
gianfar driver. During the review process, the
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: "Rafael J. Wysocki"
commit 769ba7212f2059ca9fe0c73371e3d415c8c1c529 upstream.
Commit b51306c (PCI: Set device power state to PCI_D0 for device
without native PM support) modified
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Yogesh Ashok Powar
commit c380aafb77b7435d010698fe3ca6d3e1cd745fde upstream.
PCI regions are associated with the device using
pci_request_region() call. Hence use pci_release_region()
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Namhyung Kim
commit ed6f1c996bfe4b6e520cf7a74b51cd6988d84420 upstream.
Check return value and bail out if it's NULL.
Link:
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Johannes Berg
commit 990de49f74e772b6db5208457b7aa712a5f4db86 upstream.
When a full scan 2.4 and 5 GHz scan is scheduled, but then the 2.4 GHz
part of the scan disables a 5.2 GHz
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Hugh Dickins
commit 6ee8630e02be6dd89926ca0fbc21af68b23dc087 upstream.
On architectures where a pgd entry may be shared between user and kernel
(e.g. ARM+LPAE), freeing page tables
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Yogesh Ashok Powar
commit 5b0d9b218b74042ff72bf4bfda6eeb2e4bf98397 upstream.
"drivers should call pci_release_region() AFTER
calling pci_disable_device()"
Please refer section 3.2
On Tue, 7 May 2013, Ian Campbell wrote:
> > > > @@ -301,6 +320,10 @@ static int __init xen_init_events(void)
> > > >
> > > > on_each_cpu(xen_percpu_init, NULL, 0);
> > > >
> > > > + pv_time_ops.steal_clock = xen_stolen_accounting;
> > > > +
On Tue, May 07, 2013 at 06:20:22PM +0500, Syed Salman Mansoor wrote:
> Signed-off-by: Syed Salman Mansoor
No,
this is still wrong:
Subject: [PATCH] x86, setup: Removed spaces, trailing character and suspect
code indent warnings and errors in a20.c This is a patch to the a20.c file that
This change reduces the size of the spinlocked and TASK_UNINTERRUPTIBLE
sections in rwsem_down_failed_common():
- We only need the sem->wait_lock to insert ourselves on the wait_list;
the waiter node can be prepared outside of the wait_lock.
- The task state only needs to be set to
When trying to acquire a read lock, the RWSEM_ACTIVE_READ_BIAS adjustment
doesn't cause other readers to block, so we never have to worry about waking
them back after canceling this adjustment in rwsem_down_read_failed().
We also never want to steal the lock in rwsem_down_read_failed(), so we
We are not planning to add some new waiter flags, so we can convert the
waiter type into an enumeration.
Background: David Howells suggested I do this back when I tried adding
a new waiter type for unfair readers. However, I believe the cleanup
applies regardless of that use case.
Signed-off-by:
Linus, I would like you to take this for v3.10.
These patches extend Alex Shi's work (which added write lock stealing
on the rwsem slow path) in order to provide rwsem write lock stealing
on the fast path (that is, without taking the rwsem's wait_lock).
I have unfortunately been unable to push
3.5.7.12 -stable review patch. If anyone has any objections, please let me
know.
--
From: Thomas Gleixner
commit 6f7a05d7018de222e40ca003721037a530979974 upstream.
Vitaliy reported that a per cpu HPET timer interrupt crashes the
system during hibernation. What happens is
Remove the rwsem_down_failed_common function and replace it with two
identical copies of its code in rwsem_down_{read,write}_failed.
This is because we want to make different optimizations in
rwsem_down_{read,write}_failed; we are adding this pure-duplication
step as a separate commit in order to
Using rwsem_atomic_update to try stealing the write lock forced us to
undo the adjustment in the failure path. We can have simpler and faster
code by using cmpxchg instead.
Signed-off-by: Michel Lespinasse
Reviewed-by: Peter Hurley
Acked-by: Davidlohr Bueso
Acked-by: Rik van Riel
---
401 - 500 of 1340 matches
Mail list logo