On Fri, 17 Jan 2014, Sarah Sharp wrote:
> > Allow me to propose an alternative.
> >
> > Let's do our best to treat root hubs the same as external hubs. This
> > means that udev->lpm_capable should be set the same way in
> > hub_port_init() and register_root_hub(): by calling
> > usb_device_su
On Tue, Jan 14, 2014 at 02:43:40PM -0500, Alan Stern wrote:
> On Tue, 14 Jan 2014, Sarah Sharp wrote:
>
> > Alan, I believe your analysis of the code was incorrect when you asked
> > Xenia to create commit 60e102ac73cd40069d077014c93c86dc7205cb68 in
> > August:
> >
> > http://marc.info/?l=linux-u
On 01/17/2014 10:17 AM, ZHAO Gang wrote:
Use the right function to update frequency value.
If rx skb is probe response or beacon, the wrong frequency value can
cause problem that bss info can't be updated when it should be.
Cc:
Fixes: 8318d78a44d4 ("cfg80211 API for channels/bitrates, mac80211
2014-01-17 12:18-0800, Greg KH:
> On Fri, Jan 17, 2014 at 08:52:42PM +0100, Radim Krčmář wrote:
> > We should open NMI window right after an iret, but SVM exits before it.
> > We wanted to single step using the trap flag and then open it.
> > (or we could emulate the iret instead)
> > We don't do i
On Fri, Jan 17, 2014 at 08:52:42PM +0100, Radim Krčmář wrote:
> We should open NMI window right after an iret, but SVM exits before it.
> We wanted to single step using the trap flag and then open it.
> (or we could emulate the iret instead)
> We don't do it since commit 3842d135ff2 (likely), becau
We should always make sure the cached page is up-to-date when we're
determining whether we can extend a write to cover the full page -- even
if we've received a write delegation from the server.
Commit c7559663 added logic to skip this check if we have a write
delegation, which can lead to data co
We should open NMI window right after an iret, but SVM exits before it.
We wanted to single step using the trap flag and then open it.
(or we could emulate the iret instead)
We don't do it since commit 3842d135ff2 (likely), because the iret exit
handler does not request an event, so NMI window rema
[[ this was already added to 3.4-stable, I am sending it to the stable
mailing list for 3.2, 3.0 and others stable kernels ]]
This is backport of upstream commit
bbd465df73f0d8ba41b8a0732766a243d0f5b356, modified for stable kernels
2.6.39 - 3.7.
This patch fixes warnings due to missing loc
This is a note to let you know that I've just added the patch titled
KVM: x86: Convert vapic synchronization to _cached functions (CVE-2013-6368)
to the 3.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename o
This is a note to let you know that I've just added the patch titled
ARM: 7815/1: kexec: offline non panic CPUs on Kdump panic
to the 3.10-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
The filename of the patch is:
On Wed, Jan 15, 2014 at 11:57:20AM +0800, l00221744 wrote:
> hi Greg,
>
> 4f9b4fb7a2091eec339413a460b1665758401828
> ARM: 7815/1: kexec: offline non panic CPUs on Kdump panic
>
> This looks applicable to stable-3.10, that offlines non panic CPUs on
> Kdump panic. Without this patch, the Kdump pan
Use the right function to update frequency value.
If rx skb is probe response or beacon, the wrong frequency value can
cause problem that bss info can't be updated when it should be.
Cc:
Fixes: 8318d78a44d4 ("cfg80211 API for channels/bitrates, mac80211
and driver conversion")
Signed-off-by: ZHA
On Thu, Jan 16 2014, Andrzej Pietrasiewicz wrote:
> Fix possible NULL pointer dereference introduced in
>
> 219580e64f035bb9018dbb08d340f90b0ac50f8c
> usb: f_fs: check quirk to pad epout buf size when not aligned to
> maxpacketsize
>
> after 3.13-rc1.
>
> In cases we do wait with:
>
> wait_event_in
On Fri, 2014-01-17 at 23:19 +0800, ZHAO Gang wrote:
> Use the right function to update status.freq. The wrong frequency
> value can cause problem that bss info can't be updated when it
> should be.
>
> This bug is introduced by commit 8318d78a44d49ac1edf2bdec7299de3617c4232e
> "cfg80211 API for ch
Use the right function to update status.freq. The wrong frequency
value can cause problem that bss info can't be updated when it
should be.
This bug is introduced by commit 8318d78a44d49ac1edf2bdec7299de3617c4232e
"cfg80211 API for channels/bitrates, mac80211 and driver conversion".
Cc: Stable
S
From: walt
> Oy, Sarah! ;) I put the ASMedia adapter in my older amd64 machine, and, well,
> the stupid thing Just Works(TM) with kernel 3.12.7! (Yes, with the same disk
> docking station, too.)
>
> I can't believe the adapter works perfectly in a different computer. Have you
> seen this kind o
On Fri, Jan 17, 2014 at 8:46 AM, Marek Szyprowski
wrote:
> GFP_ATOMIC is not a single gfp flag, but a macro which expands to the other
> flags and LACK of __GFP_WAIT flag. To check if caller wanted to perform an
> atomic allocation, the code must test __GFP_WAIT flag presence. This patch
> fixes t
GFP_ATOMIC is not a single gfp flag, but a macro which expands to the other
flags and LACK of __GFP_WAIT flag. To check if caller wanted to perform an
atomic allocation, the code must test __GFP_WAIT flag presence. This patch
fixes the issue introduced in v3.5-rc1
CC: stable@vger.kernel.org
Signed
GFP_ATOMIC is not a single gfp flag, but a macro which expands to the other
flags and LACK of __GFP_WAIT flag. To check if caller wanted to perform an
atomic allocation, the code must test __GFP_WAIT flag presence. This patch
fixes the issue introduced in v3.6-rc5
Signed-off-by: Marek Szyprowski
19 matches
Mail list logo
