Avoid redundant load of %r11 (it is already loaded a few instructions before).
Do not needlessly increment %rsp - we are going to return to userspace
via SYSRET, this insn doesn't use stack for return.
Signed-off-by: Denys Vlasenko
CC: Linus Torvalds
CC: Steven Rostedt
CC: Ingo Molnar
CC: Bori
CLONE_SETTLS is expected to write a TLS entry in the GDT for 32-bit
callers and to set fsbase for 64-bit callers.
The correct check is is_ia32_task(), which returns true in the
context of a 32-bit syscall. TIF_IA32 is set if the task itself has
a 32-bit personality, which is not the same thing.
The ability for modified cs and/or ss to be useful has nothing to do
with TIF_IA32. Similarly, if there's an exploit involving changing
cs or ss, it's exploitable with or without a TIF_IA32 check.
So just delete the check.
Signed-off-by: Andy Lutomirski
---
arch/x86/kernel/ptrace.c | 10 ++
At some point I'd like to remove TIF_IA32 entirely and replace it with
just user_64bit_mode and a per-mm configuration. In the mean time,
this fixes some incorrect uses.
Ingo, Thomas, Peter, if you like these, please ack the first one and apply
the other two. The first one will conflict with the
PER_CPU(old_rsp) usage is simplified - now it is used only
as temp storage, and userspace stack pointer is immediately stored
in pt_regs->sp on syscall entry, instead of being used later,
on syscall exit. This allows to get rid of thread_struct::usersp.
The lazy store of pt_regs->cs and pt_regs->s
ret_from_fork checks TIF_IA32 to determine whether pt_regs and the
related state make sense for ret_from_sys_call. This is entirely
the wrong check. TS_COMPAT would make a little more sense, but
there's really no point in keeping this optimization at all.
This fixes a return to the wrong user CS
Before this patch, r11 was saved in pt_regs->r11.
Which looks natural, but requires messy shuffling to/from iret frame
whenever ptrace or e.g. iopl wants to modify flags- because
that's how this register are used by SYSCALL/SYSRET.
This patch saves r11 in pt_regs->flags,
and uses that value for SY
PER_CPU_VAR(kernel_stack) was set up in a way where it points
five stack slots below the top of stack.
Presumably, it was done to avoid one "sub $5*8,%rsp"
in syscall/sysenter code paths, where iret frame needs to be
created by hand.
Ironically, none of them benefit from this optimization,
since
On Tue, Feb 24, 2015 at 4:00 PM, Denys Vlasenko wrote:
> The last instance of "mysterious" SS+8 constant is replaced by SIZEOF_PTREGS.
Applied and checked by reading the macro definition :)
>
> Signed-off-by: Denys Vlasenko
> CC: Linus Torvalds
> CC: Steven Rostedt
> CC: Ingo Molnar
> CC: Bo
On Tue, Feb 24, 2015 at 4:00 PM, Denys Vlasenko wrote:
> Avoid redundant load of %r11 (it is already loaded a few instructions before).
> Do not needlessly increment %rsp - we are going to return to userspace
> via SYSRET, this insn doesn't use stack for return.
>
> Signed-off-by: Denys Vlasenko
Hi,
So, this is a attempt to get a common base with the out of the tree driver
for Huion and UC-Logic tablets here
https://github.com/DIGImend/digimend-kernel-drivers
I am CC-ing DIGImend-devel though the patches are aimed at Jiri's tree upstream.
Nick, I changed a little bit the first patch co
Based on a patch from: Nikolai Kondrashov
Most of the tablets handled by hid-uclogic already uses MULTI_INPUT.
Fot the ones which are not quirked in usbhid/hidquirks, they have a
custom report descriptor which contains only one report per HID
interface. For those tablets HID_QUIRK_MULTI_INPUT is
We append "Pen", "Pad", "Mouse" or "Keyboard" suffix to the appropriate
input node to match what the Wacom driver does and be more convenient for
the user to know which one is which.
Signed-off-by: Benjamin Tissoires
---
drivers/hid/hid-uclogic.c | 40
1
From: Nikolai Kondrashov
Merge the hid-huion driver into hid-uclogic as all the devices supported
by hid-huion are in fact UC-Logic devices.
Signed-off-by: Benjamin Tissoires
---
Changed from the original patch:
- update Makefile, Kconfig accordingly
- remove one extra pr_err when kzalloc fail
The Huion tablets show 3 interfaces. Only the first and the third
are currently used.
Also remove HID_QUIRK_MULTI_INPUT for the third interface to not
create more than needed input nodes.
Signed-off-by: Benjamin Tissoires
---
drivers/hid/hid-uclogic.c | 5 +
1 file changed, 5 insertions(+)
On Tue, Feb 24, 2015 at 11:15 AM, Denys Vlasenko
wrote:
> On Fri, Feb 20, 2015 at 7:58 PM, Andy Lutomirski wrote:
>> We have eager and lazy fpu modes, introduced in:
>>
>> 304bceda6a18 x86, fpu: use non-lazy fpu restore for processors supporting
>> xsave
>>
>> The result is rather messy. There
Hi Michal,
On Tue, Feb 24, 2015 at 04:43:18PM +0100, Michal Hocko wrote:
> On Tue 24-02-15 17:18:14, Minchan Kim wrote:
> > Recently, Shaohua reported that MADV_FREE is much slower than
> > MADV_DONTNEED in his MADV_FREE bomb test. The reason is many of
> > applications went to stall with direct r
This patchset adds support of Write-Through (WT) mapping on x86.
The study below shows that using WT mapping may be useful for
non-volatile memory.
http://www.hpl.hp.com/techreports/2012/HPL-2012-236.pdf
All new/modified interfaces have been tested.
v8:
- Rebased to 4.0-rc1 and resolved conflict
This patch adds set_memory_wt(), set_memory_array_wt() and
set_pages_array_wt() for setting specified range(s) of the
regular memory to WT.
Signed-off-by: Toshi Kani
---
Documentation/x86/pat.txt |9 --
arch/x86/include/asm/cacheflush.h |6 +++-
arch/x86/mm/pageattr.c
Now that gigantic pages are dynamically allocatable, care must be taken
to ensure that p->first_page is valid before setting PageTail.
If this isn't done, then it is possible to race and have compound_head()
return NULL.
Signed-off-by: David Rientjes
---
mm/hugetlb.c | 4 +++-
1 file changed, 3
As set_memory_wb() calls set_page_memtype() with -1, _PGMT_DEFAULT is
solely used for tracking the WB type. _PGMT_WB is defined but unused.
Hence, this patch renames _PGMT_DEFAULT to _PGMT_WB to clarify its
usage, and releases the slot used by _PGMT_WB before. As a result,
set_memory_wb() is chan
This patch adds ioremap_wt() for creating WT mapping on x86.
It follows the same model as ioremap_wc() for multi-architecture
support. ARCH_HAS_IOREMAP_WT is defined in the x86 version of
io.h to indicate that ioremap_wt() is implemented on x86.
Also update the PAT documentation file to cover ior
This patch adds pgprot_writethrough() for setting WT to a given
pgprot_t.
Signed-off-by: Toshi Kani
Reviewed-by: Konrad Rzeszutek Wilk
---
arch/x86/include/asm/pgtable_types.h |3 +++
arch/x86/mm/pat.c| 10 ++
include/asm-generic/pgtable.h|4
3
This patch changes reserve_memtype() to handle the WT cache mode
with PAT. When PAT is not enabled, WB and UC- are the only types
supported.
When a target range is in RAM, reserve_ram_pages_type() verifies
the requested type. In this case, WT and WP requests fail with
-EINVAL and UC gets redirec
This patch refactors the !pat_enabled handling code and integrates
it into the PAT abstraction code. The PAT table is emulated by
corresponding to the two cache attribute bits, PWT (Write Through)
and PCD (Cache Disable). The emulated PAT table is the same as the
BIOS default setup when the system
This patch sets WT to the PA7 slot in the PAT MSR when the processor
is not affected by the PAT errata. The PA7 slot is chosen to improve
robustness in the presence of errata that might cause the high PAT bit
to be ignored. This way a buggy PA7 slot access will hit the PA3 slot,
which is UC, so a
On Thu, 2015-01-22 at 14:50 -0700, Toshi Kani wrote:
> On Thu, 2015-01-22 at 22:25 +0100, Thomas Gleixner wrote:
> > On Thu, 15 Jan 2015, Toshi Kani wrote:
> >
> > > Hi Ingo, Peter, Thomas,
> > >
> > > Is there anything else I need to do for accepting this patchset?
> >
> > You might hand me so
Hi,
On Tue, Jan 13, 2015 at 9:51 AM, Doug Anderson wrote:
> We've seen at least one card that can get confused during all the
> errors generated during tuning on rk3288. These errors seem to go
> away with DW_MCI_QUIRK_RETRY_DELAY. That quirk is documented to be
> for 2.11a and on rk3288 I beli
AP148 default console output is uart4, so this change adds a serial0
alias to it, as well add the corresponding stdout-path.
This will avoid having to set these as chosen.
Signed-off-by: Mathieu Olivari
---
arch/arm/boot/dts/qcom-ipq8064-ap148.dts | 8
1 file changed, 8 insertions(+)
All IPQ806x based boards will include this file and will need a way to
identify each GSBI device. So this change is labelling them all to make
reference from board specific file easier.
Signed-off-by: Mathieu Olivari
---
arch/arm/boot/dts/qcom-ipq8064.dtsi | 14 +++---
1 file changed, 7
On Tue, Feb 24, 2015 at 05:14:08PM +0100, Michal Hocko wrote:
> On Tue 24-02-15 17:18:16, Minchan Kim wrote:
> > MADV_FREE is hint that it's okay to discard pages if memory is
> > pressure and we uses reclaimers(ie, kswapd and direct reclaim)
>
> s@if memory is pressure@if there is memory pressure
Avoid redundant load of %r11 (it is already loaded a few instructions before).
Do not needlessly increment %rsp - we are going to return to userspace
via SYSRET, this insn doesn't use stack for return.
Changes since v1: added a comment
Signed-off-by: Denys Vlasenko
CC: Linus Torvalds
CC: Steven
On Tue, Feb 24, 2015 at 1:55 PM, Matt Fleming wrote:
> On Sun, 22 Feb, at 07:43:48PM, Yinghai Lu wrote:
>> +Field name: ext_code32_start
>> +Type:modify (optional, reloc)
>> +Offset/size: 0x268/4
>> +Protocol:2.14+
>> +
>> + This field is the upper 32bits of load address when
On Mon, Feb 23, 2015 at 09:09:32PM -0500, Steven Rostedt wrote:
> Another email inbox clean up: BLAST FROM THE PAST
>
> On Fri, 7 Feb 2014 12:22:33 +0800
> Wang Nan wrote:
>
> > If BUILD_SRC or CURDIR contains tailing '/', the file names passed to gcc
> > will
> > contain '//'. It will be conta
On Wed, Feb 25, 2015 at 1:04 AM, Andy Lutomirski wrote:
>> --- a/arch/x86/kernel/entry_64.S
>> +++ b/arch/x86/kernel/entry_64.S
>> @@ -756,9 +756,8 @@ retint_swapgs: /* return to user-space */
>> */
>> irq_return_via_sysret:
>> CFI_REMEMBER_STATE
>> - RESTORE_C
From: Al Stone
In preparation for later splitting out some of the arch-dependent code from
osl.c, clear up all the warnings reported by checkpatch.pl where pr_* should
be used instead of printk(KERN_* ...).
Signed-off-by: Al Stone
---
drivers/acpi/osl.c | 46 +++
From: Al Stone
Whether arch-specific functions are used or not now depends on the config
option CONFIG_ARCH_SPECIFIC_ACPI_OSI. By default, this is set false which
causes the x86/ia64 versions to be used, just as is done today. Setting
this option true causes architecture-specific implementation
From: Al Stone
Having moved the _OSI callback function needed by ACPICA from
drivers/acpi/osl.c to drivers/acpi/osi.c, we now move all the
remaining _OSI support functions to osi.c.
This patch is much larger than I had wanted it to be; several of the
functions that implemented acpi_osi* command
From: Al Stone
ACPI_OS_NAME is globally defined as "Microsoft Windows NT" for now.
That doesn't make much sense in the ARM context, so set it to "Linux"
when CONFIG_ARM64.
If it is necessary to change the return value from \_OS_ (that is, return
some value other than the default in ACPI_OS_NAME)
From: Al Stone
Now that all of the _OSI functionality has been separated out, we can
provide arch-specific functionality for it. This also allows us to do
the same for the acpi_blacklisted() function. We also make sure the
defaults for the arm64 kernel are set so that the arch-specific _OSI
met
From: Al Stone
In preparation for later splitting out some of the arch-dependent code from
osl.c, clean up some warnings from checkpatch that fall into more semantic
issues; none of these should change functionality, but they do touch lines
of code with semantic significance:
-- replaced #inc
From: Al Stone
In preparation for later splitting out some of the arch-dependent code from
osl.c, clean up a bunch of warnings for odd bits of syntax:
-- remove CVS keyword markers
-- remove a space from between a function name and an opening parenthesis
-- clean up all but one line > 8
From: Al Stone
In order to deprecate the use of _OSI for arm64 or other new architectures,
we need to make the default handler something we can change for various
platforms. This patch moves the definition of acpi_osi_handler() -- the
function used by ACPICA as a callback for evaluating _OSI --
From: Al Stone
In preparation for later splitting out some of the arch-dependent code from
osl.c, clean up the errors reported by checkpatch.pl. They fell into these
classes:
-- remove the FSF address from the GPL notice
-- "foo * bar" should be "foo *bar" (and the ** variation of same)
From: Al Stone
The use of the ACPI _OSI method in Linux has a long and sordid history.
Instead of perpetuating past complications on new architectures, the
consensus amongst those writing the ACPI specification and those using
it seems to be to ultimately deprecate the use of _OSI. A change req
On Tue, Feb 24, 2015 at 4:30 PM, Denys Vlasenko wrote:
> Avoid redundant load of %r11 (it is already loaded a few instructions before).
> Do not needlessly increment %rsp - we are going to return to userspace
> via SYSRET, this insn doesn't use stack for return.
Applied.
>
> Changes since v1: ad
On Tue, 24 Feb 2015, J. Bruce Fields wrote:
> On Mon, Feb 23, 2015 at 05:22:12PM -0800, Benjamin Coddington wrote:
> > That sounds a lot closer to some of the work I've been doing to see if I can
> > come up with a way to solve the "where's the namespace I need?" problem.
> >
> > I agree with Greg
On Tue, 24 Feb 2015, Borislav Petkov wrote:
On Tue, Feb 24, 2015 at 03:16:38PM -0800, Vikas Shivappa wrote:
-#define NCAPINTS 13 /* N 32-bit words worth of info */
+#define NCAPINTS 14 /* N 32-bit words worth of info */
#define NBUGINTS 1 /* N 32-bit bug fla
> Subject: Re: [E1000-devel] [PATCH] ixgbe: make VLAN filter conditional in
> SR-IOV case
>
> On Thu, 2014-11-13 at 08:28 +, Hiroshi Shimamoto wrote:
> > From: Hiroshi Shimamoto
> >
> > Disable hardware VLAN filtering if netdev->features VLAN flag is
> > dropped.
> >
> > In SR-IOV case, ther
Hi Inha,
Thanks for the patch. Please see my comments inline.
2015-02-24 18:22 GMT+09:00 Inha Song :
> This patch add CLKOUT driver support for Exynos3250 SoC.
Could you please add a little more information? I know that it might
be pretty obvious to people familiar with this driver and/or hardwa
On Tue, Feb 24, 2015 at 10:56:16AM +0100, Borislav Petkov wrote:
> On Tue, Feb 24, 2015 at 08:15:35AM +, Naoya Horiguchi wrote:
> > Let me update my explanation about the problem. I wrote the description
> > about
> > race window of nmi shoot down threads. That's not wrong, but that's only the
On Tue, Feb 17, 2015 at 10:46:04AM +0100, Vlastimil Babka wrote:
> On 02/12/2015 08:15 AM, Joonsoo Kim wrote:
> >Compaction has anti fragmentation algorithm. It is that freepage
> >should be more than pageblock order to finish the compaction if we don't
> >find any freepage in requested migratetype
On Wed, Feb 18, 2015 at 04:04:05PM -0800, Andrew Morton wrote:
> On Thu, 12 Feb 2015 16:15:05 +0900 Joonsoo Kim wrote:
>
> > Compaction has anti fragmentation algorithm. It is that freepage
> > should be more than pageblock order to finish the compaction if we don't
> > find any freepage in reque
On Mon, Feb 23, 2015 at 12:51 PM, Michal Marek wrote:
> On 2015-02-23 15:30, Lucas De Marchi wrote:
>> This could be particularly bad if in a kernel version an option was
>> tristate and in a new version it changed to boolean. I'm not sure if
>> this is common to happen in kernel. Any code that di
Hi all,
Today's linux-next merge of the drm-intel tree got a conflict in
drivers/gpu/drm/i915/intel_display.c between commit f37b5c2be897
("drm/i915: Align initial plane backing objects correctly") from the
drm-intel-fixes tree and commit 6bf129df6ffa ("drm/i915: Use an
intermediate variable to av
On Wed 18 Feb 18:29 PST 2015, Stephen Boyd wrote:
> On 02/18/15 13:08, Bjorn Andersson wrote:
> > On Wed, Feb 18, 2015 at 12:28 PM, Stephen Boyd wrote:
After taking a deeper look at this I've come to the following
conclusion:
We can save 2100 bytes of data by spreading out the magic numbers fro
On Tue, Feb 24, 2015 at 8:42 AM, Harish Jenny Kandiga Nagaraj
wrote:
>
> On Monday 23 February 2015 09:21 PM, Michal Marek wrote:
>> On 2015-02-23 15:30, Lucas De Marchi wrote:
> Can we add some flag like
> KMOD_PROBE_FORCE_DIRECTORY_CHECK = 0x00040,
> and pass it to kmod_module_get_initstate to m
On Tue, Feb 24, 2015 at 4:00 PM, Denys Vlasenko wrote:
> Changes since v1: BUG_ON fix in traps.c
For future reference: This should be below the ---
--Andy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordo
On Tue, Feb 17, 2015 at 09:33:27AM +0100, Michal Hocko wrote:
> On Tue 17-02-15 14:24:59, Joonsoo Kim wrote:
> > It can be possible to return NULL in parent_mem_cgroup()
> > if use_hierarchy is 0.
>
> This alone is not sufficient because the low limit is present only in
> the unified hierarchy API
On 02/24, Maxime Ripard wrote:
> On Mon, Feb 23, 2015 at 03:11:40PM -0800, Stephen Boyd wrote:
> > >>> I would do something more simple that is just a list of keys and
> > >>> their location like this:
> > >>>
> > >>> device-serial-number = ;
> > >>> key1 = ;
> > >>> key2 = ;
> > >> I'm sorry, but
On Wed, Feb 25, 2015 at 5:34 AM, David Cohen
wrote:
> Hi,
>
>> If we decide to go ahead with the solution proposed by this patch for
>> practical reasons (which are good reasons indeed), I still have one
>> problem with its current form.
>>
>> As the discussion highlighted, this is an ACPI problem
Writing to registers is needed for setting configuration parameters.
Signed-off-by: Andrew Duggan
---
drivers/hid/hid-rmi.c | 40
1 file changed, 40 insertions(+)
diff --git a/drivers/hid/hid-rmi.c b/drivers/hid/hid-rmi.c
index 28579d7..e2a43a1 100644
--
A touchpad may have firmware based palm detection code enabled which
suppresses 2D data from being reported when the firmware believes a palm is
on the touchpad. This functionality is meant to be used in mouse mode without
a driver. When a driver is present, the driver can do a better job of
determ
When a finger is lifted from a Synaptics touchpad the firmware will continue
to interrupts for up to a second. These additional interrupts are know and
dribble interrupts. Since the data read from the touchpad does not change
the input subsystem only reports a single event. This makes the servicing
On Tue, Feb 24, 2015 at 05:51:46PM +0100, Michal Hocko wrote:
> On Tue 24-02-15 17:18:17, Minchan Kim wrote:
> > Historically, we have disabled reclaiming completely with swapoff
> > or non-swap configurable system. It did make sense but problem
> > for lazy free pages is that we couldn't get a cha
> On 2/3/15 05:26, Chen Gang S wrote:
>
> [...]
>
>>
>> - Xtensa gcc5 cross compiler has issues:
>>
>>it causes more than 10 broken areas with allmodconfig (but no issues
>>with defconfig). I guess, in fact, it is only 1 real issue (which can
>>cause all breaks), and I shall try to
On Thu, Feb 05, 2015 at 04:52:58PM -0500, Murali Karicheri wrote:
> If there is a DT node available for the root bridge's parent device,
> use the dma configuration from that device node. For example, keystone
> PCI devices would require dma_pfn_offset to be set correctly in the
> device structure
On Mon, 23 Feb 2015, r...@redhat.com wrote:
> From: Rik van Riel
>
> Ensure that cpus specified with the isolcpus= boot commandline
> option stay outside of the load balancing in the kernel scheduler.
>
> Operations like load balancing can introduce unwanted latencies,
> which is exactly what t
On Mon, 23 Feb 2015, r...@redhat.com wrote:
> From: Rik van Riel
>
> The previous patch makes it so the code skips over isolcpus when
> building scheduler load balancing domains. This makes it hard to
> see for a user which of the CPUs in a cpuset are participating in
> load balancing, and which
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 6088beef3f7517717bd21d90b379714dd0837079 ]
NAPI poll logic now enforces that a poller returns exactly the budget
when it wants to be called again.
If a driver l
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit ac64da0b83d82abe62f78b3d0e21cca31aea24fa ]
softnet_data.input_pkt_queue is protected by a spinlock that
we must hold when transferring packets from victim queue
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Hagen Paul Pfeifer
[ Upstream commit 9d289715eb5c252ae15bd547cb252ca547a3c4f2 ]
Reduce the attack vector and stop generating IPv6 Fragment Header for
paths with an MTU smaller than the minimum
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
[ Upstream commit 86f3cddbc3037882414c7308973530167906b7e9 ]
While working on rhashtable walking I noticed that the UDP diag
dumping code is buggy. In particular, the socket skippi
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hagen Paul Pfeifer
[ Upstream commit 9d289715eb5c252ae15bd547cb252ca547a3c4f2 ]
Reduce the attack vector and stop generating IPv6 Fragment Header for
paths with an MTU smaller than the minimum
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Govindarajulu Varadarajan <_gov...@gmx.com>
[ Upstream commit 24e579c8898aa641ede3149234906982290934e5 ]
With the commit d75b1ade567ffab ("net: less interrupt masking in NAPI") napi
repoll is d
3.10-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 811230cd853d62f09ed0addd0ce9a1b9b0e13fb5 ]
When I added sk_pacing_rate field, I forgot to initialize its value
in the per cpu unicast_sock used in ip_send_unicas
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Frederic Sowa
[ Upstream commit 6e9e16e6143b725662e47026a1d0f270721cdd24 ]
Lubomir Rintel reported that during replacing a route the interface
reference counter isn't correctly decremen
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Saran Maruti Ramanara
[ Upstream commit cfbf654efc6d78dc9812e030673b86f235bf677d ]
When making use of RFC5061, section 4.2.4. for setting the primary IP
address, we're passing a wrong paramete
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 0d32ef8cef9aa8f375e128f78b77caceaa7e8da0 ]
Doing the following commands on a non idle network device
panics the box instantly, because cpu_bstats gets overwritte
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Haiyang Zhang
[ Upstream commit d953ca4ddf71aa91a4596b2ff7ff1598f6ad4708 ]
The existing code frees the skb in EAGAIN case, in which the skb will be
retried from upper layer and used again.
Als
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
[ Upstream commit 06539d3071067ff146a9bffd1c801fa56d290909 ]
Signed-off-by: Christoph Hellwig
Signed-off-by: David S. Miller
Signed-off-by: Greg Kroah-Hartman
---
net/soc
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Austin Lund
commit a8f29e89f2b54fbf2c52be341f149bc195b63a8b upstream.
Userspace expects to see a long space before the first pulse is sent on
the lirc device. Currently, if a long time has pa
This is the start of the stable review cycle for the 3.18.8 release.
There are 20 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 Fri Feb 27 02:08:41 UTC 2015.
Anything receive
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit bdbbb8527b6f6a358dbcb70dac247034d665b8e4 ]
In commit be9f4a44e7d41 ("ipv4: tcp: remove per net tcp_sock")
I tried to address contention on a socket lock, but the
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
[ Upstream commit e2a4800e75780ccf4e6c2487f82b688ba736eb18 ]
When we've run out of space in the output buffer to store more data, we
will call zlib_deflate with a NULL output
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Frederic Sowa
[ Upstream commit 6e9e16e6143b725662e47026a1d0f270721cdd24 ]
Lubomir Rintel reported that during replacing a route the interface
reference counter isn't correctly decremen
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Roopa Prabhu
[ Upstream commit 59cc49b5b096cdc1f16706a9f931416b2332 ]
Reported in: https://bugzilla.kernel.org/show_bug.cgi?id=92081
This patch avoids calling rtnl_notify if the device nd
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 811230cd853d62f09ed0addd0ce9a1b9b0e13fb5 ]
When I added sk_pacing_rate field, I forgot to initialize its value
in the per cpu unicast_sock used in ip_send_unicas
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: "subas...@codeaurora.org"
[ Upstream commit fc752f1f43c1c038a2c6ae58cc739ebb5953ccb0 ]
An exception is seen in ICMP ping receive path where the skb
destructor sock_rfree() tries to access a fr
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Herbert Xu
[ Upstream commit 86f3cddbc3037882414c7308973530167906b7e9 ]
While working on rhashtable walking I noticed that the UDP diag
dumping code is buggy. In particular, the socket skippi
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 6088beef3f7517717bd21d90b379714dd0837079 ]
NAPI poll logic now enforces that a poller returns exactly the budget
when it wants to be called again.
If a driver l
On Tue, 2015-02-24 at 16:16 -0800, David Rientjes wrote:
> Now that gigantic pages are dynamically allocatable, care must be taken
> to ensure that p->first_page is valid before setting PageTail.
>
> If this isn't done, then it is possible to race and have compound_head()
> return NULL.
>
> Signe
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Frederic Sowa
[ Upstream commit df4d92549f23e1c037e83323aff58a21b3de7fe0 ]
Not caching dst_entries which cause redirects could be exploited by hosts
on the same subnet, causing a severe
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Borkmann
[ Upstream commit 600ddd6825543962fb807884169e57b580dba208 ]
When hitting an INIT collision case during the 4WHS with AUTH enabled, as
already described in detail in commit 1be
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit ac64da0b83d82abe62f78b3d0e21cca31aea24fa ]
softnet_data.input_pkt_queue is protected by a spinlock that
we must hold when transferring packets from victim queue
3.18-stable review patch. If anyone has any objections, please let me know.
--
From: Willem de Bruijn
[ Upstream commit f812116b174e59a350acc8e4856213a166a91222 ]
The sockaddr is returned in IP(V6)_RECVERR as part of errhdr. That
structure is defined and allocated on the stack
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Hannes Frederic Sowa
[ Upstream commit df4d92549f23e1c037e83323aff58a21b3de7fe0 ]
Not caching dst_entries which cause redirects could be exploited by hosts
on the same subnet, causing a severe
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: "subas...@codeaurora.org"
[ Upstream commit fc752f1f43c1c038a2c6ae58cc739ebb5953ccb0 ]
An exception is seen in ICMP ping receive path where the skb
destructor sock_rfree() tries to access a fr
This is the start of the stable review cycle for the 3.14.34 release.
There are 17 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 Fri Feb 27 02:08:17 UTC 2015.
Anything receiv
3.14-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Westphal
[ Upstream commit e2a4800e75780ccf4e6c2487f82b688ba736eb18 ]
When we've run out of space in the output buffer to store more data, we
will call zlib_deflate with a NULL output
701 - 800 of 923 matches
Mail list logo
