4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Elad Raz
[ Upstream commit 28e46a0f2e03ab4ed0e23cace1ea89a68c8c115b ]
The event_data starts from address 0x00-0x0C and not from 0x08-0x014. This
leads to duplication with
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Ahern
[ Upstream commit 8a430ed50bb1b19ca14a46661f3b1b35f2fb5c39 ]
rtm_table is an 8-bit field while table ids are allowed up to u32. Commit
709772e6e065
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Shannon Nelson
[ Upstream commit 003c941057eaa868ca6fedd29a274c863167230d ]
Fix up a data alignment issue on sparc by swapping the order
of the cookie byte array
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
[ Upstream commit f154be241d22298d2b63c9b613f619fa1086ea75 ]
Commit 448b4482c671 ("net: dsa: Add lockdep class to tx queues to avoid
lockdep splat")
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arkadi Sharshevsky
[ Upstream commit 400fc0106dd8c27ed84781c929c1a184785b9c79 ]
During transmission the skb is checked for headroom in order to
add vendor specific
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Arkadi Sharshevsky
[ Upstream commit 36bf38d158d3482119b3e159c0619b3c1539b508 ]
During transmission the skb is checked for headroom in order to
add vendor specific
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 7be2c82cfd5d28d7adb66821a992604eb6dd112e ]
Ashizuka reported a highmem oddity and sent a patch for freescale
fec driver.
But the problem
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: WANG Cong
[ Upstream commit 0fb44559ffd67de8517098b81f675fa0210f13f0 ]
Dmitry reported a deadlock scenario:
unix_bind() path:
u->bindlock ==> sb_writer
do_splice()
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Alexey Kodanev
[ Upstream commit 0dbd7ff3ac5017a46033a9d0a87a8267d69119d9 ]
Found that if we run LTP netstress test with large MSS (65K),
the first attempt from
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Lance Richardson
[ Upstream commit 75f01a4c9cc291ff5cb28ca1216adb163b7a20ee ]
When executing conntrack actions on skbuffs with checksum mode
CHECKSUM_COMPLETE, the
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Daniel Gonzalez Cabanelas
[ Upstream commit cd33b3e0da43522ff8e8f2b2b71d3d08298512b0 ]
Commit a1cba5613edf ("net: phy: Add Broadcom phy library for common
interfaces") make
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 493611ebd62673f39e2f52c2561182c558a21cb6 upstream.
With COW files they are the hotpath, just like for files with the
extent size hint attribute. We
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: "Darrick J. Wong"
commit c364b6d0b6cda1cd5d9ab689489adda3e82529aa upstream.
In a bmapx call, bmv_count is the total size of the array, including the
zeroth element
On Thu, Feb 02, 2017 at 10:26:55AM -0800, Steve Longerbeam wrote:
> On 02/02/2017 09:56 AM, Russell King - ARM Linux wrote:
> >and for whatever reason we end up falling out through free_ring. This
> >is VERY bad news, because it means that the ring which SMFC took a copy
> >of is now freed
On Thu, Feb 2, 2017 at 11:09 AM, wrote:
> From: Thor Thayer
>
> Add the device tree entries needed to support the EMAC AXI
> bus settings on the Arria10 SoCFPGA chip.
>
> Signed-off-by: Thor Thayer
> ---
>
Direct reclaim has been replaced by kswapd reclaim in pretty much all
common memory pressure situations, so this code most likely doesn't
accomplish the described effect anymore. The previous patch wakes up
flushers for all reclaimers when we encounter dirty pages at the tail end
of the LRU.
Dirty pages can easily reach the end of the LRU while there are still
clean pages to reclaim around. Don't let kswapd write them back just
because there are a lot of them. It costs more CPU to find the clean
pages, but that's almost certainly better than to disrupt writeback from
the flushers
On Tue, Jan 31, 2017 at 12:19:54PM +, Mark Rutland wrote:
> From: Ding Tianhong
>
> Erratum Hisilicon-161010101 says that the ARM generic timer counter "has
> the potential to contain an erroneous value when the timer value
> changes". Accesses to TVAL (both read and
On Wed, 1 Feb 2017, Arnd Bergmann wrote:
> clang warns about unused inline functions by default:
>
> arch/arm/crypto/aes-cipher-glue.c:68:1: warning: unused function '__inittest'
> [-Wunused-function]
> arch/arm/crypto/aes-cipher-glue.c:69:1: warning: unused function '__exittest'
>
Hi Matt,
A kernel bug report was opened against Ubuntu [0]. After a kernel
bisect, it was found that reverting the following commit resolved this bug:
commit 1297667083d5442aafe3e337b9413bf02b114edb
Author: Matt Fleming
Date: Mon Sep 19 13:09:09 2016 +0100
On Tue, 2017-01-24 at 09:09 +0100, Ingo Molnar wrote:
> * Yu-cheng Yu wrote:
This needs to go to stable too, 4.8 and 4.9
Jocke
>
> > The compacted-format XSAVES area is determined at boot time and
> > never changed after. The field xsave.header.xcomp_bv indicates
> >
We had all these corrected in commit 0c8c6ba00cbf ("pinctrl: sunxi:
make bool drivers explicitly non-modular") but this new one recently
crept in.
The Kconfig currently controlling compilation of this code is:
drivers/pinctrl/sunxi/Kconfig:config PINCTRL_SUN5I
Please pull:
git://linux-nfs.org/~bfields/linux.git tags/nfsd-4.10-2
Three more miscellaneous nfsd bugfixes.
Christoph Hellwig (1):
nfsd: special case
On 02/02/2017 11:37 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.8 release.
> There are 51 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
On 02/02/2017 03:36 PM, Laura Abbott wrote:
> On 02/02/2017 12:17 PM, Joseph Salisbury wrote:
>> Hi Matt,
>>
>> A kernel bug report was opened against Ubuntu [0]. After a kernel
>> bisect, it was found that reverting the following commit resolved this bug:
>>
>> commit
Linus,
Please pull the latest core-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
core-urgent-for-linus
# HEAD: b5b46c4740aed1538544f0fa849c5b76c7823469 objtool: Fix IRET's opcode
A fix for a bad opcode in objtool's instruction decoder.
From: Borislav Petkov
It is a debugging statement so make it be issued only then.
No functionality change.
Signed-off-by: Borislav Petkov
Cc: Lee Jones
---
drivers/mfd/rtsx_pcr.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
On Tue, 31 Jan, at 03:13:49PM, David Howells wrote:
> diff --git a/arch/x86/boot/compressed/eboot.c
> b/arch/x86/boot/compressed/eboot.c
> index f99978db6b6f..57c2c9c71e53 100644
> --- a/arch/x86/boot/compressed/eboot.c
> +++ b/arch/x86/boot/compressed/eboot.c
> @@ -988,6 +988,12 @@ struct
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
[ Upstream commit f154be241d22298d2b63c9b613f619fa1086ea75 ]
Commit 448b4482c671 ("net: dsa: Add lockdep class to tx queues to avoid
lockdep splat")
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 5149fd327f16e393c1d04fa5325ab072c32472bf upstream.
Setting aside 4 blocks globally for bmbt splits isn't all that useful,
as different threads can
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 255c516278175a6dc7037d1406307f35237d8688 upstream.
We can't just set minleft to 0 when we're low on space - that's exactly
what we need minleft for: to
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Ivan Vecera
[ Upstream commit b6677449dff674cf5b81429b11d5c7f358852ef9 ]
Any bridge options specified during link creation (e.g. ip link add)
are ignored as br_dev_newlink()
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Robert Shearman
[ Upstream commit 85c814016ce3b371016c2c054a905fa2492f5a65 ]
When attempting to free lwtunnel state after the module for the encap
has been unloaded an
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Arkadi Sharshevsky
[ Upstream commit 36bf38d158d3482119b3e159c0619b3c1539b508 ]
During transmission the skb is checked for headroom in order to
add vendor specific
On Mon, Jan 30, 2017 at 02:43:01PM +0530, Kishon Vijay Abraham I wrote:
>
>
> On Saturday 28 January 2017 01:35 AM, Krzysztof Kozlowski wrote:
> > Hi,
> >
> > Suggested by Marek, continuation of cleanup of PMU register defines
> > in headers.
> >
> > Let's keep all of them in
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: hayeswang
[ Upstream commit 19c0f40d4fca3a47b8f784a627f0467f0138ccc8 ]
Fix the hw rx checksum is always enabled, and the user couldn't switch
it to sw rx checksum.
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: stephen hemminger
[ Upstream commit 0719e72ccb801829a3d735d187ca8417f0930459 ]
The receive callback (in tasklet context) is using RCU to get reference
to
Arnd Bergmann writes:
> On Thu, Feb 2, 2017 at 10:25 AM, Rusty Russell wrote:
>> Arnd Bergmann writes:
>>> clang warns about unused inline functions by default:
>>>
>>> arch/arm/crypto/aes-cipher-glue.c:68:1: warning: unused function
>>>
On Thu, Feb 2, 2017 at 4:54 AM, Baoquan He wrote:
> This is v4 post.
>
> In the previous 3 versions I tried to detect and determine kernel image
> mapping size at runtime for x86_64. With this the inconsistency between
> KASLR code is not compiled in by disabling
Linus,
Please pull the latest efi-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
efi-urgent-for-linus
# HEAD: c8f325a59cfc718d13a50fbc746ed9b415c25e92 efi/fdt: Avoid FDT
manipulation after ExitBootServices()
Two EFI boot fixes, one for arm64
Linus,
Please pull the latest x86-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
x86-urgent-for-linus
# HEAD: 0becc0ae5b42828785b589f686725ff5bc3b9b25 x86/mce: Make timer
handling more robust
Misc fixes:
- two microcode loader fixes
- two
Peter Zijlstra:
> > >> kernel/locking/rwsem.c:126:2: error: implicit declaration of functi=
on 'lock_downgrade' [-Werror=3Dimplicit-function-declaration]
> > lock_downgrade(>dep_map, _RET_IP_);
> > ^~
:::
> This is what you need !LOCKDEP stubs for ;-)
Ok, here is the
Hi,
Last changes around PMU driver (the header)
On top of previous pull request.
This patch (and others below) might be also pulled by Linus or Lee for:
[PATCH v3 0/7] Pad retentions support for Exynos5433
http://www.mail-archive.com/linux-kernel@vger.kernel.org/msg1321519.html
Best regards,
Hi Daniel,
On Tue, Jan 31, 2017 at 12:19:54PM +, Mark Rutland wrote:
> From: Ding Tianhong
>
> Erratum Hisilicon-161010101 says that the ARM generic timer counter "has
> the potential to contain an erroneous value when the timer value
> changes". Accesses to TVAL
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Brian Foster
commit 5a93790d4e2df73e30c965ec6e49be82fc3ccfce upstream.
xfs_attr_[get|remove]() have unlocked attribute fork checks to optimize
away a lock cycle in cases
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: "Darrick J. Wong"
commit 83d230eb5c638949350f4761acdfc0af5cb1bc00 upstream.
sb_dirblklog is added to sb_blocklog to compute the directory block size
in bytes.
>> Nice to have:
>> 1) Readout using "perf(1)" [subset of modes that make sense ... tying
>> monitoring
>> to resctrl file system will make most command line usage of perf(1) close to
>> impossible.
>
>
> We discussed this offline and I still disagree that it is close to
> impossible to use
The serdev bus is designed for devices such as Bluetooth, WiFi, GPS
and NFC connected to UARTs on host processors. Tradionally these have
been handled with tty line disciplines, rfkill, and userspace glue such
as hciattach. This approach has many drawbacks since it doesn't fit
into the Linux
Register a serdev controller with the serdev bus when a tty_port is
registered. This creates the serdev controller and create's serdev
devices for any DT child nodes of the tty_port's parent (i.e. the UART
device).
Signed-off-by: Rob Herring
Reviewed-By: Sebastian Reichel
Introduce a client (upward direction) operations struct for tty_port
clients. Initially supported operations are for receiving data and write
wake-up. This will allow for having clients other than an ldisc.
Convert the calls to the ldisc to use the client ops as the default
operations.
On Thu, Feb 02, 2017 at 12:36:12PM +0100, Arnd Bergmann wrote:
> It looks like a search+replace accidentally change one function pointer that
> should have remained as before, as shown by this new warning:
>
> fs/ext4/file.c:279:1: error: 'ext4_dax_huge_fault' defined but not used
>
This patch implements cgroup v2 thread support. The goal of the
thread mode is supporting hierarchical accounting and control at
thread granularity while staying inside the resource domain model
which allows coordination across different resource controllers and
handling of anonymous resource
On Tue, Jan 10, 2017 at 4:28 PM, Manuel Schölling
wrote:
> The impact of the persistent scrollback feature on the code size is
> rather small, so the config option is removed. The feature stays
> disabled by default and can be enabled by using the boot command line
>
css_task_iter currently always walks all tasks. With the scheduled
cgroup v2 thread support, the iterator would need to handle multiple
types of iteration. As a preparation, add @flags to
css_task_iter_start() and implement CSS_TASK_ITER_PROCS. If the flag
is not specified, it walks all tasks
On Wed, Feb 01, 2017 at 06:01:17PM +0100, Arnd Bergmann wrote:
> Building with clang shows lots of warning like:
>
> drivers/amba/bus.c:447:8: warning: implicit conversion from 'long long' to
> 'int' changes value from 4294967248 to -48
...
> arch/arm/include/asm/atomic.h:21:27: note: expanded
On 02/02/2017 03:57 PM, Greg KH wrote:
> On Thu, Feb 02, 2017 at 02:58:16PM -0500, Joseph Salisbury wrote:
>> On 02/02/2017 01:23 PM, Greg KH wrote:
>>> On Thu, Feb 02, 2017 at 12:38:33PM -0500, Joseph Salisbury wrote:
Hello,
Please consider reverting commit
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Sandeen
commit 657bdfb7f5e68ca5e2ed009ab473c429b0d6af85 upstream.
The GETNEXTQOTA ioctl takes whatever ID is sent in,
and looks for the next active quota for an user
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit d2b3964a0780d2d2994eba57f950d6c9fe489ed8 upstream.
Due to the way how xfs_iomap_write_allocate tries to convert the whole
found extents from delalloc to
For spinlock and read-write locks, both *_unlock() and *_unlock_irq()
functions are inlined if !PREEMPT. Whereas the *_unlock_bh() and
*unlock_irqrestore() are not inlined as that will increase the size
of the kernel binary.
Given the fact that the PV qspinlock unlock call is a callee-saved
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Kefeng Wang
[ Upstream commit 03e4deff4987f79c34112c5ba4eb195d4f9382b0 ]
Just like commit 4acd4945cd1e ("ipv6: addrconf: Avoid calling
netdevice notifiers with RCU
On Fri, May 27, 2016 at 10:19 AM, Chris Bainbridge
wrote:
> On 25 May 2016 at 08:31, Sedat Dilek wrote:
>> Hi Daniel,
>>
>> with latest Linus Git I see this with my Intel SandyBridge GPU...
>>
>> [ 17.629014]
/linux-xtensa.git tags/xtensa-20170202
for you to fetch changes up to 4b3e6f2ef3722f1a6a97b6034ed492c1a21fd4ae:
xtensa: fix noMMU build on cores with MMU (2017-01-31 18:49:59 -0800)
Xtensa fix for v4.10-rc7:
- fix noMMU build
consider that you changed the length of this datatype on 64 bit systems.
unsigned int is always 32 bit, but size_t may be 64 bit too
Am 02.02.2017 um 11:19 schrieb Amadeusz Sławiński:
cleanup to consolidate type used for len variables
Signed-off-by: Amadeusz Sławiński
I'm going to need to cool down for a bit. Let's resume this on Monday,
maybe we can get back to being constructive after the weekend.
Thierry
signature.asc
Description: PGP signature
> Hi,
>
> your commit 80cca775cdc4f8555612d2943a2872076b33e0ff breaks Linux
> booting in qemu-system-m68k:
Hi.
Do you compile with CONFIG_M5272?
Is f85de347c974cdf97b1026180995d912d7d0 also in your tree?
Nikita
> -Original Message-
> From: Borislav Petkov [mailto:b...@alien8.de]
> Sent: Thursday, February 2, 2017 1:11 PM
>
> Yazen, what BD generation is your machine?
>
The processors are revision C0. Also, I forgot to mention it's a 2P G34 system.
Thanks,
Yazen
Linus,
Please pull the latest perf-urgent-for-linus git tree from:
git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
perf-urgent-for-linus
# HEAD: fff4b87e594ad3d2e4f51e8d3d86a6f9d3d8b654 perf/x86/intel/uncore: Make
package handling more robust
Five kernel fixes:
- an mmap
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Elad Raz
[ Upstream commit 28e46a0f2e03ab4ed0e23cace1ea89a68c8c115b ]
The event_data starts from address 0x00-0x0C and not from 0x08-0x014. This
leads to duplication with
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Arkadi Sharshevsky
[ Upstream commit 400fc0106dd8c27ed84781c929c1a184785b9c79 ]
During transmission the skb is checked for headroom in order to
add vendor specific
This is the start of the stable review cycle for the 4.9.8 release.
There are 51 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 Sat Feb 4 18:33:31 UTC 2017.
Anything
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Eric Dumazet
[ Upstream commit 7be2c82cfd5d28d7adb66821a992604eb6dd112e ]
Ashizuka reported a highmem oddity and sent a patch for freescale
fec driver.
But the problem
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Rolf Neugebauer
[ Upstream commit 501db511397fd6efff3aa5b4e8de415b9550 ]
This patch part reverts fd2a0437dc33 and e858fae2b0b8 which introduced a
subtle change
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: David Ahern
[ Upstream commit 9ed59592e3e379b2e9557dc1d9e9ec8fcbb33f16]
Trying to add an mpls encap route when the MPLS modules are not loaded
hangs. For example:
On Thu, Feb 02, 2017 at 01:29:16PM -0500, Mike Snitzer wrote:
> Are you trying to say that this happens using a certain .config?
>
> Also, not sure why you didn't cc Christoph (or Jens) seeing as these
> changes are _not_ staged in linux-next by linux-dm.git.
No changes to dm caused this, it was
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Christoph Hellwig
commit 84a4620cfe97c9d57e39b2369bfb77faff55063d upstream.
There are only two reasons for xfs_log_force / xfs_log_force_lsn to fail:
one is an I/O error, for
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Amir Goldstein
commit 1fc4d33fed124fb182e8e6c214e973a29389ae83.
The size of the xfs_mode_to_ftype[] conversion table
was too small to handle an invalid value of
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Amir Goldstein
commit a324cbf10a3c67aaa10c9f47f7b5801562925bc2 upstream.
Check for invalid file type in xfs_dinode_verify()
and fail to load the inode structure from disk.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/generic.h| 2 +
arch/arm/mach-at91/pm.c | 163
arch/arm/mach-at91/pm.h | 13 +---
arch/arm/mach-at91/pm_suspend.S | 104
When going to suspend, the UART registers may be lost because the power to
VDDcore is cut. This is not an issue in the normal case but when
no_console_suspend is used, we need to restore the registers in order to
get a functional console.
Signed-off-by: Alexandre Belloni
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/sama5d2.dtsi | 6 --
1 file changed, 6 deletions(-)
diff --git a/arch/arm/boot/dts/sama5d2.dtsi b/arch/arm/boot/dts/sama5d2.dtsi
index 111470359235..908b0baca42f 100644
---
When suspending to RAM, the power to the core is cut and the register
values are lost. Save and restore more registers than just IMR.
Signed-off-by: Alexandre Belloni
---
drivers/pinctrl/pinctrl-at91-pio4.c | 34 --
1 file
Signed-off-by: Alexandre Belloni
---
drivers/clk/at91/clk-main.c | 71 +
1 file changed, 71 insertions(+)
diff --git a/drivers/clk/at91/clk-main.c b/drivers/clk/at91/clk-main.c
index c813c27f2e58..63be69cd1437
SFRBU, the Special Function Registers Backup manage specific aspects of the
integrated memory, bridge implementations, processor and other
functionality not controlled elsewhere.
Signed-off-by: Alexandre Belloni
---
On Tue, Jan 31, 2017 at 9:43 PM, Hoan Tran wrote:
> Next generation of X-Gene SoC's GPIO hardware register map is very
> similar to DW GPIO. It only differs by a few register addresses.
> This patch modifies DW GPIO driver to accommodate the difference
> in a few register
On 02/02/2017 10:44, Christoph Hellwig wrote:
> ec8013bedd ("dm: do not forward ioctls from logical volumes to the
> underlying device"),
>
> The trivial fix would be to add a select of the SCSI_REQUEST symbol
> to dm, but my gut feeling teels me the call is simply wrong, and
> should be
Hello Peterz/Andi,
On Thu, 2 Feb 2017, Luck, Tony wrote:
Nice to have:
1) Readout using "perf(1)" [subset of modes that make sense ... tying
monitoring
to resctrl file system will make most command line usage of perf(1) close to
impossible.
Vikas is pushing for "-R rdtgroup" ...
> On 2 Feb 2017, at 20:49, Linus Torvalds wrote:
>
> On Thu, Feb 2, 2017 at 9:04 AM, Ard Biesheuvel
> wrote:
>>
>> So update order_base_2() to adhere to its own documented interface.
>
> Ok, looks like you screwed up the types
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: David Ahern
[ Upstream commit ea7a80858f57d8878b1499ea0f1b8a635cc48de7 ]
Handle failure in lwtunnel_fill_encap adding attributes to skb.
Fixes: 571e722676fe ("ipv4:
4.4-stable review patch. If anyone has any objections, please let me know.
--
From: Florian Fainelli
[ Upstream commit 148d3d021cf9724fcf189ce4e525a094bbf5ce89 ]
The __bcm_sysport_tx_reclaim() function is used to reclaim transmit
resources in different
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Basil Gunn
[ Upstream commit 8a367e74c0120ef68c8c70d5a025648c96626dff ]
The ax.25 socket connection timed out & the sock struct has been
previously taken down ie. sock
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jakub Sitnicki
[ Upstream commit 02ca0423fd65a0a9c4d70da0dbb8f4b8503f08c7 ]
With ip6gre we have a tunnel header which also makes the tunnel MTU
smaller. We need to reserve
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: Jamal Hadi Salim
[ Upstream commit 0faa9cb5b3836a979864a6357e01d2046884ad52 ]
Demonstrating the issue:
.. add a drop action
$sudo $TC actions add action drop index 10
..
4.9-stable review patch. If anyone has any objections, please let me know.
--
From: David Ahern
[ Upstream commit ea7a80858f57d8878b1499ea0f1b8a635cc48de7 ]
Handle failure in lwtunnel_fill_encap adding attributes to skb.
Fixes: 571e722676fe ("ipv4:
On Mon, Jan 30, 2017 at 7:30 AM, George Cherian
wrote:
> diff --git a/drivers/crypto/cavium/cpt/cptvf_main.c
> b/drivers/crypto/cavium/cpt/cptvf_main.c
> new file mode 100644
> index 000..4cf466d
> --- /dev/null
> +++ b/drivers/crypto/cavium/cpt/cptvf_main.c
> @@
On Wed, 1 Feb 2017, Dmitry Vyukov wrote:
>
> Can't we still end up with an inconsistently setup timer?
> do_timerfd_settime executes timerfd_setup_cancel and timerfd_setup as
> two separate non-atomic actions. So if there are 2 concurrent
> timerfd_settime calls, one that needs cancel and another
Mention dirty expiration as a condition: we need dirty data that is too
recent for periodic flushing and not large enough for waking up limit
flushing. As per Mel.
Link: http://lkml.kernel.org/r/20170126174739.ga30...@cmpxchg.org
Signed-off-by: Johannes Weiner
Cc: Hillf
cgroup v2 is in the process of growing thread granularity support.
Once thread mode is enabled, the root cgroup of the subtree serves as
the proc_cgrp to which the processes of the subtree conceptually
belong and domain-level resource consumptions not tied to any specific
task are charged. In the
Hello,
This patchset implements cgroup v2 thread mode. It is largely based
on the discussions that we had at the plumbers last year. Here's the
rough outline.
* Thread mode is explicitly enabled on a cgroup by writing "enable"
into "cgroup.threads" file. The cgroup shouldn't have any child
Currently, writes "cgroup.procs" and "cgroup.tasks" files are all
handled by __cgroup_procs_write() on both v1 and v2. This patch
reoragnizes the write path so that there are common helper functions
that different write paths use.
While this somewhat increases LOC, the different paths are no
cgroup v2 is in the process of growing thread granularity support.
Once thread mode is enabled, the root cgroup of the subtree serves as
the proc_cgrp to which the processes of the subtree conceptually
belong and domain-level resource consumptions not tied to any specific
task are charged. In the
1 - 100 of 1530 matches
Mail list logo