From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
bond_alb_handle_active_change() is legitimate: It is assigning a pointer
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
ip6gre_tunnel_unlink() is legitimate: It is assigning a pointer to an
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
ip6_tnl_unlink() is legitimate: It is assigning a pointer to an element
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
notifier_chain_unregister() is legitimate: It is deleting an element
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
ipip6_tunnel_unlink() is legitimate: It is assigning a pointer to an
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
sta_info_hash_del() are legitimate: They are assigning a pointer to an
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
__br_mdb_del() is legitimate: They are assigning a pointer to an element
From: Josh Triplett
rcu_assign_pointer needs to use ACCESS_ONCE to make the assignment to
the destination pointer volatile, to protect against compilers too
clever for their own good.
In addition, since rcu_assign_pointer force-casts the source pointer to
add the __rcu address space (overriding
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the uses in
cfg80211_combine_bsses() and cfg80211_bss_update() are legitimate:
They
On Fri, 11 Oct 2013 15:43:40 -0500
Scott Wood wrote:
> On Fri, 2013-10-11 at 01:27 -0500, Kim Phillips wrote:
> > Force the vfio-pci driver to only be bound explicitly via sysfs to avoid
> > conflics with other drivers in the event of a hotplug.
> >
> > Signed-off-by: Kim Phillips
> > ---
> >
From: "Paul E. McKenney"
The sparse checking for rcu_assign_pointer() was recently upgraded
to reject non-__kernel address spaces. This also rejects __rcu,
which is almost always the right thing to do. However, the use in
dn_insert_route() is legitimate: It is assigning a pointer to an element
> -Original Message-
> From: David Rientjes [mailto:rient...@google.com]
> Sent: Friday, October 11, 2013 4:08 PM
> To: Ingo Molnar; H. Peter Anvin; t...@linutronix.de; H. Peter Anvin
> Cc: KY Srinivasan; Olaf Hering; linux-kernel@vger.kernel.org; linux-tip-
> comm...@vger.kernel.org
>
Hello!
This series features updates to allow sparse to do a better job of
statically analyzing RCU usage:
1. Add a comment indicating that despite appearances,
rcu_assign_pointer() really only evaluates its arguments once,
as a cpp macro should.
2-13. Apply ACCESS_ONCE()
On Tue, Sep 10, 2013 at 3:04 PM, Bjorn Helgaas wrote:
> [+cc Thomas, e1000e driver folks, linux-pci, lkml]
>
> On Mon, Jul 15, 2013 at 2:31 AM, wrote:
>> https://bugzilla.kernel.org/show_bug.cgi?id=60555
>>
>> Bug ID: 60555
>>Summary: Some amount of ifconfig cause load
9e7827b5ea4c ("x86, hyperv: Get the local APIC timer frequency from the
hypervisor") breaks the build with some configs because apic.h isn't
directly included:
arch/x86/kernel/cpu/mshyperv.c: In function 'ms_hyperv_init_platform':
arch/x86/kernel/cpu/mshyperv.c:90:3: error:
Not entirely sure about the assembly part, but shouldn't it...
Test for the nul character rather than the '0' (== 0x30), in the
__get_user_unknown() case.
Signed-off-by: Roel Kluin
---
diff --git a/kernel/lockdep_proc.c b/kernel/lockdep_proc.c
index b2c71c5..71b3aba 100644
---
Jeff Layton wrote:
> > - if (kflags & (1 << KEY_FLAG_NEGATIVE))
> > + if (kflags & (1 << KEY_FLAG_NEGATIVE)) {
>
> Not specifically related to this bug, but why are you open-coding
> test_bit() here and elsewhere?
Because kflags is read once and kept in a variable. Might
On Friday, October 11, 2013 09:54:07 AM tianyu@intel.com wrote:
> From: Lan Tianyu
>
> AC's proc directory is not used and so remove it. Prepare for removing
> /proc/acpi directory.
>
> Signed-off-by: Lan Tianyu
Can you please rebase this patch on top of current linux-pm.git/linux-next
On 10/11/2013 04:08 PM, Roel Kluin wrote:
Untested, but this looks like a bug to me
Careless error on my part. Fix looks good; thanks for catching this.
Regards,
Peter Hurley
---
test echo_buf() result for ECHO_OP_START
Signed-off-by: Roel Kluin
---
diff --git
Ryan Mallon writes:
> The only remaining problem is kernel/module.c:module_sect_show() which
> is used to write the sysfs files in /sys/module//sections/.
> Those files are actually are really good target for leaking %pK values
> via setuid binaries. The problem is that the module_sect_show()
Greg Kroah-Hartman wrote:
> 3.4-stable review patch. If anyone has any objections, please let me know.
3.4-stable doesn't need this patch because commit 264b83c07a84
("usermodehelper: check subprocess_info->path != NULL") already fixed it.
--
To unsubscribe from this list: send the line
Greg Kroah-Hartman wrote:
> 3.10-stable review patch. If anyone has any objections, please let me know.
3.10-stable doesn't need this patch because commit 264b83c07a84
("usermodehelper: check subprocess_info->path != NULL") already fixed it.
--
To unsubscribe from this list: send the line
Greg Kroah-Hartman wrote:
> 3.0-stable review patch. If anyone has any objections, please let me know.
3.0-stable doesn't need this patch because commit 264b83c07a84
("usermodehelper: check subprocess_info->path != NULL") already fixed it.
--
To unsubscribe from this list: send the line
> +#else
> +static struct device_node *of_find_gpio(struct device *dev, const char *id
> + unsigned int idx, unsigned long flags)
> +{
> + return ERR_PTR(-ENODEV);
> +}
> +#endif
... and of course I forgot to fix the main compilation error. Linus,
would
On Sat, Oct 12, 2013 at 12:04:50AM +0200, Roel Kluin wrote:
> Adding Andrew to CC, thanks for comments & picking up my patches, BTW.
Given that Jiri and I are the tty/serial maintainers, we should be able
to handle this, give us a few days to catch up with patches sent before
yours...
thanks,
Daniel Kiper writes:
> On Fri, Oct 11, 2013 at 03:08:43AM -0700, ebied...@xmission.com wrote:
>> Daniel Kiper writes:
>>
>> > Hi,
>> >
>> > Could you explain why do you clear all registers just before jumping
>> > into purgatory (please look into arch/x86/kernel/relocate_kernel_64.S
>> > for
On Fri, Oct 11, 2013 at 12:36:07PM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.4.66 release.
> There are 48 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
On Fri, Oct 11, 2013 at 12:34:44PM -0700, Greg Kroah-Hartman wrote:
>
> NOTE: This is going to be the next-to-last 3.0.x release that I do.
> You should be moving off to the 3.4.x or 3.10.x longterm kernels
> by now, and not use the 3.0.x kernel unless
Hi Jan,
I'm testing out some changes to the xHCI USB host controller driver
(which uses a radix tree when a UAS device is attached to the host), and
I noticed the following warning:
Oct 11 14:42:08 xanatos kernel: [18165.819014] usb 2-2: new SuperSpeed USB
device number 2 using xhci_hcd
Oct 11
On Fri, Oct 11, 2013 at 02:56:19PM -0700, Guenter Roeck wrote:
> On Fri, Oct 11, 2013 at 12:36:07PM -0700, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.4.66 release.
> > There are 48 patches in this series, all will be posted as a response
> > to this one.
On Fri, Oct 11, 2013 at 05:16:42PM -0400, Mike Snitzer wrote:
> On Fri, Oct 11 2013 at 12:13am -0400,
> Kent Overstreet wrote:
>
> > On Sun, Oct 06, 2013 at 08:14:10PM -0400, Mike Snitzer wrote:
> > >
> > > Please fold this fix into your for-jens branch, thanks. (Could be that
> > > by the
On Fri, Oct 11, 2013 at 02:49:10PM -0700, Guenter Roeck wrote:
> On Fri, Oct 11, 2013 at 12:37:40PM -0700, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 3.10.16 release.
> > There are 110 patches in this series, all will be posted as a response
> > to this one.
Hi Wim,
On Sat, Oct 05, 2013 at 04:20:17PM +0200, Maxime Ripard wrote:
> This driver has a section mismatch, for probe and remove functions,
> leading to the following warning during the compilation.
>
> WARNING: drivers/watchdog/built-in.o(.data+0x24): Section mismatch in
> reference from the
Hi Stephen,
On Thu, Oct 10, 2013 at 03:46:11PM -0700, Stephen Boyd wrote:
> On 10/10/13 12:13, Maxime Ripard wrote:
> > On Wed, Sep 25, 2013 at 04:16:14PM -0700, Stephen Boyd wrote:
> >> On 09/25/13 07:03, Maxime Ripard wrote:
> >>> + sun5i_clockevent.cpumask = cpumask_of(0);
> >> Can this timer
On 10/11/2013 05:24 AM, Ralf Baechle wrote:
On Fri, Oct 11, 2013 at 06:21:28AM +0530, Srikar Dronamraju wrote:
Will be nice to have another arch(mips) support for uprobes.
It's basically ready to be merged - but it's triggering issues elsewhere
in the kernel which I have to resolve first.
On Fri, 2013-10-11 at 13:57 -0700, gre...@linuxfoundation.org wrote:
> On Fri, Oct 11, 2013 at 03:48:21AM +, Fangxiaozhi (Franko) wrote:
> > 1. Add new supporting declarations to option.c, to support Huawei new
> > devices with new bInterfaceSubClass value.
> > Signed-off-by: fangxiaozhi
>
On 10/11/13 3:51 PM, Andi Kleen wrote:
David Ahern writes:
On 10/11/13 9:11 AM, David Ahern wrote:
It would be nice to fix the callchain arg handler to not attempt to
process the next argument if it is not fp or dwarf.
Specifically, something like this which maintains syntax and default
fp
On 11/10/13 15:42, George Spelvin wrote:
> ebied...@xmission.com (Eric W. Biederman) wrote:
>> Sigh. This is all wrong. The only correct thing to test is
>> file->f_cred. Aka the capabilities of the program that opened the
>> file.
>>
>> Which means that the interface to %pK in the case of
On Fri, Oct 11, 2013 at 12:36:07PM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.4.66 release.
> There are 48 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
From: Hannes Frederic Sowa
Date: Fri, 11 Oct 2013 17:02:17 +0200
> On Thu, Oct 10, 2013 at 06:50:27PM +0100, Oussama Ghorbel wrote:
>> The ip6_tnl.hlen (gre and ipv6 headers length) is independent from the
>> outgoing interface, so it would be better to initialize it even when no
>> route is
Hi Stephen,
Stephen Boyd writes:
> The sched_clock.h include is under include/linux now.
>
> Cc: Alexander Shiyan
> Signed-off-by: Stephen Boyd
I applied both of these to next/cleanup.
Thanks,
Kevin
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
David Ahern writes:
> On 10/11/13 9:11 AM, David Ahern wrote:
>> It would be nice to fix the callchain arg handler to not attempt to
>> process the next argument if it is not fp or dwarf.
>
> Specifically, something like this which maintains syntax and default
> fp option:
Yes please! This
On Fri, Oct 11, 2013 at 12:37:40PM -0700, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 3.10.16 release.
> There are 110 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
Use a firmware operation to set the CPU reset handler and only resort to
doing it ourselves if there is none defined.
This supports the booting of secondary CPUs on devices using a TrustZone
secure monitor.
Signed-off-by: Alexandre Courbot
Reviewed-by: Tomasz Figa
Reviewed-by: Stephen Warren
Not all Tegra devices can set the CPU reset handler in the same way.
In particular, devices using a TrustZone secure monitor cannot set the
reset handler directly and need to do it through a firmware operation.
This patch separates the act of setting the reset handler from its
preparation, so the
On Friday, October 11, 2013 10:21:35 AM Linus Torvalds wrote:
> On Fri, Oct 11, 2013 at 4:13 AM, Rafael J. Wysocki wrote:
> > +/**
> > + * slot_should_be_exposed - Check whether or not to expose a slot to
> > userland.
> > + * @bridge: ACPIPHP bridge the slot belongs to.
> > + * @handle: ACPI
Support for Trusted Foundations is light and allows the kernel to run on
a wider range of devices, so enable it by default.
Signed-off-by: Alexandre Courbot
Reviewed-by: Tomasz Figa
Reviewed-by: Stephen Warren
---
arch/arm/configs/tegra_defconfig | 1 +
1 file changed, 1 insertion(+)
diff
Hopefully this has received enough review to be merged (although a few more
acks/review especially from DT people on patch 1 would be nice). Thanks
everyone for all the input and comments!
Trusted Foundations is an ARM secure monitor that is used by many Tegra-based
retail devices (like SHIELD
Trusted Foundations is a TrustZone-based secure monitor for ARM that
can be invoked using the same SMC-based API on all supported
platforms. This patch adds initial basic support for Trusted
Foundations using the ARM firmware API. Current features are limited
to the ability to boot secondary
OK, I'll prepare a new patch with explicit ID checks (BEA01, BOOT2,
CDROM, CD001, CDW02, NSR02, NSR03, TEA01, that's all I think) and the
needed changelog in a few days. Do you think that a hard upper limit
on the sector offset is desirable? The ISO9660 driver looks for the
first 100 sectors, but
Register the firmware operations for Trusted Foundations if the device
tree indicates it is active on the device.
Signed-off-by: Alexandre Courbot
Reviewed-by: Tomasz Figa
Reviewed-by: Stephen Warren
---
Documentation/devicetree/bindings/arm/tegra.txt | 5 +
arch/arm/mach-tegra/Kconfig
On Fri, Oct 11, 2013 at 08:25:17AM -0400, Jeff Layton wrote:
> At LSF this year, there was a discussion about the "wishlist" for
> userland file servers. One of the things brought up was the goofy and
> problematic behavior of POSIX locks when a file is closed. Boaz started
> a thread on it here:
On Fri, Oct 11, 2013 at 12:40:21PM +0800, Wei Yongjun wrote:
> From: Wei Yongjun
>
> Use free_bch() instead of kfree() to free init_bch()
> allocated data.
>
> Signed-off-by: Wei Yongjun
Pushed to l2-mtd.git. Thanks!
Brian
--
To unsubscribe from this list: send the line "unsubscribe
On Fri, Oct 11 2013 at 12:13am -0400,
Kent Overstreet wrote:
> On Sun, Oct 06, 2013 at 08:14:10PM -0400, Mike Snitzer wrote:
> >
> > Please fold this fix into your for-jens branch, thanks. (Could be that
> > by the time Jens takes your immutable biovec changes we'll need to
> > rebase but at
From: Darbha Sriharsha
Adds support for the bq24735 charger chipset. The bq24735 is a
high-efficiency, synchronous battery charger.
It allows control of the charging current, input current, and the charger
voltage DAC's through SMBus.
Signed-off-by: Darbha Sriharsha
Signed-off-by: Rhyland
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Jones
[ Upstream commit 0c1db731bfcf3a9fd6c58132134f8b0f423552f0 ]
The indentation here implies this was meant to be a multi-line if.
Introduced several years back in commit
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 627aad1c01da6f881e7f98d71fd928ca0c316b1a upstream.
The pciinfo struct has a two byte hole after ->dev_fn so stack
information could be leaked to the user.
This was
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 58f09e00ae095e46ef9edfcf3a5fd9ccdfad065e upstream.
The arg64 struct has a hole after ->buf_size which isn't cleared. Or if
any of the calls to copy_from_user() fail then
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nikolay Aleksandrov
[ Upstream commit d0fe8c888b1fd1a2f84b9962cabcb98a70988aec ]
I've been hitting a NULL ptr deref while using netconsole because the
np->dev check and the pointer
NOTE: This is going to be the next-to-last 3.0.x release that I do.
You should be moving off to the 3.4.x or 3.10.x longterm kernels
by now, and not use the 3.0.x kernel unless you have to for some
reason. If anyone has any problems with this,
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Alex Williamson
commit 3269ee0bd6686baf86630300d528500ac5b516d7 upstream.
At best the current code only seems to free the leaf pagetables and
the root. If you're unlucky enough to have a
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Borkmann
[ Upstream commit 95ee62083cb6453e056562d91f597552021e6ae7 ]
Alan Chester reported an issue with IPv6 on SCTP that IPsec traffic is not
being encrypted, whereas on IPv4 it is.
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Frederic Sowa
[ Upstream commit 2811ebac2521ceac84f2bdae402455baa6a7fb47 ]
In the following scenario the socket is corked:
If the first UDP packet is larger then the mtu we try to
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ricardo Ribalda
[ Upstream commit 7167cf0e8cd10287b7912b9ffcccd9616f382922 ]
The dma descriptors indexes are only initialized on the probe function.
If a packet is on the buffer when
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Peter Korsgaard
[ Upstream commit bf0ea6380724beb64f27a722dfc4b0edabff816e ]
Pass-all-multicast is controlled by bit 3 in RX control, not bit 2
(pass undersized frames).
Reported-by: Joseph
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit f8d7b13e14357ed19d2ca2799539600418dc3939 upstream.
The ->put() function are called from snd_ctl_elem_write() with user
supplied data. The limit checks here could
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
[ Upstream commit be4f154d5ef0ca147ab6bcd38857a774133f5450 ]
At some point limits were added to forward_delay. However, the
limits are only enforced when STP is enabled. This
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ansis Atteka
[ Upstream commit 703133de331a7a7df47f31fb9de51dc6f68a9de8 ]
If local fragmentation is allowed, then ip_select_ident() and
ip_select_ident_more() need to generate unique IDs to
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Neil Horman
[ Upstream commit 5a0068deb611109c5ba77358be533f763f395ee4 ]
Recently grabbed this report:
https://bugzilla.redhat.com/show_bug.cgi?id=1005567
Of an issue in which the bonding
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kirill Tkhai
[ Upstream commit 61d9b9355b0d427bd1e732bd54628ff9103e496f ]
The functions
__down_read
__down_read_trylock
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Roger Luethi
[ Upstream commit 207070f5221e2a901d56a49df9cde47d9b716cd7 ]
Outgoing packets sent by via-rhine have their VLAN PCP field off by one
(when hardware acceleration is enabled). The
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Prarit Bhargava
commit e82b89a6f19bae73fb064d1b3dd91fcefbb478f4 upstream.
modalias_show() should return an empty string on error, not -ENODEV.
This causes the following false and annoying
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit d967967e8d1116fb38bad25e58714b503cca upstream.
This is called from snd_ctl_elem_write() with user supplied data so we
need to add some bounds checking.
Signed-off-by:
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Nishanth Aravamudan
commit 1cf389df090194a0976dc867b7fffe99d9d490cb upstream.
Under heavy (DLPAR?) stress, we tripped this panic() in
arch/powerpc/kernel/iommu.c::iommu_init_table():
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Salam Noureddine
[ Upstream commit e2401654dd0f5f3fb7a8d80dad9554d73d7ca394 ]
It is possible for the timer handlers to run after the call to
ip_mc_down so use in_dev_put instead of
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kirill Tkhai
[ Upstream commit 1c2696cdaad84580545a2e9c0879ff597880b1a9 ]
1)Use kvmap_itlb_longpath instead of kvmap_dtlb_longpath.
2)Handle page #0 only, don't handle page #1: bleu -> blu
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Salam Noureddine
[ Upstream commit 9260d3e1013701aa814d10c8fc6a9f92bd17d643 ]
It is possible for the timer handlers to run after the call to
ipv6_mc_down so use in6_dev_put instead of
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "Paul E. McKenney"
commit d9813c3681a36774b254c0cdc9cce53c9e22c756 upstream.
The csum_partial_copy_generic() uses register r7 to adjust the remaining
bytes to process. Unfortunately, r7 also
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Christian Lamparter
commit 1e43692cdb7cc445d6347d8a5207d9cef0c71434 upstream.
Added USB ID for Corega WLUSB2GTST USB adapter.
Reported-by: Joerg Kalisch
Signed-off-by: Christian Lamparter
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Michal Malý
commit eb2addd4044b4b2ce77693bde5bc810536dd96ee upstream.
Hi,
my Huawei 3G modem has an embedded Smart Card reader which causes
trouble when the modem is being detected (a bunch
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Tetsuo Handa
commit 4c1c7be95c345cf2ad537a0c48e9aeadc7304527 upstream.
If /proc/sys/kernel/core_pattern contains only "|", a NULL pointer
dereference happens upon core dump because
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: "David S. Miller"
[ Upstream commit 63d499662aeec1864ec36d042aca8184ea6a938e ]
Reported-by: Kirill Tkhai
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
---
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Ian Abbott
commit 677a31565692d596ef42ea589b53ba289abf4713 upstream.
The `insn_bits` handler `ni_65xx_dio_insn_bits()` has a `for` loop that
currently writes (optionally) and reads back up to
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kirill Tkhai
[ Upstream commit ab2abda6377723e0d5fbbfe5f5aa16a5523344d1 ]
(From v1 to v2: changed comment)
On the way linux_sparc_syscall32->linux_syscall_trace32->goto 2f,
register %o5
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Kirill Tkhai
[ Upstream commit 7a3b0f89e3fea680f93932691ca41a68eee7ab5e ]
Pass 1 in %o1 to indicate that syscall_trace accounts exit.
Signed-off-by: Kirill Tkhai
CC: David Miller
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Josef Bacik
commit b6c60c8018c4e9beb2f83fc82c09f9d033766571 upstream.
Previously we only added blocks to the list to have their backrefs checked if
the level of the block is right above the
Dear RT folks!
I'm pleased to announce the v3.10.15-rt11 patch set.
Changes since v3.10.15-rt10
- two genirq patches: one was already in v3.8-rt ("genirq: Set irq
thread to RT priority on creation"). The second ("genirq: Set the irq
thread policy without checking CAP_SYS_NICE") ensures that
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 627aad1c01da6f881e7f98d71fd928ca0c316b1a upstream.
The pciinfo struct has a two byte hole after ->dev_fn so stack
information could be leaked to the user.
This was
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Lv Zheng
commit 06a8566bcf5cf7db9843a82cde7a33c7bf3947d9 upstream.
This patch fixes the issues indicated by the test results that
ipmi_msg_handler() is invoked in atomic context.
BUG:
This is the start of the stable review cycle for the 3.4.66 release.
There are 48 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 Sun Oct 13 19:35:35 UTC 2013.
Anything
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dan Carpenter
commit 58f09e00ae095e46ef9edfcf3a5fd9ccdfad065e upstream.
The arg64 struct has a hole after ->buf_size which isn't cleared. Or if
any of the calls to copy_from_user() fail then
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Nikolay Aleksandrov
[ Upstream commit d0fe8c888b1fd1a2f84b9962cabcb98a70988aec ]
I've been hitting a NULL ptr deref while using netconsole because the
np->dev check and the pointer
3.0-stable review patch. If anyone has any objections, please let me know.
--
From: Chris Metcalf
commit f862eefec0b68e099a9fa58d3761ffb10bad97e1 upstream.
It turns out the kernel relies on barrier() to force a reload of the
percpu offset value. Since we can't easily modify
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit b86783587b3d1d552326d955acee37eac48800f1 ]
In commit 8ed781668dd49 ("flow_keys: include thoff into flow_keys for
later usage"), we missed that existing code was
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Borkmann
[ Upstream commit 95ee62083cb6453e056562d91f597552021e6ae7 ]
Alan Chester reported an issue with IPv6 on SCTP that IPsec traffic is not
being encrypted, whereas on IPv4 it is.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Claudiu Manoil
commit b98b8babd6e3370fadb7c6eaacb00eb2f6344a6c upstream.
This is primarily to address transmission timeout occurrences, when
multiple H/W Tx queues are being used concurrently.
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Dave Jones
[ Upstream commit 0c1db731bfcf3a9fd6c58132134f8b0f423552f0 ]
The indentation here implies this was meant to be a multi-line if.
Introduced several years back in commit
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Borkmann
[ Upstream commit 88362ad8f9a6cea787420b57cc27ccacef000dbe ]
This was originally reported in [1] and posted by Neil Horman [2], he said:
Fix up a missed null pointer check
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Frederic Sowa
[ Upstream commit 2811ebac2521ceac84f2bdae402455baa6a7fb47 ]
In the following scenario the socket is corked:
If the first UDP packet is larger then the mtu we try to
3.4-stable review patch. If anyone has any objections, please let me know.
--
From: Roger Luethi
[ Upstream commit 207070f5221e2a901d56a49df9cde47d9b716cd7 ]
Outgoing packets sent by via-rhine have their VLAN PCP field off by one
(when hardware acceleration is enabled). The
101 - 200 of 2146 matches
Mail list logo
