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 associated VF network device but this
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.
Note that the RTL_VER_01 on
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
---
Documentation/devicetree/bindings/arm/atmel-at91.txt | 3 ++-
arch/arm/boot/dts/
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
---
drivers/tty/serial/a
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
--- a/arch/arm/boot/dts/sama5d2.dtsi
+++ b/arch/arm/boot/dts/sama5d2
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 changed, 28 insertions(+), 6 deletions(-)
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 100644
--- a/drivers/clk/at91/clk-main.c
+
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 +
arch/arm/mach-at91/sama5.c
Signed-off-by: Alexandre Belloni
---
drivers/clocksource/tcb_clksrc.c | 55 ++--
1 file changed, 53 insertions(+), 2 deletions(-)
diff --git a/drivers/clocksource/tcb_clksrc.c b/drivers/clocksource/tcb_clksrc.c
index d4ca9962a759..e49f6cf2daf3 100644
--- a/dri
Signed-off-by: Alexandre Belloni
---
drivers/irqchip/irq-atmel-aic5.c | 22 +-
1 file changed, 21 insertions(+), 1 deletion(-)
diff --git a/drivers/irqchip/irq-atmel-aic5.c b/drivers/irqchip/irq-atmel-aic5.c
index 2a624d87a035..e4eb594bf4ef 100644
--- a/drivers/irqchip/irq-at
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
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
> @@ -0,0 +1,948 @@
> +/*
> + * Co
Please, disregard that series, it has been sent by mistake.
On 02/02/2017 at 19:51:51 +0100, Alexandre Belloni wrote:
> 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
On Wed, Feb 1, 2017 at 6:06 PM, Rafał Miłecki wrote:
> On 02/01/2017 11:39 PM, Jon Mason wrote:
>>
>> From: Zac Schroff
>>
>> Fix a bug in the 'bgmac' driver init sequence that blind writes for init
>> sequence where it should preserve most bits other than the ones it is
>> deliberately manipulat
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 beneath
The sama5d2 Xplained can wake up with its RTC. Enable that feature.
Signed-off-by: Alexandre Belloni
---
arch/arm/boot/dts/at91-sama5d2_xplained.dts | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/boot/dts/at91-sama5d2_xplained.dts
b/arch/arm/boot/dts/at91-sama5d2_xplained.dts
inde
On Thu, Feb 2, 2017 at 7:54 PM, Thomas Gleixner wrote:
> 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 concurren
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
>>> '__inittest' [-Wunused-function]
>>> arch/arm/crypto/aes-
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] [drm:intel_cpu_fifo_underrun_irq_handler [i915]]
>> *ERROR* CPU pipe A FIFO underrun
>
On 02/02/2017 10:58 AM, Russell King - ARM Linux wrote:
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
Hi Ard,
[auto build test WARNING on linus/master]
[also build test WARNING on v4.10-rc6 next-20170202]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux/commits/Ard-Biesheuvel/log2-make-order_base_2
Mention the trade-off between waiting for writeback and potentially
causing hot cache refaults in the code where we make this decisions
and activate writeback pages.
Signed-off-by: Johannes Weiner
---
mm/vmscan.c | 9 +
1 file changed, 9 insertions(+)
diff --git a/mm/vmscan.c b/mm/vmsca
Memory pressure can put dirty pages at the end of the LRU without anybody
running into dirty limits. Don't start writing individual pages from
kswapd while the flushers might be asleep.
Unlike the old direct reclaim flusher wakeup (removed in the next
patch) that flushes the number of pages just
Patch series "mm: vmscan: fix kswapd writeback regression".
We noticed a regression on multiple hadoop workloads when moving from 3.10
to 4.0 and 4.6, which involves kswapd getting tangled up in page writeout,
causing direct reclaim herds that also don't make progress.
I tracked it down to the th
Hi Andrew,
here are some minor updates to the series. It's nothing functional,
just code comments and updates to the changelogs from the mailing list
discussions. Since we don't have a good delta system for changelogs
I'm resending the entire thing as a drop-in replacement for -mm.
These are the
We noticed a performance regression when moving hadoop workloads from 3.10
kernels to 4.0 and 4.6. This is accompanied by increased pageout activity
initiated by kswapd as well as frequent bursts of allocation stalls and
direct reclaim scans. Even lowering the dirty ratios to the equivalent of
le
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 Danton
Cc: Mel Gorman
S
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 wit
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. Remo
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
> ---
> arch/arm/boot/dts/socfpga_arria10.dtsi | 7 +++
> 1 file changed, 7 insertions(+)
>
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 write) are also affected
/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 on
On Thu, Feb 02, 2017 at 02:14:10PM +0900, Minchan Kim wrote:
> Hi Johannes,
>
> On Tue, Jan 31, 2017 at 04:38:10PM -0500, Johannes Weiner wrote:
> > On Tue, Jan 31, 2017 at 11:45:47AM -0800, Shaohua Li wrote:
> > > On Tue, Jan 31, 2017 at 01:59:49PM -0500, Johannes Weiner wrote:
> > > > Hi Shaohua
* h...@zytor.com wrote:
> On February 1, 2017 11:16:00 PM PST, Ingo Molnar wrote:
> >
> >* Nicolas Iooss wrote:
> >
> >> With %Ld, my compiler (gcc 6.3.1 on x86_64) complains:
> >>
> >> arch/x86/tools/relocs.c:400:7: error: format ‘%Ld’ expects argument
> >of
> >> type ‘long long int’, but ar
>> 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
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
---
drivers/net/wirele
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 CONFIG_RANDOMIZE_BASE and
> KASLR
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'
> [-Wunused-fu
On Thu, 2017-02-02 at 16:22 +0100, Antonio Murdaca wrote:
> This patch allows changing labels for cgroup mounts. Previously,
> running
> chcon on cgroupfs would throw an "Operation not supported". This
> patch
> specifically whitelist cgroupfs.
>
> The patch could also allow containers to write on
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 addresses.
> +#define GP
Add a common binding for describing serial/UART attached devices. Common
examples are Bluetooth, WiFi, NFC and GPS devices.
Serial attached devices are represented as child nodes of a UART node.
This may need to be extended for more complex devices with multiple
interfaces, but for the simple case
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 driver
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
Tested-By: Sebastian Re
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.
Signed-off
Here's V4 of the serdev bus support. Just 2 small fixes from V3 and
Sebastian's Tested-by(Thanks!). I fixed a module build breakage in
serdev.h and dropped setting of receive_room. It was only needed for the
ldisc->receive_buf() function.
There's a few additions Sebastion needed for more serial
Add a serdev controller driver for tty ports.
The controller is registered with serdev when tty ports are registered
with the TTY core. As the TTY core is built-in only, this has the side
effect of making serdev built-in as well.
Signed-off-by: Rob Herring
Reviewed-By: Sebastian Reichel
Tested-
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
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
>> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y release.
> What release can I remove it from?
>
> It isn't in 4.4.y, and 4.9.y d
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
> [-Werror=unus
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 long
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
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 as
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 cons
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
> parameter 'vgacon.scrollback_p
The TS-72xx/73xx boards have a CPLD watchdog which is configured to
reset the board after 8 seconds, if the kernel is large enough that this
takes about this time to decompress the kernel, we will encounter a
spurious reboot.
Do not pull ts72xx.h, but instead locally define what we need to disable
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
x86/efi: Only map RAM into EFI
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
drivers/pinctrl/sunxi/Kconfig:
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
> > which components are in
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 removed
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" ... thou
Hi,
your commit 80cca775cdc4f8555612d2943a2872076b33e0ff breaks Linux
booting in qemu-system-m68k:
qemu-system-m68k -nographic -M mcf5208evb -cpu m5208 -kernel
qemu-m68k-mcf5208-initramfspiggyback-kernel
[0.00] Linux version 4.9.6-1 (wbx@vopenadk) (gcc version
5.4.0 (GCC) ) #2 Thu Feb 2
On Thu, Feb 2, 2017 at 3:15 PM, Rafał Miłecki wrote:
> On 2017-02-02 01:31, Zac Schroff wrote:
>>
>> How about BCMA_IOCTL_PRESERVE_ACROSS_INIT?
>
>
> I think wireless drivers may still set some these bits during init.
>
> I've a simpler idea: make it bgmac specific. Call it sth like
> BGMAC_BCMA_I
> 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
On Thu, Feb 2, 2017 at 11:33 AM, 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.
>>
>>
>> We discussed this offline a
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 fr
>From 225248f9f11895dabd86e118b69220242aece94b Mon Sep 17 00:00:00 2001
From: Tejun Heo
Date: Thu, 2 Feb 2017 15:25:08 -0500
Consistently use UL postfix for mask calculation and drop unnecessary
(unsigned long) cast from the enum definitions.
Signed-off-by: Tejun Heo
---
Arnd,
I also queued th
On 02/02/2017 11:33 AM, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.4.47 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 sh
On 2 February 2017 at 20:17, 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 1297667083d5442aafe3e337b9413bf02b114edb
> Author: Matt Fleming
> Date:
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 1297667083d5442aafe3e337b9413bf02b114edb
> Author: Matt Fleming
> Date: Mon
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 sho
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 truncat
On Thursday, February 02, 2017 1:12 PM, Florian Fainelli wrote:
> The TS-72xx/73xx boards have a CPLD watchdog which is configured to
> reset the board after 8 seconds, if the kernel is large enough that this
> takes about this time to decompress the kernel, we will encounter a
> spurious reboot.
>
> -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
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 according to the build server.
Making the return type "unsigned long" is slightly excessive. If you
need an unsigned long to descr
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.
Thanks
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 1297667083d5442aafe3e337b941
> 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 according to the build server.
>
> Making the return type "unsign
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 an
On Thu, Feb 02, 2017 at 01:38:04PM -0700, Shuah Khan wrote:
> 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 issue
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
> >> 4c63c2454eff996c5e27991221106eb511f7db38 in the next v4.x.y re
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 --git a/drivers/mfd/rtsx_pcr.c b/drivers/mfd/rtsx_pcr
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
4c63c2454eff996c5e27
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 tra
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 F
Peter Zijlstra:
> > >> kernel/locking/rwsem.c:126:2: error: implicit declaration of functi=
on 'lock_downgrade' [-Werror=3Dimplicit-function-declaration]
> > lock_downgrade(&sem->dep_map, _RET_IP_);
> > ^~
:::
> This is what you need !LOCKDEP stubs for ;-)
Ok, here is
> Il giorno 02 feb 2017, alle ore 16:30, Jens Axboe ha scritto:
>
> On 02/02/2017 02:19 AM, Paolo Valente wrote:
>> The scheme is clear. One comment, in case it could make sense and
>> avoid more complexity: since put_rq_priv is invoked in two different
>> contexts, process or interrupt, I didn
On Thu, Feb 2, 2017 at 12:06 PM, Tejun Heo wrote:
> 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.
I like this, but I have some design questions:
>
> * Thread mode is explici
On 02/02/2017 02:15 PM, Paolo Valente wrote:
>
>> Il giorno 02 feb 2017, alle ore 16:30, Jens Axboe ha scritto:
>>
>> On 02/02/2017 02:19 AM, Paolo Valente wrote:
>>> The scheme is clear. One comment, in case it could make sense and
>>> avoid more complexity: since put_rq_priv is invoked in two
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 boot_pa
On Wed, 01 Feb, at 03:02:14PM, Ard Biesheuvel wrote:
>
> Let's wait for Matt to comment on the x86 bits before reissuing
> anything, but if the subsequent patches still apply cleanly, I don't
> think there is a need to resend or re-sign.
This all looks fine to me now, thanks for the re-work David
The cache management functions always do the data cache PoU
(point of unification) operations even though it is not required
on some systems. NO need to clean data cache till PoU if all the
cache levels below PoUIS are WT (Write-Through) caches. It causes
a huge performance degradation when operati
> On 2 Feb 2017, at 21:36, Matt Fleming wrote:
>
>> On Wed, 01 Feb, at 03:02:14PM, Ard Biesheuvel wrote:
>>
>> Let's wait for Matt to comment on the x86 bits before reissuing
>> anything, but if the subsequent patches still apply cleanly, I don't
>> think there is a need to resend or re-sign.
Hello,
On Thu, Feb 02, 2017 at 01:32:19PM -0800, Andy Lutomirski wrote:
> > * Thread mode is explicitly enabled on a cgroup by writing "enable"
> > into "cgroup.threads" file. The cgroup shouldn't have any child
> > cgroups or enabled controllers.
>
> Why do you need to manually turn it on?
On Thu, Feb 02, 2017 at 03:29:22PM -0500, Tejun Heo wrote:
> From 225248f9f11895dabd86e118b69220242aece94b Mon Sep 17 00:00:00 2001
> From: Tejun Heo
> Date: Thu, 2 Feb 2017 15:25:08 -0500
>
> Consistently use UL postfix for mask calculation and drop unnecessary
> (unsigned long) cast from the en
On Thu, 02 Feb, at 04:55:06PM, Peter Zijlstra wrote:
> On Tue, Jan 31, 2017 at 10:22:47AM -0700, Ross Zwisler wrote:
> > On Tue, Jan 31, 2017 at 4:48 AM, Mike Galbraith wrote:
> > > On Tue, 2017-01-31 at 16:30 +0530, Sachin Sant wrote:
>
>
> Could some of you test this? It seems to cure things i
Hi all,
Today's linux-next merge of the powerpc tree got a conflict in:
arch/powerpc/Kconfig
between commit:
f2574030b0e3 ("powerpc: Revert the initial stack protector support")
from the powerpc-fixes tree and commit:
d6c569b99558 ("powerpc/64: Move HAVE_CONTEXT_TRACKING from pseries to
On 01/30/2017 05:58 PM, Nobuhiro Iwamatsu wrote:
+
+ if (zap && *paddr + sz - cxt->phys_addr > cxt->size) {
+ dev_err(dev, "no room for %s mem region (0x%zx@0x%llx) in
(0x%lx@0x%llx)\n",
+ name, sz, (unsigned long long)*paddr,
+ cxt
From: Arnd Bergmann
Date: Wed, 1 Feb 2017 17:46:02 +0100
> The device match tables for both the xgene_enet driver and its phy driver
> have forward declarations that declare an array without a length, leading
> to a clang warning when they are not followed by an actual defitinition:
>
> drivers
501 - 600 of 765 matches
Mail list logo
