Hi Liam,
> Am 30.08.2017 um 13:24 schrieb Liam Breck :
>
> Hi Nikolaus,
>
> On Wed, Aug 30, 2017 at 2:30 AM, H. Nikolaus Schaller
> wrote:
>> Hi Liam and Sebastian,
>>
>>> Am 29.08.2017 um 22:20 schrieb Liam Breck :
>>>
>>> Hi Nikolaus, thanks for the patch...
>>>
>>> On Tue, Aug 29, 2017 a
On Thu, Aug 31, 2017 at 07:52:41AM +0300, Amir Goldstein wrote:
> On Thu, Aug 31, 2017 at 6:51 AM, Xiong Zhou wrote:
> > hi,
> >
> > This happens on 4.13.0-rc7+ to commit 42ff72c
>
> Don't understand. Is this a regression? from which commit?
No. I'm just saying the exact kernel version: Linus tr
On 31/08/17 09:38, Ravi Bangoria wrote:
> 'Object code reading' test always fails on powerpc. Two reasons for
> the failure are:
>
> 1. When elf section is too big (size beyond 'unsigned int' max value).
> objdump fails to disassemble from such section. This was fixed with
> commit 0f6329bd7fc ("b
On 08/30/2017 03:02 PM, Laurent Dufour wrote:
> On 30/08/2017 07:58, Peter Zijlstra wrote:
>> On Wed, Aug 30, 2017 at 10:33:50AM +0530, Anshuman Khandual wrote:
>>> diff --git a/mm/filemap.c b/mm/filemap.c
>>> index a497024..08f3042 100644
>>> --- a/mm/filemap.c
>>> +++ b/mm/filemap.c
>>> @@ -1181,
Hi Bjorn,
After merging the rpmsg tree, today's linux-next build (x86_64
allmodconfig) failed like this:
ERROR: "qcom_glink_native_probe" [drivers/rpmsg/qcom_glink_rpm.ko] undefined!
ERROR: "qcom_glink_native_remove" [drivers/rpmsg/qcom_glink_rpm.ko] undefined!
Maybe caused by commit
6799c434
On 30 August 2017 at 19:16, Michael Ellerman wrote:
> Joe Stringer writes:
>
>> On 30 August 2017 at 15:59, Andrew Morton wrote:
>>> On Tue, 29 Aug 2017 16:01:14 -0700 Joe Stringer wrote:
>>>
Recent changes[0] to make use of __compiletime_assert() from
container_of() increased the usa
On Thu 2017-08-31 07:44:58, Kalle Valo wrote:
> David Miller writes:
>
> > From: Kalle Valo
> > Date: Wed, 30 Aug 2017 20:31:31 +0300
> >
> >> AFAICS the bug was introduced by 9df86e2e702c6 back in 2010. If the bug
> >> has been there for 7 years so waiting for a few more weeks should not
> >> h
Hi Anthony,
On Tue, Aug 22, 2017 at 06:03:38PM +0900, Anthony Kim wrote:
> The HiDeep touchscreen device is a capacitive multi-touch controller
> mainly for multi-touch supported devices use. It use I2C interface for
> communication to IC and provide axis X, Y, Z locations for ten finger
> touch t
On 30/08/17 16:04, Ritesh Harjani wrote:
> When CMDQ is halted the HW expects descriptor size to
> be same which is using in CMDQ mode.
> Thus adjust the desc_sz of sdhci accordingly.
>
> Without this patch below command gives ADMA error
> when CQE is enabled.
> cat /sys/kernel/debug/mmc0/mmc0:000
If the function bfq_update_next_in_service is invoked as a consequence
of the activation or requeueing of an entity, say E, and finds out
that E belongs to a higher-priority class than that of the current
next-in-service entity, then it sets next_in_service directly to
E. But this may lead to anoma
[SECOND TAKE, with just the name of one of the tester fixed]
Hi,
while testing the read-write unfairness issues reported by Mel, I
found BFQ failing to guarantee good responsiveness against heavy
random sync writes in the background, i.e., multiple writers doing
random writes and systematic fdatas
If the function bfq_update_next_in_service is invoked as a consequence
of the activation or requeueing of an entity, say E, then it doesn't
invoke bfq_lookup_next_entity to get the next-in-service entity. In
contrast, it follows a shorter path: if E happens to be eligible (see
commit "bfq-sq-mq: ma
To provide a very smooth service, bfq starts to serve a bfq_queue
only if the queue is 'eligible', i.e., if the same queue would
have started to be served in the ideal, perfectly fair system that
bfq simulates internally. This is obtained by associating each
queue with a virtual start time, and by
> Il giorno 31 ago 2017, alle ore 08:41, oleksa...@natalenko.name ha scritto:
>
>> Tested-by: Oleksander Natalenko
>
> I'm "Oleksandr" :).
>
Sorry, resending ...
Paolo
> 31.08.2017 08:10, Paolo Valente wrote:
>> Hi,
>> while testing the read-write unfairness issues reported by Mel, I
>> fou
Tested-by: Oleksander Natalenko
I'm "Oleksandr" :).
31.08.2017 08:10, Paolo Valente wrote:
Hi,
while testing the read-write unfairness issues reported by Mel, I
found BFQ failing to guarantee good responsiveness against heavy
random sync writes in the background, i.e., multiple writers doing
'Object code reading' test always fails on powerpc. Two reasons for
the failure are:
1. When elf section is too big (size beyond 'unsigned int' max value).
objdump fails to disassemble from such section. This was fixed with
commit 0f6329bd7fc ("binutils/objdump: Fix disassemble for huge elf
sectio
Fixed checkpatch errors, spaces before tabs.
Found using checkpatch.
Signed-off-by: Derek Robson
---
drivers/staging/pi433/rf69.h | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/staging/pi433/rf69.h b/drivers/staging/pi433/rf69.h
index fbccaae51c61..5c0c95628f2f
On Wed, 30 Aug 2017, Himanshu Jha wrote:
> kfree on NULL pointer is a no-op and therefore checking is redundant.
IMO the code has more clarity as it is.
BR,
Jani.
>
> Signed-off-by: Himanshu Jha
> ---
> drivers/gpu/drm/i915/intel_opregion.c | 6 ++
> 1 file changed, 2 insertions(+), 4 del
On 8/31/2017 1:58 AM, Andrew Morton wrote:
On Wed, 30 Aug 2017 13:02:22 +0530 Prakash Gupta wrote:
The stacktraces always begin as follows:
[] save_stack_trace_tsk+0x0/0x98
[] save_stack_trace+0x24/0x28
...
This is because the stack trace code includes the stack frames for itself.
Th
Hi all,
Since this is a blocker bug found on SGI UV system and only happen on
SGI UV system, and expert from HPE SGI UV dev team, Mike Travis sent
private mail to me saying that I can add his Acked-by to this patchset
if repost, I will repost with updated patch log. Currently without this
fix, SGI
Hi,
On Mon, Aug 28, 2017 at 1:41 PM, Andi Kleen wrote:
>> So I think we are good to go. to capture multiplexing scaling factor
>> when sampling simply use the S
>> modifier.
>> But to my surprise, newer kernels are not happy with the cmdline:
>> $ perf record -e cycles:S noploop 1
>> Error:
>>
On Wed, 2017-08-30 at 17:57 +0300, David Weinehall wrote:
> On Tue, Aug 22, 2017 at 10:37:29AM +0300, Luca Coelho wrote:
> > From: Luca Coelho
> >
> > Work queues cannot be allocated when a mutex is held because the mutex
> > may be in use and that would make it sleep. Doing so generates the
> >
To provide a very smooth service, bfq starts to serve a bfq_queue
only if the queue is 'eligible', i.e., if the same queue would
have started to be served in the ideal, perfectly fair system that
bfq simulates internally. This is obtained by associating each
queue with a virtual start time, and by
If the function bfq_update_next_in_service is invoked as a consequence
of the activation or requeueing of an entity, say E, then it doesn't
invoke bfq_lookup_next_entity to get the next-in-service entity. In
contrast, it follows a shorter path: if E happens to be eligible (see
commit "bfq-sq-mq: ma
If the function bfq_update_next_in_service is invoked as a consequence
of the activation or requeueing of an entity, say E, and finds out
that E belongs to a higher-priority class than that of the current
next-in-service entity, then it sets next_in_service directly to
E. But this may lead to anoma
Hi,
while testing the read-write unfairness issues reported by Mel, I
found BFQ failing to guarantee good responsiveness against heavy
random sync writes in the background, i.e., multiple writers doing
random writes and systematic fdatasync [1]. The failure was caused by
three related bugs, because
On 30/08/17 16:04, Ritesh Harjani wrote:
> Without this patch the CQHCI registers are getting reset
> again.
>
> Signed-off-by: Ritesh Harjani
> ---
> drivers/mmc/host/cqhci.c | 7 +++
> 1 file changed, 3 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/mmc/host/cqhci.c b/drivers/mmc/
On Tue, Aug 29, 2017 at 03:07:08PM +0200, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Mon, Feb 20, 2017 at 10:48 PM, Linux Kernel Mailing List
> wrote:
> > Web:
> > https://git.kernel.org/torvalds/c/bc88c10d7e6900916f5e1ba3829d66a9de92b633
> > Commit: bc88c10d7e6900916f5e1ba3829d66a9d
Here, prototype of thermal_zone_device_register is not matching
with static inline thermal_zone_device_register. One is using
const thermal_zone_params. Other is using non-const.
Signed-off-by: Arvind Yadav
---
include/linux/thermal.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff -
On Wed, Aug 30, 2017 at 11:41 PM, Tony Lindgren wrote:
> Hi Timur, Linus & Grygorii,
>
> Looks like commit 108d23e322a2 ("gpiolib: request the gpio before
> querying its direction") caused a regression on at least pandaboard
> es with booting hanging shortly after gpio init.
>
> It seems to be th
On Thu, Aug 31, 2017 at 12:53 AM, Andy Shevchenko
wrote:
> On Sat, Aug 19, 2017 at 11:22 AM, Bhumika Goyal wrote:
>> Make these const as they are only stored in the type field of a device
>> structure, which is const.
>> Done using Coccinelle.
>>
>
> Please, stop spamming so many people and MLs w
Add CPU idle state nodes to enable C1/C2 idle states.
Signed-off-by: James Liao
---
This patch bases on latest Matthias v4.13-next/dts64 branch [1],
add CPU idle states for MT2712.
[1] https://github.com/mbgg/linux-mediatek.git
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 25 +++
On 08/22, Bhumika Goyal wrote:
> Make this const as it is only stored in the const field of a
> clk_init_data structure.
>
> Signed-off-by: Bhumika Goyal
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On 08/25, Eugeniy Paltsev wrote:
> HSDK board manages its clocks using various PLLs. These PLL have same
> dividers and corresponding control registers mapped to different addresses.
> So we add one common driver for such PLLs.
>
> Each PLL on HSDK board consists of three dividers: IDIV, FBDIV and
On Tue 29-08-17 13:28:23, Michal Hocko wrote:
> On Tue 29-08-17 20:20:39, Tetsuo Handa wrote:
> > On 2017/08/29 7:33, Andrew Morton wrote:
> > > On Mon, 28 Aug 2017 11:33:41 +0200 Michal Hocko wrote:
> > >
> > >> drain_all_pages backs off when called from a kworker context since
> > >> 0ccce3b924
On 08/28, Arvind Yadav wrote:
> clk_div_table are not supposed to change at runtime. All functions
> working with clk_div_table provided by work
> with const clk_div_table. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
> ---
Applied to clk-next
--
Qualcomm Innovation
On 08/28, Arvind Yadav wrote:
> clk_div_table are not supposed to change at runtime. All functions
> working with clk_div_table provided by work
> with const clk_div_table. So mark the non-const structs as const.
>
> Signed-off-by: Arvind Yadav
> ---
Applied to clk-next
--
Qualcomm Innovation
On 08/28, Kunihiko Hayashi wrote:
> Add clock control for ethernet controller on Pro4, PXs2, LD11 and LD20.
>
> Signed-off-by: Kunihiko Hayashi
> ---
Applied to clk-next
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
On Wed 30-08-17 19:49:04, Andrea Arcangeli wrote:
> Hello Michal,
>
> On Wed, Aug 30, 2017 at 10:46:00AM +0200, Michal Hocko wrote:
> > +* TODO: we really want to get rid of this ugly hack and make sure that
> > +* notifiers cannot block for unbounded amount of time and add
> > +* mmu_
On 08/28, Arvind Yadav wrote:
> clk_ops are not supposed to change at runtime. All functions
> working with clk_ops provided by work
> with const clk_ops. So mark the non-const clk_ops as const.
>
> Here, Function "clk_reg_prcmu" is used to initialized clk_init_data.
> clk_init_data is working wi
On 08/28, Arvind Yadav wrote:
> clk_ops are not supposed to change at runtime. All functions
> working with clk_ops provided by work
> with const clk_ops. So mark the non-const clk_ops as const.
>
> Here, Function "clk_reg_sysctrl" is used to initialized clk_init_data.
> clk_init_data is working
On 08/28, Arvind Yadav wrote:
> clk_ops are not supposed to change at runtime. All functions
> working with clk_ops provided by work
> with const clk_ops. So mark the non-const clk_ops as const.
>
> Here, Function "clk_reg_prcc" is used to initialized clk_init_data.
> clk_init_data is working wit
Add handling of IPV6_PKTOPTIONS to dccp_v6_do_rcv() in net/dccp/ipv6.c,
similar
to the handling in net/ipv6/tcp_ipv6.c
Signed-off-by: Andrii Vladyka
---
diff --git a/net/dccp/ipv6.c b/net/dccp/ipv6.c
index 1b58eac..35c2edb 100644
--- a/net/dccp/ipv6.c
+++ b/net/dccp/ipv6.c
@@ -16,6 +16,7 @@
#
I'll fix and re-send. Thanks.
On 8/31/2017 8:16 AM, David Miller wrote:
From: Andrii Vladyka
Date: Wed, 30 Aug 2017 09:04:35 +0300
+ if (opt_skb)
Trailing whitespace.
@@ -653,6 +647,36 @@ static int dccp_v6_do_rcv(struct sock *sk, struct sk_buff
*skb)
Hi all,
After merging the xen-tip tree, today's linux-next build (x86_64
allmodconfig) failed like this:
arch/x86/xen/xen-asm_64.o: In function `xen_trace_page_fault':
(.text+0x174): undefined reference to `trace_page_fault'
Caused by commit
ad5b8c4ba323 ("xen: get rid of paravirt op adjust_e
On Thu 31-08-17 10:42:41, Joonsoo Kim wrote:
> On Tue, Aug 29, 2017 at 09:33:44AM +0900, Joonsoo Kim wrote:
> > On Mon, Aug 28, 2017 at 03:08:29PM +0200, Michal Hocko wrote:
> > > On Mon 28-08-17 13:29:29, Vlastimil Babka wrote:
> > > > On 08/28/2017 03:11 AM, js1...@gmail.com wrote:
> > > > > From
On Thu, 2017-08-31 at 06:36 +0200, Greg Kroah-Hartman wrote:
> On Wed, Aug 30, 2017 at 11:10:14PM +0300, Pasi Kärkkäinen wrote:
> > Hello everyone,
> >
> > Recently Nathan March reported on centos-virt list he's getting frequent
> > Linux kernel crashes with Linux 4.9 LTS kernel because of the mis
On 08/30/2017 05:37 PM, Maxime Ripard wrote:
Hi,
On Mon, Aug 28, 2017 at 09:32:42AM +0300, Stefan Mavrodiev wrote:
From revision J the board uses new phy chip LAN8710. Compared
with RTL8201, RA17 pin is TXERR. It has pullup which causes phy
not to work. To fix this PA17 is muxed with GMAC func
Looking to lose weight fast in a healthy way?
While it may be very tempting to turn to diet aid solutions that promise
awesome weight loss, it's also important to be cautious about your health.
Recent data show that most diet medicines, drinks and "organic" formulas are
capable of causing a range
From: Andrii Vladyka
Date: Wed, 30 Aug 2017 09:04:35 +0300
> + if (opt_skb)
Trailing whitespace.
> @@ -653,6 +647,36 @@ static int dccp_v6_do_rcv(struct sock *sk, struct
> sk_buff *skb)
> __kfree_skb(opt_skb);
> kfree_skb(skb);
> return 0
>From: Rob Herring [mailto:r...@kernel.org]
>Subject: Re: [PATCH] arm64: dts: Add support for NXP's LX2160A SoC
>
>On Fri, Aug 18, 2017 at 04:25:36PM +0530, Sriram Dash wrote:
>> The QorIQ LX2160A processor is built in the 16FFC process on the
>> Layerscape architecture combining sixteen ARM A72 pr
On Wed, Aug 30, 2017 at 12:30:52PM +0100, Suzuki K Poulose wrote:
> commit 6c0d706b563af732adb094c5bf807437e8963e84 upstream.
>
> In kvm_free_stage2_pgd() we check the stage2 PGD before holding
> the lock and proceed to take the lock if it is valid. And we unmap
> the page tables, followed by rele
Hi Martin,
Replied inline.
Thanks,
Suganath Prabu S
On Thu, Aug 31, 2017 at 8:35 AM, Martin K. Petersen
wrote:
>
> Hi Suganath,
>
>> Theoretically we want to use h/w capability (to translate IEEE to PRP)
>> for smaller IO size to leverage h/w capability.
>
> Nobody says we have to use the capabi
On Thu, Aug 31, 2017 at 6:51 AM, Xiong Zhou wrote:
> hi,
>
> This happens on 4.13.0-rc7+ to commit 42ff72c
Don't understand. Is this a regression? from which commit?
>
> After firing up the stress, touch a file in monitoring directory could
> hang like forever.
>
> Pretty easy to hit.
So are ru
Add description for optional device tree property
'prsnt-gpios' for PCI hotplug feature.
Signed-off-by: Oza Pawandeep
Reviewed-by: Ray Jui
Acked-by: Rob Herring
diff --git a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt
b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt
i
Host drivers have the requirement of implementing PCI hotplug
based on the how their SOC supports it.
Couple of properties have been added. the one to enable
the hotplug feature itself, and the other caters to
the PCI hotplug implementation with the use of gpios.
Signed-off-by: Oza Pawandeep
Ack
This patch implements PCI hotplug support for iproc family chipsets.
iproc based SOC (e.g. Stingray) does not have hotplug controller
integrated.
Hence, standard PCI hotplug framework hooks can-not be used.
e.g. controlled power up/down of slot.
The mechanism, for e.g. Stingray has adopted for PC
These patches bring in PCI hotplug support for iproc family chipsets.
It includes DT binding documentation and, the implementation in
iproc pcie RC driver.
Changes since v5:
[RESEND]
Changes since v4:
Rebased to pci-next
Added; Acked-by: Rob Herring
Changes since v3:
Resend. just to be in sync
On 08/30/2017 08:42 AM, Gustavo A. R. Silva wrote:
Refactor code in order to avoid identical code for different branches.
This issue was detected with the help of Coccinelle.
Addresses-Coverity-ID: 1226788
Signed-off-by: Gustavo A. R. Silva
---
This issue was reported by Coverity and it was te
qcom_mdt_load function loads the mdt type firmware and
initialises the secure memory as well. Make the initialisation only
when requested by the caller, so that the function can be used
by self-authenticating remoteproc as well.
Signed-off-by: Sricharan R
---
drivers/soc/qcom/mdt_loader.c
IPQ8074 has an integrated Hexagon dsp core q6v5 and a wireless lan
(Lithium) IP. An mdt type single image format is used for the
firmware. So the mdt_load function can be directly used to load
the firmware. Also add the relevant resets required for this core.
Signed-off-by: Sricharan R
---
.../d
q6v5-wcss core's start function is mostly common
with the q6v5 of msm8996. So reuse that and add
the stop function.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 212 +
1 file changed, 212 insertions(+)
diff --git a/drivers/remoteproc/qc
Most of the q6v5-pil start function is same for the q6v5-wcss rproc
that will be added later. So split and move out the common pieces
so that the same code can be reused.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 166 -
1 file changed
Export rproc_elf_get_boot_addr so that it can be
used by any remoteproc to get the bootaddr of the
elf type firmware images. This is used in the
subsequent patch by the q6v5 based remoteproc
while loading its elf based mdt type image.
Signed-off-by: Sricharan R
---
drivers/remoteproc/remoteproc_
Instead of directly assigning reset, fw and rproc ops, put them
in to of_match data and get from that. Currently same ops
are used for all compatibles, but that will change when we add
q6v5-wcss support.
Signed-off-by: Sricharan R
---
drivers/remoteproc/qcom_q6v5_pil.c | 38 +
IPQ8074 has an integrated Hexagon dsp core Q6v5 and a wireless lan
(Lithium) IP. This series adds the remoteproc driver to reset, load
and boot Q6 firmware.
The first patch is to make the mdt_loader authenticate
the firmware only if required, so that the code can be reused for
self-authenticating
David Miller writes:
> From: Kalle Valo
> Date: Wed, 30 Aug 2017 20:31:31 +0300
>
>> AFAICS the bug was introduced by 9df86e2e702c6 back in 2010. If the bug
>> has been there for 7 years so waiting for a few more weeks should not
>> hurt.
>
> As a maintainer you have a right to handle bug fixing
This patch implements PCI hotplug support for iproc family chipsets.
iproc based SOC (e.g. Stingray) does not have hotplug controller
integrated.
Hence, standard PCI hotplug framework hooks can-not be used.
e.g. controlled power up/down of slot.
The mechanism, for e.g. Stingray has adopted for PC
Add description for optional device tree property
'prsnt-gpios' for PCI hotplug feature.
Signed-off-by: Oza Pawandeep
Reviewed-by: Ray Jui
Acked-by: Rob Herring
diff --git a/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt
b/Documentation/devicetree/bindings/pci/brcm,iproc-pcie.txt
i
Host drivers have the requirement of implementing PCI hotplug
based on the how their SOC supports it.
Couple of properties have been added. the one to enable
the hotplug feature itself, and the other caters to
the PCI hotplug implementation with the use of gpios.
Signed-off-by: Oza Pawandeep
Ack
These patches bring in PCI hotplug support for iproc family chipsets.
It includes DT binding documentation and, the implementation in
iproc pcie RC driver.
Changes since v3:
Rebased to pci-next
Added; Acked-by: Rob Herring
Changes since v3:
Resend. just to be in sync previous in-flight patches.
On 08/30/2017 12:04 PM, Gustavo A. R. Silva wrote:
Refactor code in order to avoid identical code for different branches.
Addresses-Coverity-ID: 1248728
Signed-off-by: Gustavo A. R. Silva
According to Realtek, this change is OK.
Acked-by: Larry Finger
Thanks,
Larry
---
This issue was re
On Wed, Aug 30, 2017 at 04:39:42PM -0700, H. Peter Anvin wrote:
> On 08/30/17 13:14, Josh Poimboeuf wrote:
> > On Wed, Aug 30, 2017 at 12:23:24PM -0700, H. Peter Anvin wrote:
> >> On 08/30/17 02:43, tip-bot for Josh Poimboeuf wrote:
> >>>
> >>> Those warnings are caused by an unusual GCC non-optimi
If 'clk_prepare_enable()' fails, we must release some resources before
returning. Add a new label in the existing error handling path and 'goto'
there.
Fixes: 260ea95cc027 ("ASoC: atmel: ac97c: Handle return value of
clk_prepare_enable.")
Signed-off-by: Christophe JAILLET
---
sound/atmel/ac97c.
On Wed, 2017-08-30 at 21:10 -0700, Kees Cook wrote:
> On Wed, Aug 30, 2017 at 9:01 PM, Kees Cook wrote:
> > On Wed, Aug 30, 2017 at 8:12 PM, Mike Galbraith wrote:
> >> On Wed, 2017-08-30 at 19:27 -0700, Kees Cook wrote:
> >>
> >>> Interesting! Can you try with 633547973ffc3 ("net: convert
> >>> s
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in:
arch/x86/xen/enlighten_pv.c
between commit:
64b163fab684 ("x86/idt: Unify gate_struct handling for 32/64-bit kernels")
from the tip tree and commit:
ad5b8c4ba323 ("xen: get rid of paravirt op adjust_exception_frame"
On Wed, Aug 30, 2017 at 11:10:14PM +0300, Pasi Kärkkäinen wrote:
> Hello everyone,
>
> Recently Nathan March reported on centos-virt list he's getting frequent
> Linux kernel crashes with Linux 4.9 LTS kernel because of the missing patch
> "tty: Fix ldisc crash on reopened tty".
Crashes with "n
On Tue, Aug 29, 2017 at 11:32:58PM +0200, Ondrej Zary wrote:
> On Tuesday 29 August 2017 01:42:08 David Miller wrote:
> > From: Greg Kroah-Hartman
> > Date: Sun, 27 Aug 2017 17:03:30 +0200
> >
> > > The IRDA code has long been obsolete and broken. So, to keep people
> > > from trying to use it, a
On Wed, Aug 30, 2017 at 12:46:38PM -0700, Sherry Yang wrote:
> On Tue, Aug 29, 2017 at 11:07 PM, Greg Kroah-Hartman
> wrote:
> > On Tue, Aug 29, 2017 at 05:46:57PM -0700, Sherry Yang wrote:
> >> Use helper functions buffer_next and buffer_prev instead
> >> of list_entry to get the next and previou
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in:
arch/x86/include/asm/traps.h
between commit:
11a7ffb01703 ("x86/traps: Simplify pagefault tracing logic")
from the tip tree and commit:
ad5b8c4ba323 ("xen: get rid of paravirt op adjust_exception_frame")
from the x
Removed printk statements for debugging. The same information can be
acquired via ftrace, so these print statements are uneccessary.
Signed-off-by: Jonathan Whitaker
---
Changes in v2:
- Wrapped the changelog text to 72 columns.
- Fixed the commit subject to be more clear.
Changes in v3:
On 08/30/2017 06:28 PM, Jakub Kicinski wrote:
> Hi!
>
> I'm seeing a lot of kmemleak reports like this on 4.13.0-rc6:
>
yep, thanks for the report. I have seen this one and am still trying
to chase it down.
> unreferenced object 0x88045e62ab08 (size 1024):
> comm "apparmor_parser", pid 802
On Tue, 2017-08-29 at 18:09 +0200, Borislav Petkov wrote:
> On Fri, Aug 18, 2017 at 05:27:46PM -0700, Ricardo Neri wrote:
> > Even though memory addresses are unsigned, the operands used to compute the
> > effective address do have a sign. This is true for ModRM.rm, SIB.base,
> > SIB.index as well
On Wed, Aug 30, 2017 at 01:55:36PM -0500, Christopher Bostic wrote:
> Add ability to clear logged faults via sysfs.
>
I am not in favor of such chip specific commands, in this case for several
reasons (besides it being a non-standard attribute).
The logged faults are not read or used by the drive
On Wed, Aug 30, 2017 at 9:01 PM, Kees Cook wrote:
> On Wed, Aug 30, 2017 at 8:12 PM, Mike Galbraith wrote:
>> On Wed, 2017-08-30 at 19:27 -0700, Kees Cook wrote:
>>
>>> Interesting! Can you try with 633547973ffc3 ("net: convert
>>> sk_buff.users from atomic_t to refcount_t") reverted? I'll see if
Hi,
I have seen a behavior using kernel threads that I do not understand. I
would like to know if there is a real issue within the kernel or if I am
expecting something that is not possible. I have donned the flame suit.
I would expect the kernel module listed below to load successfully and
run,
On Fri, 2017-08-25 at 19:41 +0200, Borislav Petkov wrote:
Thanks Borislav for your feedback!
> On Fri, Aug 18, 2017 at 05:27:43PM -0700, Ricardo Neri wrote:
> > Both head_32.S and head_64.S utilize the same value to initialize the
> > control register CR0. Also, other parts of the kernel might wa
On Wed, Aug 30, 2017 at 8:12 PM, Mike Galbraith wrote:
> On Wed, 2017-08-30 at 19:27 -0700, Kees Cook wrote:
>
>> Interesting! Can you try with 633547973ffc3 ("net: convert
>> sk_buff.users from atomic_t to refcount_t") reverted? I'll see if
>> running haveged will help me trigger this on my syste
On August 30, 2017 8:38:46 PM PDT, Samuel Mendoza-Jonas
wrote:
>Patch "net/ncsi: Configure VLAN tag filter" defined two new callback
>functions in include/net/ncsi.h, but neglected the !CONFIG_NET_NCSI
>case. This can cause a build error if these are referenced elsewhere
>without NCSI enabled, fo
hi,
This happens on 4.13.0-rc7+ to commit 42ff72c
After firing up the stress, touch a file in monitoring directory could
hang like forever.
Pretty easy to hit.
Thanks,
Xiong
[ 492.060879] INFO: task touch:2259 blocked for more than 120 seconds.
[ 492.093497] Not tainted 4.13.0-rc7-mast
Hi all,
Today's linux-next merge of the tip tree got a conflict in:
drivers/net/ethernet/cavium/liquidio/lio_main.c
between commit:
d1d97ee6e3a8 ("liquidio: moved liquidio_napi_drv_callback to lio_core.c")
from the net-next tree and commit:
966a967116e6 ("smp: Avoid using two cache line
Patch "net/ncsi: Configure VLAN tag filter" defined two new callback
functions in include/net/ncsi.h, but neglected the !CONFIG_NET_NCSI
case. This can cause a build error if these are referenced elsewhere
without NCSI enabled, for example in ftgmac100:
>>> ERROR: "ncsi_vlan_rx_kill_vid" [drivers/
On Wed, 2017-08-30 at 19:27 -0700, Kees Cook wrote:
> Interesting! Can you try with 633547973ffc3 ("net: convert
> sk_buff.users from atomic_t to refcount_t") reverted? I'll see if
> running haveged will help me trigger this on my system...
With that (plus 230cd1279d001 fix to it) reverted, vbox
On 30 August 2017 at 22:45, Stephen Rothwell wrote:
> Hi Jassi,
>
> Commits
>
> da91001cab90 ("mailbox: bcm-flexrm-mailbox: Set IRQ affinity hint for FlexRM
> ring IRQs")
> 6bee3ba26d4d ("mailbox: bcm-flexrm-mailbox: Add debugfs support")
> 73c28265c82b ("mailbox: bcm-flexrm-mailbox: Fix mask use
When cramfs_physmem is used then we have the opportunity to map files
directly from ROM, directly into user space, saving on RAM usage.
This gives us Execute-In-Place (XIP) support.
For a file to be mmap()-able, the map area has to correspond to a range
of uncompressed and contiguous blocks, and i
Small embedded systems typically execute the kernel code in place (XIP)
directly from flash to save on precious RAM usage. This adds the ability
to consume filesystem data directly from flash to the cramfs filesystem
as well. Cramfs is particularly well suited to this feature as it is
very simple a
Update documentation, pointer to latest tools, appoint myself as
maintainer. Given it's been unloved for so long, I don't expect anyone
will protest.
Signed-off-by: Nicolas Pitre
Tested-by: Chris Brandt
---
Documentation/filesystems/cramfs.txt | 42
MAINTAIN
Two new capabilities are introduced here:
- The ability to store some blocks uncompressed.
- The ability to locate blocks anywhere.
Those capabilities can be used independently, but the combination
opens the possibility for execute-in-place (XIP) of program text segments
that must remain uncompr
This series is also available based on v4.13-rc4 via git here:
http://git.linaro.org/people/nicolas.pitre/linux xipcramfs
Please consider this an official merge request.
This series brings a nice refresh to the cramfs filesystem, adding the
following capabilities:
- Direct memory access, bypa
Signed-off-by: Nicolas Pitre
Tested-by: Chris Brandt
---
init/do_mounts.c | 8
1 file changed, 8 insertions(+)
diff --git a/init/do_mounts.c b/init/do_mounts.c
index c2de5104aa..43b5817f60 100644
--- a/init/do_mounts.c
+++ b/init/do_mounts.c
@@ -556,6 +556,14 @@ void __init prepare_nam
1 - 100 of 843 matches
Mail list logo
