Like the JMicron JMS567 enclosures with the JMS566 choke on report-opcodes,
so avoid it.
Tested-and-reported-by: Takeo Nakayama javh...@gmx.com
Cc: stable@vger.kernel.org # 3.16
Signed-off-by: Hans de Goede hdego...@redhat.com
---
drivers/usb/storage/unusual_uas.h | 7 +++
1 file changed, 7
On 12/08/2014 08:16 AM, Joonsoo Kim wrote:
What we want to check here is whether there is highorder freepage
in buddy list of other migratetype in order to steal it without
fragmentation. But, current code just checks cc-order which means
allocation request order. So, this is wrong.
Without
This looks applicable to stable-3.10, which load cycle count after
epoch stabilizes. The function was moved from
arch/arm/kernel/sched_clock.c to kernel/time/sched_clock.c
because of upgrading version. I rearrange this patch for
fixing bug in stable-3.10.
The commit id is
There is a small race between when the cycle count is read from
the hardware and when the epoch stabilizes. Consider this scenario:
CPU0 CPU1
cyc = read_sched_clock()
cyc_to_sched_clock()
On 2014/12/6 17:57, Russell King - ARM Linux wrote:
On Fri, Dec 05, 2014 at 02:17:19PM -0800, Greg KH wrote:
On Fri, Nov 28, 2014 at 02:18:58AM +, xiaofeng.yan wrote:
From: Stephen Boyd sb...@codeaurora.org
There is a small race between when the cycle count is read from
the hardware and
From: Johannes Berg johannes.b...@intel.com
Upstream commit 4f031fa9f188b2b0641ac20087d9e16bcfb4e49d.
Commit 7ec7c4a9a686c608315739ab6a2b0527a240883c (mac80211: port CCMP to
cryptoapi's CCM driver) introduced a regression when decrypting empty
packets (data_len == 0). This will lead to
Hi Julian,
Am 07.12.2014 19:27, schrieb Julian Anastasov:
Hello,
On Fri, 5 Dec 2014, Smart Weblications GmbH - Florian Wiessner wrote:
thank you for the fast responses! I would like to test any patch for 3.12.
I'm attaching a patch that avoids rerouting in
IPVS for LOCAL_IN.
On Fri, 05 Dec 2014, Daniel Vetter dan...@ffwll.ch wrote:
On Fri, Dec 05, 2014 at 10:30:47AM -0800, Jesse Barnes wrote:
On Fri, 11 Apr 2014 15:55:17 +0200
Daniel Vetter daniel.vet...@ffwll.ch wrote:
Apparently stuff works that way on those machines.
I agree with Chris' concern that
On 05.12.2014 18:34, Felipe Balbi wrote:
From: Mathias Nyman mathias.ny...@linux.intel.com
commit 8e71a322fdb127814bcba423a512914ca5bc6cf5 upstream.
If a device is halted and reuturns a STALL, then the halted endpoint
needs to be cleared both on the host and device side. The host
side
As requested a version of the patch rebased on 3.17 is attached.
Regards,
Christian.
Am 07.12.2014 um 07:09 schrieb gre...@linuxfoundation.org:
The patch below does not apply to the 3.17-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email
On Sun, Dec 7, 2014 at 4:31 PM, Filipe Manana fdman...@suse.com wrote:
When we abort a transaction we iterate over all the ranges marked as
dirty
in fs_info-freed_extents[0] and fs_info-freed_extents[1], clear them
from those trees, add them back (unpin) to the free space caches and,
if
the fs
As requested a version of the patch rebased on 3.17 is attached.
Regards,
Christian.
Am 07.12.2014 um 07:09 schrieb gre...@linuxfoundation.org:
The patch below does not apply to the 3.17-stable tree.
If someone wants it applied there, or to any other stable or longterm
tree, then please email
On Mon, Dec 8, 2014 at 1:53 PM, Chris Mason c...@fb.com wrote:
On Sun, Dec 7, 2014 at 4:31 PM, Filipe Manana fdman...@suse.com wrote:
When we abort a transaction we iterate over all the ranges marked as dirty
in fs_info-freed_extents[0] and fs_info-freed_extents[1], clear them
from those
On Fri, Dec 05, 2014 at 07:03:28PM -0800, Andy Lutomirski wrote:
paravirt_enabled has the following effects:
- Disables the F00F bug workaround warning. There is no F00F bug
workaround any more because Linux's standard IDT handling already
works around the F00F bug, but the warning
Hi Mauro,
On 04/12/14 17:38, Mauro Carvalho Chehab wrote:
Em Mon, 1 Dec 2014 12:55:09 +
James Hogan james.ho...@imgtec.com escreveu:
When the img-ir driver is asked to change protocol, if the chosen
decoder is already loaded then don't call img_ir_set_decoder(), so as
not to clear the
Since commit da6e162d6a46 ([media] rc-core: simplify sysfs code), when
the IR protocol is set using the sysfs interface to the same set of
protocols that are already set, store_protocols() does not refresh the
scancode filter with the new protocol, even if it has already called the
On Fri, Dec 05, 2014 at 10:41:04AM +, Yingjoe Chen wrote:
On Sun, 2014-11-23 at 23:02 -0800, Sonny Rao wrote:
This is a bug fix for using physical arch timers when
the arch_timer_use_virtual boolean is false. It restores the
arch_counter_get_cntpct() function after removal in
On Mon, Dec 8, 2014 at 7:45 AM, Konrad Rzeszutek Wilk
konrad.w...@oracle.com wrote:
On Fri, Dec 05, 2014 at 07:03:28PM -0800, Andy Lutomirski wrote:
paravirt_enabled has the following effects:
- Disables the F00F bug workaround warning. There is no F00F bug
workaround any more because
On 12/06/2014 08:07 AM, Jiri Slaby wrote:
This is the start of the stable review cycle for the 3.12.35 release.
There are 66 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
Is anything wrong with this patch?
It was made against last mainline kernel at the moment.
If a patch against linux-next needed, I can make it.
Without this patch wireless is always blocked.
Regards,
Dmitry.
27.11.2014 19:39, Dmitry Tunin пишет:
Rfkill always shows wireless blocked unless
From: Dave Hansen dave.han...@linux.intel.com
We calculate nr_pages with f-flush_end and f-flush_start, both
of which are virtual addresses. However, we only divide
f-flush_start by PAGE_SIZE, and missed f-flush_end. This patch
adds some parenthesis to catch f-flush_end as well.
nr_pages is
From: Dave Hansen dave.han...@linux.intel.com
If flush_end ends up being at or above 1 page before the end of
memory, the following calculation can overflow:
f-flush_end = f-flush_start + PAGE_SIZE;
x86_64 has a 2MB hole at the end of memory, so we don't expect
this to be possible
Otherwise, if buggy user code points DS or ES into the TLS array,
they would be corrupted after a context switch.
- begin test case -
/*
* Copyright (c) 2014 Andy Lutomirski
* GPL v2
*/
static unsigned short GDT3(int idx)
{
return (idx 3) | 3;
}
static int create_tls(int
Hello,
On Mon, 8 Dec 2014, Smart Weblications GmbH - Florian Wiessner wrote:
Am 07.12.2014 19:27, schrieb Julian Anastasov:
I'm attaching a patch that avoids rerouting in
IPVS for LOCAL_IN. Please test it in your setup. My tests
were with NAT on today's net tree. I checked
Otherwise, if buggy user code points DS or ES into the TLS array,
they would be corrupted after a context switch.
This also significantly improves the comments and documents some
gotchas in the code.
Before this patch, the both tests below failed. With this patch,
the es test passes, although
The rule is simple. Don't allow anything that wouldn't be allowed
without unprivileged mappings.
It was previously overlooked that establishing gid mappings would
allow dropping groups and potentially gaining permission to files and
directories that had lesser permissions for a specific group
setgroups is unique in not needing a valid mapping before it can be called,
in the case of setgroups(0, NULL) which drops all supplemental groups.
The design of the user namespace assumes that CAP_SETGID can not actually
be used until a gid mapping is established. Therefore add a helper
As any gid mapping will allow and must allow for backwards
compatibility dropping groups don't allow any gid mappings to be
established without CAP_SETGID in the parent user namespace.
For a small class of applications this change breaks userspace
and removes useful functionality. This small
setresuid allows the euid to be set to any of uid, euid, suid, and
fsuid. Therefor it is safe to allow an unprivileged user to map their
euid and use CAP_SETUID privileged with exactly that uid, as no new
credentials can be obtained.
I can not find a combination of existing system calls that
On Mon, Dec 8, 2014 at 2:07 PM, Eric W. Biederman ebied...@xmission.com wrote:
setgroups is unique in not needing a valid mapping before it can be called,
in the case of setgroups(0, NULL) which drops all supplemental groups.
The design of the user namespace assumes that CAP_SETGID can not
If you did not create the user namespace and are allowed
to write to uid_map or gid_map you should already have the necessary
privilege in the parent user namespace to establish any mapping
you want so this will not affect userspace in practice.
Limiting unprivileged uid mapping establishment to
On Mon, Dec 8, 2014 at 2:08 PM, Eric W. Biederman ebied...@xmission.com wrote:
setresuid allows the euid to be set to any of uid, euid, suid, and
fsuid. Therefor it is safe to allow an unprivileged user to map their
euid and use CAP_SETUID privileged with exactly that uid, as no new
- Expose the knob to user space through a proc file /proc/pid/setgroups
A value of 0 means the setgroups system call is disabled in the
current processes user namespace and can not be enabled in the
future in this user namespace.
A value of 1 means the segtoups system call is enabled.
On Mon, Dec 8, 2014 at 2:10 PM, Eric W. Biederman ebied...@xmission.com wrote:
If you did not create the user namespace and are allowed
to write to uid_map or gid_map you should already have the necessary
privilege in the parent user namespace to establish any mapping
you want so this will
Now that setgroups can be disabled and not reenabled, setting gid_map
without privielge can now be enabled when setgroups is disabled.
This restores most of the functionality that was lost when unprivilege
setting of gid_map was removed. Applications that use this
functionality will need to
Am 08.12.2014 um 23:07 schrieb Eric W. Biederman:
setgroups is unique in not needing a valid mapping before it can be called,
in the case of setgroups(0, NULL) which drops all supplemental groups.
The design of the user namespace assumes that CAP_SETGID can not actually
be used until a gid
On Mon, Dec 8, 2014 at 2:11 PM, Eric W. Biederman ebied...@xmission.com wrote:
- Expose the knob to user space through a proc file /proc/pid/setgroups
A value of 0 means the setgroups system call is disabled in the
deny
current processes user namespace and can not be enabled in the
On Mon, Dec 8, 2014 at 2:17 PM, Richard Weinberger rich...@nod.at wrote:
Am 08.12.2014 um 23:07 schrieb Eric W. Biederman:
setgroups is unique in not needing a valid mapping before it can be called,
in the case of setgroups(0, NULL) which drops all supplemental groups.
The design of the user
On Mon, Dec 8, 2014 at 2:14 PM, Eric W. Biederman ebied...@xmission.com wrote:
Now that setgroups can be disabled and not reenabled, setting gid_map
without privielge can now be enabled when setgroups is disabled.
This restores most of the functionality that was lost when unprivilege
Am 08.12.2014 um 23:25 schrieb Andy Lutomirski:
On Mon, Dec 8, 2014 at 2:17 PM, Richard Weinberger rich...@nod.at wrote:
Am 08.12.2014 um 23:07 schrieb Eric W. Biederman:
setgroups is unique in not needing a valid mapping before it can be called,
in the case of setgroups(0, NULL) which drops
On Mon, Dec 8, 2014 at 2:26 PM, Eric W. Biederman ebied...@xmission.com wrote:
Andy Lutomirski l...@amacapital.net writes:
On Mon, Dec 8, 2014 at 2:07 PM, Eric W. Biederman ebied...@xmission.com
wrote:
setgroups is unique in not needing a valid mapping before it can be called,
in the case
Andy Lutomirski l...@amacapital.net writes:
On Mon, Dec 8, 2014 at 2:11 PM, Eric W. Biederman ebied...@xmission.com
wrote:
- Expose the knob to user space through a proc file /proc/pid/setgroups
A value of 0 means the setgroups system call is disabled in the
deny
current processes
On Mon, Dec 8, 2014 at 2:39 PM, Eric W. Biederman ebied...@xmission.com wrote:
Richard Weinberger rich...@nod.at writes:
Am 08.12.2014 um 23:25 schrieb Andy Lutomirski:
On Mon, Dec 8, 2014 at 2:17 PM, Richard Weinberger rich...@nod.at wrote:
Am 08.12.2014 um 23:07 schrieb Eric W. Biederman:
On Mon, Dec 8, 2014 at 2:44 PM, Eric W. Biederman ebied...@xmission.com wrote:
Andy Lutomirski l...@amacapital.net writes:
On Mon, Dec 8, 2014 at 2:11 PM, Eric W. Biederman ebied...@xmission.com
wrote:
- Expose the knob to user space through a proc file /proc/pid/setgroups
A value of 0
Andy Lutomirski l...@amacapital.net writes:
On Mon, Dec 8, 2014 at 2:44 PM, Eric W. Biederman ebied...@xmission.com
wrote:
Andy Lutomirski l...@amacapital.net writes:
On Mon, Dec 8, 2014 at 2:11 PM, Eric W. Biederman ebied...@xmission.com
wrote:
- Expose the knob to user space through a
Replace PAGE_KERNEL with PAGE_KERNEL_EXEC to allow copy_to_user_page
invalidate icache for pages mapped with kmap.
Cc: stable@vger.kernel.org
Signed-off-by: Max Filippov jcmvb...@gmail.com
---
arch/xtensa/include/asm/highmem.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Hi, Greg
This commit has been upstreamed since v3.17-rc3.
It is proven to be a conflict with Samsung laptops.
So we've reverted it since v3.18-rc3.
The reversion commit ID is df9ff918.
Best regards
-Lv
From: gre...@linuxfoundation.org [mailto:gre...@linuxfoundation.org]
Sent: Friday, December
From: Anton Blanchard an...@samba.org
Backport of 152d44a853e42952f6c8a504fb1f8eefd21fd5fd.
I used some 64 bit instructions when adding the 32 bit getcpu VDSO
function. Fix it.
Fixes: 18ad51dd342a (powerpc: Add VDSO version of getcpu)
Signed-off-by: Anton Blanchard an...@samba.org
Most users see this message when booting without knowning that it is of
mostly no importance and that TSC calibration may have succeeded by another
way.
As explained thoroufly by Paul Bolle in 2012
(http://lkml.iu.edu//hypermail/linux/kernel/1209.3/00224.html),
Fast TSC calibration failed
On Mon, 2014-12-08 at 16:21 +, Catalin Marinas wrote:
On Fri, Dec 05, 2014 at 10:41:04AM +, Yingjoe Chen wrote:
On Sun, 2014-11-23 at 23:02 -0800, Sonny Rao wrote:
This is a bug fix for using physical arch timers when
the arch_timer_use_virtual boolean is false. It restores the
There is a small race between when the cycle count is read from
the hardware and when the epoch stabilizes. Consider this scenario:
CPU0 CPU1
cyc = read_sched_clock()
cyc_to_sched_clock()
commit 336ae1180df5f69b9e0fb6561bec01c5f64361cf
ARM: sched_clock: Load cycle count after epoch stabilizes
This looks applicable to stable-3.10, which load cycle count after epoch
stabilizes,
The function was moved from arch/arm/kernel/sched_clock.c to
kernel/time/sched_clock.c because of
commit 336ae1180df5f69b9e0fb6561bec01c5f64361cf
ARM: sched_clock: Load cycle count after epoch stabilizes
This looks applicable to stable-3.10, which load cycle count after epoch
stabilizes,
The function was moved from arch/arm/kernel/sched_clock.c to
kernel/time/sched_clock.c because of
From: Stephen Boyd sb...@codeaurora.org
There is a small race between when the cycle count is read from
the hardware and when the epoch stabilizes. Consider this
scenario:
CPU0 CPU1
cyc = read_sched_clock()
cyc_to_sched_clock()
54 matches
Mail list logo
