On 7/11/2018 10:00 AM, Peter Zijlstra wrote:
> On Wed, Jul 11, 2018 at 04:57:51PM +0100, Will Deacon wrote:
>
>> It might be simple to model, but I worry this weakens our locking
>> implementations to a point where they will not be understood by the average
>> kernel developer. As I've said before
On Wed, Jul 11, 2018 at 10:43 AM, Dave Hansen wrote:
> On 07/11/2018 10:29 AM, H.J. Lu wrote:
>>> I have seen it on machines with various amounts of cores and RAMs.
>>> It triggers the fastest on 8 cores with 6GB RAM reliably.
>> Here is the first kernel message.
>
> Does it trigger better with mo
On Mon, Jul 09, 2018 at 05:48:54PM -0400, Steven Rostedt wrote:
> From: Steven Rostedt (VMware)
>
> It is unwise to take spin locks from the handlers of trace events.
> Mainly, because they can introduce lockups, because it introduces locks
> in places that are normally not tested. Worse yet, bec
On Wed, Jul 11, 2018 at 06:03:42PM +0100, David Woodhouse wrote:
> On Wed, 2018-07-11 at 09:49 -0700, Paul E. McKenney wrote:
> > And here is an updated v4.15 patch with Marius's Reported-by and David's
> > fix to my lost exclamation point.
>
> Thanks. Are you sending the original version of that
On Mon, Jul 09, 2018 at 11:12:47AM -0500, Gustavo A. R. Silva wrote:
> Make use of the swap macro and remove some unnecessary variables.
> This makes the code easier to read and maintain. Also, reduces the
> stack usage.
>
> This code was detected with the help of Coccinelle.
>
> Signed-off-by: G
On Mon, Jul 09, 2018 at 04:02:59PM -0500, Gustavo A. R. Silva wrote:
> Make use of the swap macro and remove some unnecessary variables.
> This makes the code easier to read and maintain. Also, reduces the
> stack usage.
>
> This code was detected with the help of Coccinelle.
>
> Signed-off-by: G
On 07/11/2018 10:29 AM, H.J. Lu wrote:
>> I have seen it on machines with various amounts of cores and RAMs.
>> It triggers the fastest on 8 cores with 6GB RAM reliably.
> Here is the first kernel message.
Does it trigger better with more RAM or less?
On Wed, Jul 11, 2018 at 06:49:46AM +0100, Mark Rutland wrote:
> > > Dave pointed out that it would be useful to be able to opt-in to full
> > > checks
> > > regardless of CONFIG_REFCOUNT_FULL, so that we can simplify callsites
> > > where we
> > > always want checks. I've spotted a few of these i
When we switched from doing rdmsr() to reading FS/GS base values from
current->thread we completely forgot about legacy 32-bit userspaces which
we still support in KVM (why?). task->thread.{fsbase,gsbase} are only
synced for 64-bit processes, calling save_fsgs_for_kvm() and using
its result from cu
On Wed, Jul 11, 2018 at 10:29 AM, H.J. Lu wrote:
> On Wed, Jul 11, 2018 at 9:53 AM, H.J. Lu wrote:
>> On Wed, Jul 11, 2018 at 9:49 AM, Dave Hansen wrote:
>>> On 07/11/2018 09:29 AM, H.J. Lu wrote:
>> # It takes about 3 hour to bootstrap x86-64 GCC and 3 hour to run tests,
>> TIMEOUT=480
On Wed, 11 Jul 2018, David Laight wrote:
> > From: Alan Stern
> > Sent: 10 July 2018 19:18
> > More than one kernel developer has expressed the opinion that the LKMM
> > should enforce ordering of writes by locking. In other words, given
> > the following code:
> >
> > WRITE_ONCE(x, 1);
> > spin_u
Hello, Sebastian.
On Wed, Jul 11, 2018 at 01:05:13PM +0200, Sebastian Andrzej Siewior wrote:
> > > We at least used to do this in the kernel - manipulating irqsafe locks
> > > with spin_lock/unlock() if the irq state is known, whether enabled or
> > > disabled, and ISTR lockdep being smart enough
On Wed, 11 Jul 2018, Linus Torvalds wrote:
> It's the testing that worries me most. Pretty much no developers run
> 32-bit any more, and I'd be most worried about the odd interactions that
> might be hw-specific. Some crazy EFI mapping setup or the similar odd
> case that simply requires a part
Attn: Sir / Ma
We write to know if you authorized anyone to claim your funds with us?
However, we shall proceed if we do not hear from you within the next two
working days from today Please clarify with us.
Therefore, if you must respond now, kindly reconfirm your ID or any utility
receipt
On Wed, 2018-07-11 at 19:07 +0200, Geert Uytterhoeven wrote:
> Hi Joe,
Rehi Geert.
> On Wed, Jul 11, 2018 at 6:20 PM Joe Perches wrote:
> > On Wed, 2018-07-11 at 17:10 +0200, Geert Uytterhoeven wrote:
> > > Print a warning if none of the Signed-off-by lines cover the patch
> > > author.
> > >
>
On 11/07/18 11:32, Colin King wrote:
From: Colin Ian King
Variable segpos is being assigned but is never used hence it is redundant
and can be removed.
Cleans up clang warning:
warning: variable 'segpos' set but not used [-Wunused-but-set-variable]
Signed-off-by: Colin Ian King
---
drivers
On Wed, 2018-07-11 at 09:53 -0700, Jae Hyun Yoo wrote:
> On 7/10/2018 10:42 PM, Brendan Higgins wrote:
> > On Mon, Jul 2, 2018 at 2:14 PM Jae Hyun Yoo
> > wrote:
> > > There are some log printing without a newline character. This
> > > patch adds the missing newline characters.
[]
> > > diff --gi
On 7/11/18 4:53 AM, Michal Hocko wrote:
On Wed 11-07-18 14:13:12, Kirill A. Shutemov wrote:
On Wed, Jul 11, 2018 at 12:33:12PM +0200, Michal Hocko wrote:
this is not a small change for something that could be achieved
from the userspace trivially (just call madvise before munmap - library
ca
Hi Joe,
On Wed, Jul 11, 2018 at 6:20 PM Joe Perches wrote:
> On Wed, 2018-07-11 at 17:10 +0200, Geert Uytterhoeven wrote:
> > Print a warning if none of the Signed-off-by lines cover the patch
> > author.
> >
> > Non-ASCII quoted printable encoding in From: headers and (lack of)
> > double quotes
> On Jul 11, 2018, at 12:22 AM, David Howells wrote:
>
> Andy Lutomirski wrote:
>
>>> sfd = fsopen("ext4", FSOPEN_CLOEXEC);
>>> write(sfd, "s /dev/sdb1"); // note I'm ignoring write's length arg
>>
>> Imagine some malicious program passes sfd as stdout to a setuid
>> program. That program get
On 7/11/18 4:10 AM, Kirill A. Shutemov wrote:
On Wed, Jul 11, 2018 at 07:34:06AM +0800, Yang Shi wrote:
Background:
Recently, when we ran some vm scalability tests on machines with large memory,
we ran into a couple of mmap_sem scalability issues when unmapping large memory
space, please refe
On Wed, 2018-07-11 at 09:49 -0700, Paul E. McKenney wrote:
> And here is an updated v4.15 patch with Marius's Reported-by and David's
> fix to my lost exclamation point.
Thanks. Are you sending the original version of that to Linus? It'd be
useful to have the commit ID so that we can watch for it
On Mon, Jul 9, 2018 at 10:58 PM, MyungJoo Ham wrote:
>> + dev freq maintainters.
>>
>> On Mon, Jul 9, 2018 at 3:37 AM, noman pouigt wrote:
>> > folks,
>> >
>> > I am trying to figure out the relationship between PM QOS
>> > with devfreq framework. I see this thread[1] where MyungJoo
>> > talks ab
On Wed, Jul 11, 2018 at 04:57:51PM +0100, Will Deacon wrote:
> It might be simple to model, but I worry this weakens our locking
> implementations to a point where they will not be understood by the average
> kernel developer. As I've said before, I would prefer "full" RCsc locking,
Another vote
On Wed, Jul 11, 2018 at 10:11 PM, A.s. Dong wrote:
> Hi Jassi,
>
>> -Original Message-
>> From: Jassi Brar [mailto:jassisinghb...@gmail.com]
>> Sent: Thursday, July 12, 2018 12:32 AM
>> To: A.s. Dong
>> Cc: Sascha Hauer ; linux-arm-
>> ker...@lists.infradead.org; donga...@gmail.com; linux
Thanks, Michael. In which branch should I fix these now that the changes have
been
merged with the char-misc-next branch?
Comments inline.
> -Original Message-
> From: Michael Kelley (EOSG)
> Sent: Tuesday, July 10, 2018 6:05 PM
> To: KY Srinivasan ; gre...@linuxfoundation.org; linux-
>
On 7/11/18 3:33 AM, Michal Hocko wrote:
On Wed 11-07-18 07:34:06, Yang Shi wrote:
Background:
Recently, when we ran some vm scalability tests on machines with large memory,
we ran into a couple of mmap_sem scalability issues when unmapping large memory
space, please refer to https://lkml.org/
On 7/10/2018 10:47 PM, Brendan Higgins wrote:
On Mon, Jul 2, 2018 at 2:20 PM Jae Hyun Yoo
wrote:
This patch changes the order of enum aspeed_i2c_master_state and
enum aspeed_i2c_slave_state defines to make their initial value to
ASPEED_I2C_MASTER_INACTIVE and ASPEED_I2C_SLAVE_STOP respectively
On 7/10/2018 10:42 PM, Brendan Higgins wrote:
On Mon, Jul 2, 2018 at 2:14 PM Jae Hyun Yoo
wrote:
There are some log printing without a newline character. This
patch adds the missing newline characters.
Signed-off-by: Jae Hyun Yoo
---
drivers/i2c/busses/i2c-aspeed.c | 18 +-
On Wed, Jul 11, 2018 at 9:49 AM, Dave Hansen wrote:
> On 07/11/2018 09:29 AM, H.J. Lu wrote:
# It takes about 3 hour to bootstrap x86-64 GCC and 3 hour to run tests,
TIMEOUT=480
# Run it every hour,
30 * * * * /export/gnu/import/git/gcc-test-x32/gcc-build -mx32
--with-pic
Hi Bjorn,
On 7/11/2018 6:11 AM, Bjorn Helgaas wrote:
On Mon, Jun 11, 2018 at 05:21:03PM -0700, Ray Jui wrote:
Activate PAXC bridge quirk for more PAXC based PCIe root complex with
the following PCIe device ID:
0xd750, 0xd802, 0xd804
Signed-off-by: Ray Jui
Because this quirk_paxc_bridge() me
On 11/07/18 10:32 AM, Serge Semin wrote:
> @@ -1320,7 +1321,9 @@ static int idt_ntb_peer_mw_set_trans(struct ntb_dev
> *ntb, int pidx, int widx,
> idt_nt_write(ndev, bar->ltbase, (u32)addr);
> idt_nt_write(ndev, bar->utbase, (u32)(addr >> 32));
> /* Set
On 07/11/2018 09:29 AM, H.J. Lu wrote:
>>> # It takes about 3 hour to bootstrap x86-64 GCC and 3 hour to run tests,
>>> TIMEOUT=480
>>> # Run it every hour,
>>> 30 * * * * /export/gnu/import/git/gcc-test-x32/gcc-build -mx32
>>> --with-pic > /dev/null 2>&1
>> Oh, fun, one of those.
>>
>> How long do
Hello,
syzbot found the following crash on:
HEAD commit:98be45067040 Add linux-next specific files for 20180711
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=12496ac240
kernel config: https://syzkaller.appspot.com/x/.config?x=3f3b3673fec35d01
On 07/11/2018 05:48 AM, Michal Hocko wrote:
> On Wed 11-07-18 14:47:11, Michal Hocko wrote:
>> On Tue 10-07-18 11:49:03, Cannon Matthews wrote:
>>> When using 1GiB pages during early boot, use the new
>>> memblock_virt_alloc_try_nid_raw() function to allocate memory without
>>> zeroing it. Zeroing
On Wed, Jul 11, 2018 at 07:43:03AM -0700, Paul E. McKenney wrote:
> On Wed, Jul 11, 2018 at 03:23:45PM +0100, David Woodhouse wrote:
> >
> >
> > On Mon, 2018-07-09 at 15:08 -0700, Paul E. McKenney wrote:
> > > index f9c0ca2ccf0c..3350ece366ab 100644
> > > --- a/kernel/rcu/tree.c
> > > +++ b/kerne
- On Jul 11, 2018, at 11:26 AM, rostedt rost...@goodmis.org wrote:
> On Wed, 11 Jul 2018 17:17:51 +0200
> Peter Zijlstra wrote:
>
>> I just read the comment that goes with that function; the order doesn't
>> matter. All we want to ensure is that the unregistration is visible to
>> either sch
Hi Jassi,
> -Original Message-
> From: Jassi Brar [mailto:jassisinghb...@gmail.com]
> Sent: Thursday, July 12, 2018 12:32 AM
> To: A.s. Dong
> Cc: Sascha Hauer ; linux-arm-
> ker...@lists.infradead.org; donga...@gmail.com; linux-
> ker...@vger.kernel.org; Oleksij Rempel ; dl-
> linux-imx
- On Jul 11, 2018, at 11:17 AM, Peter Zijlstra pet...@infradead.org wrote:
> On Wed, Jul 11, 2018 at 09:06:49AM -0400, Steven Rostedt wrote:
>> On Wed, 11 Jul 2018 14:56:47 +0200
>> Peter Zijlstra wrote:
>>
>> > On Thu, Jun 28, 2018 at 11:21:46AM -0700, Joel Fernandes wrote:
>> > > static i
On Mon 09 Jul 04:43 PDT 2018, Amit Kucheria wrote:
> We want to create common code for v2 of the TSENS IP block that is used in
> a large number of Qualcomm SoCs. "qcom,tsens-v2" should be able to handle
> most of the common functionality start with a common get_temp() function.
>
> It is also ne
Hello,
syzbot found the following crash on:
HEAD commit:98be45067040 Add linux-next specific files for 20180711
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=10de4efc40
kernel config: https://syzkaller.appspot.com/x/.config?x=3f3b3673fec35d01
On Wed, Jul 11, 2018 at 08:22:41AM +0100, David Howells wrote:
> Andy Lutomirski wrote:
>
> > >sfd = fsopen("ext4", FSOPEN_CLOEXEC);
> > >write(sfd, "s /dev/sdb1"); // note I'm ignoring write's length arg
> >
> > Imagine some malicious program passes sfd as stdout to a setuid
> > program
On 11/07/2018 15:42, Sudeep Holla wrote:
> Hi Daniel,
>
> On 11/07/18 12:36, Daniel Lezcano wrote:
>> On 11/07/2018 13:24, Sudeep Holla wrote:
>>> Currently, quite a few clockevent devices have cpumask set to
>>> cpu_all_mask which should be fine. However, cpu_possible_mask is more
>>> accurate an
On Mon 09 Jul 04:43 PDT 2018, Amit Kucheria wrote:
> SDM845 has two tsens blocks, one with 13 sensors and the other with 8
> sensors. It uses version 2 of the TSENS IP, so use the fallback property to
> allow more common code.
>
> Signed-off-by: Amit Kucheria
Reviewed-by: Bjorn Andersson
Rega
On Mon 09 Jul 04:43 PDT 2018, Amit Kucheria wrote:
> SDM845 uses v2 of the TSENS IP block but the get_temp() function
> appears to be identical across v2.x.y in code seen so far. We use the
> generic get_temp() function defined as part of ops_generic_v2.
>
> Signed-off-by: Amit Kucheria
Reviewe
On Mon 09 Jul 04:43 PDT 2018, Amit Kucheria wrote:
> The TSENS block inside the 8996 is internally classified as version 2 of
> the IP. Several other SoC families use this block and can share this code.
>
> We rename get_temp() to reflect that it can be used across the v2 family.
>
> Signed-off-
On Wed, Jul 11, 2018 at 10:43:45AM +0100, Will Deacon wrote:
> Hi Alan,
>
> On Tue, Jul 10, 2018 at 02:18:13PM -0400, Alan Stern wrote:
> > More than one kernel developer has expressed the opinion that the LKMM
> > should enforce ordering of writes by locking. In other words, given
> > the follow
Quoting Joel Stanley (2018-07-10 22:53:52)
> Hi Stephen,
>
> On 7 July 2018 at 03:55, Stephen Boyd wrote:
> > Quoting Joel Stanley (2018-06-28 16:15:40)
> >> The HPLL can be configured through a register (SCU24), however some
> >> platforms chose to configure it through the strapping settings and
On Mon 09 Jul 04:43 PDT 2018, Amit Kucheria wrote:
> We also split up the regmap address space into two, one for the TM
> registers, the other for the SROT registers. This was required to deal with
> different address offsets for the TM and SROT registers across different
> SoC families.
>
> Sinc
Quoting Shawn Guo (2018-07-11 01:43:03)
> On Fri, Jul 06, 2018 at 01:58:46PM -0700, Stephen Boyd wrote:
> > Quoting Anson Huang (2018-06-21 23:32:33)
> > > According to Reference Manual Rev.0, 06/2017,
> > > there are GPIO LPCGs defined in CCM CCGRs,
> > > add them into clock tree.
> > >
> > > Sig
On Wed, Jul 11, 2018 at 6:28 PM, A.s. Dong wrote:
> Hi Jassi,
>
>> -Original Message-
>> From: Jassi Brar [mailto:jassisinghb...@gmail.com]
>> Sent: Wednesday, July 11, 2018 6:44 PM
>> To: A.s. Dong
>> Cc: Sascha Hauer ; linux-arm-
>> ker...@lists.infradead.org; donga...@gmail.com; linux-
IDT NTB driver sets the upper limit of actual translation address
being set to the corresponding memory window. It is achieved by
BARLIMITx register initialization. Needless to say, that the register
works within PCIe bus address space.
In general CPU and PCIe address spaces are different. It mean
On Mon 09 Jul 04:43 PDT 2018, Amit Kucheria wrote:
> There are two banks of registers for v2 TSENS IPs: SROT and TM. On older
> SoCs these were contiguous, leading to DTs mapping them as one register
> address space of size 0x2000. In newer SoCs, these two banks are not
> contiguous anymore.
>
>
On Wed, Jul 11, 2018 at 9:24 AM, Dave Hansen wrote:
> On 07/11/2018 08:40 AM, H.J. Lu wrote:
>> This is a quad-core machine with HT and 6 GB RAM. The workload is
>> x32 GCC build and test with "make -j8". The bug is triggered during GCC
>> test after a couple hours. I have a script to set up my
On Wed, Jul 11, 2018 at 4:30 AM Joerg Roedel wrote:
>
> I did the load-testing again with 'perf top', the ldt_gdt
> self-test and a kernel-compile running in a loop again.
So none of the patches looked scary to me, but then, neither did
earlier versions.
It's the testing that worries me most. Pr
On 2018-06-15 22:33:47 [+0200], Jason A. Donenfeld wrote:
> On Fri, Jun 15, 2018 at 8:32 PM Andy Lutomirski wrote:
> > quite in the form you imagined. The idea that we've tossed around is
> > to restore FPU state on return to user mode. Roughly, we'd introduce
> > a new thread flag TIF_FPU_UNLOA
> It might be simple to model, but I worry this weakens our locking
> implementations to a point where they will not be understood by the average
> kernel developer. As I've said before, I would prefer "full" RCsc locking,
> but that's not the case with architectures we currently support today, so
On Mon, 2018-07-02 at 22:25 +, Yixun Lan wrote:
> From: Xingyu Chen
>
> Add the DT info for SAR ADC of the Amlogic's Meson-AXG SoC.
>
> Signed-off-by: Xingyu Chen
> Signed-off-by: Yixun Lan
> ---
> Hi kevin
> I just re-send this patch which rebased to your khilman/v4.18/integ branch
>
Fix typo for PIN_PB22 on TD function.
Signed-off-by: Claudiu Beznea
---
arch/arm/boot/dts/sama5d2-pinfunc.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/arm/boot/dts/sama5d2-pinfunc.h
b/arch/arm/boot/dts/sama5d2-pinfunc.h
index e57191fb83de..ac61491c9d7f 100644
--- a
On 07/11/2018 08:40 AM, H.J. Lu wrote:
> This is a quad-core machine with HT and 6 GB RAM. The workload is
> x32 GCC build and test with "make -j8". The bug is triggered during GCC
> test after a couple hours. I have a script to set up my workload:
>
> https://github.com/hjl-tools/gcc-regressio
On 07/09/2018 05:50 PM, Georgi Djakov wrote:
> This patch introduces a new API to get requirements and configure the
> interconnect buses across the entire chipset to fit with the current
> demand.
>
> The API is using a consumer/provider-based model, where the providers are
> the interconnect bus
On Wed, 2018-07-11 at 17:10 +0200, Geert Uytterhoeven wrote:
> Print a warning if none of the Signed-off-by lines cover the patch
> author.
>
> Non-ASCII quoted printable encoding in From: headers and (lack of)
> double quotes are handled.
> Split From: headers are not fully handled: only the firs
Jonathan Corbet wrote:
> A minor detail but ... the "r" operation mentioned above is not actually
> implemented in this system call.
Yeah, that's something I'd like to add. NFS4 already does this inside its
->mount() method, so my thought is that we might be able to move this from
there to the
On 07/10/2018 08:08 PM, Li Zhijian wrote:
> root@vm-lkp-nex04-8G-7 ~/linux-v4.18-rc2/tools/testing/selftests/android# make
> make[1]: warning: jobserver unavailable: using -j1. Add '+' to parent make
> rule.
> make[1]: Entering directory
> '/root/linux-v4.18-rc2/tools/testing/selftests/android/i
On Wed, Jul 11, 2018 at 08:42:11AM -0700, Paul E. McKenney wrote:
> On Wed, Jul 11, 2018 at 10:43:45AM +0100, Will Deacon wrote:
> > Hi Alan,
> >
> > On Tue, Jul 10, 2018 at 02:18:13PM -0400, Alan Stern wrote:
> > > More than one kernel developer has expressed the opinion that the LKMM
> > > shoul
On 7/11/2018 7:24 PM, Johan Hovold wrote:
On Tue, Jul 10, 2018 at 12:20:49PM +0530, Keerthy wrote:
Cut down the shutdown time from 2 seconds to 1 sec. In case of roll
over try again.
Signed-off-by: Keerthy
---
drivers/rtc/rtc-omap.c | 9 +++--
1 file changed, 7 insertions(+), 2 delet
Hi Thomas,
On Wed, Jul 11, 2018 at 01:38:52PM +0200, Thomas Bogendoerfer wrote:
> platform devices for sonic and esp didn't have dma_masks.
That's a very brief commit message :)
Could you add a description of why this is a problem & what was broken
as a result of it?
If this is a problem you've
On Wed, Jul 11, 2018 at 04:25:55PM +0100, Al Viro wrote:
> FWIW, looking at the ->f_flags handling, I'm seriously tempted to do
> alloc_file_pseudo(inode, mnt, name, f_flags, ops).
>
> Reason: right now all but two callers of alloc_file_pseudo() are followed
> by setting ->f_flags and for all tho
Hi Yun,
On 02/07/18 12:16, Jun Yao wrote:
> Move {idmap_pg_dir, swapper_pg_dir} to .rodata section and
> populate swapper_pg_dir by fixmap.
(any chance you could split the fixmap bits into a separate patch so that the
rodata move comes last? This will make review and bisecting any problems
easi
Hi,
On 09/07/2018 09:50:47-0600, Rob Herring wrote:
> On Tue, Jun 19, 2018 at 3:40 PM Rob Herring wrote:
> >
> > The DT core will call of_platform_default_populate, so it is not
> > necessary for machine specific code to call it unless there are custom
> > match entries, auxdata or parent device.
On Fri, Jul 06, 2018 at 03:20:47PM +0800, Jisheng Zhang wrote:
> Synopsys SDHCI compatible DesignWare Cores Mobile Storage Host
> Controller can support eMMC/SD/SDIO. Add the bindings.
>
> Signed-off-by: Jisheng Zhang
> ---
> .../bindings/mmc/sdhci-of-dwcmshc.txt | 20 +++
On Mon, Jul 09, 2018 at 04:04:38PM +0530, Vinod wrote:
> On 06-07-18, 11:55, Guodong Xu wrote:
> > From: Li Yu
> >
> > Add optional property hisilicon,dma-min-chan for k3dma.
> >
> > Signed-off-by: Li Yu
> > Signed-off-by: Guodong Xu
> > ---
> > Documentation/devicetree/bindings/dma/k3dma.txt
We have reports of the following crash:
PID: 7 TASK: 88085c6d61c0 CPU: 1 COMMAND: "kworker/u25:0"
#0 [88085c6db710] machine_kexec at 81046239
#1 [88085c6db760] crash_kexec at 810fc248
#2 [88085c6db830] oops_end at 81008ae7
#3 [88085c6
On Wed, Jul 11, 2018 at 05:03:15PM +0100, Will Deacon wrote:
> On Wed, Jul 11, 2018 at 04:47:58PM +0100, Mark Rutland wrote:
> > On Wed, Jul 11, 2018 at 09:20:03AM +0200, Ard Biesheuvel wrote:
> > > On 11 July 2018 at 03:09, Yandong.Zhao wrote:
> > > > diff --git a/arch/arm64/include/asm/simd.h
>
On Wed, Jul 11, 2018 at 08:39:50AM -0700, Guenter Roeck wrote:
> On Wed, Jul 11, 2018 at 04:30:16PM +0100, Sudeep Holla wrote:
[...]
> >
> > Typically new properties needs to registered or discussed in d...@acpica.org
> > Though there's almost no activity on that list for more than a year now.
>
On Thu, Jul 05, 2018 at 01:15:01PM +0200, Frieder Schrempf wrote:
> Adjust the documentation of the new SPI memory interface based
> driver to reflect the new drivers settings.
Bindings shouldn't change (other than new properties) due to driver
changes.
>
> Signed-off-by: Frieder Schrempf
> --
On Wed, 2018-07-11 at 15:57 +0200, Michael Straube wrote:
> On 07/08/18 19:36, Michael Straube wrote:
> > On 07/08/18 18:46, Joe Perches wrote:
> > > On Sun, 2018-07-08 at 12:38 +0200, Michael Straube wrote:
> > >
> > > uint rtw_is_cckratesonly_included(u8 *rate)
> > > {
> > > while (*rate) {
Hi Thomas,
On Wed, Jul 11, 2018 at 01:38:51PM +0200, Thomas Bogendoerfer wrote:
> sg list elements could cover more than one page of data. Therefore
> using plat_map_dma_mem_page() doesn't work for platforms, which have
> IOMMU functionality hidden behind plat_map_dma_XXX functions.
>
> Fixes: e3
On 11/07/18 15:40, Rob Herring wrote:
On Tue, Jul 10, 2018 at 12:43 PM Robin Murphy wrote:
Whilst the common firmware code invoked by dma_configure() initialises
devices' DMA masks according to limitations described by the respective
properties ("dma-ranges" for OF and _DMA/IORT for ACPI), the
On Wed, Jul 11, 2018 at 1:42 AM David Howells wrote:
>
> Buffering till the end means you have to buffer *everything* - and,
> unless you limit your buffer, you risk running out of RAM
Do we really care?
Can't we limit the buffer size to something small?
Right now, the mount options c
On Wed, Jul 11, 2018 at 04:47:58PM +0100, Mark Rutland wrote:
> On Wed, Jul 11, 2018 at 09:20:03AM +0200, Ard Biesheuvel wrote:
> > On 11 July 2018 at 03:09, Yandong.Zhao wrote:
> > > diff --git a/arch/arm64/include/asm/simd.h b/arch/arm64/include/asm/simd.h
> > > index fa8b3fe..784a8c2 100644
> >
Oleg Nesterov writes:
> On 07/10, Eric W. Biederman wrote:
>>
>> @@ -1602,6 +1603,20 @@ static __latent_entropy struct task_struct
>> *copy_process(
>> {
>> int retval;
>> struct task_struct *p;
>> +unsigned seq;
>> +
>> +/*
>> + * Signals that are delivered to multiple pr
On Wed, Jul 11, 2018 at 7:38 AM, Federico Vaga wrote:
Hi Federico,
> Hi Alan,
>
> I have another point that I would like to discuss. It is about the
> usage of 'fpga_mgr_free()' which does not look like consistent.
>
> This function, according to the current implementation, can be used by
> an F
On Wed, Jul 11, 2018 at 02:34:21PM +0200, Andrea Parri wrote:
> On Wed, Jul 11, 2018 at 10:43:11AM +0100, Will Deacon wrote:
> > On Tue, Jul 10, 2018 at 11:38:21AM +0200, Andrea Parri wrote:
> > > This distinction between locking operations and "other acquires" appears
> > > to me not only unmotiva
On Thu, Jul 05, 2018 at 01:15:00PM +0200, Frieder Schrempf wrote:
> Move the documentation of the old SPI NOR driver to the place of the new
> SPI memory interface based driver.
>
> Signed-off-by: Frieder Schrempf
> ---
> Changes in v2:
> ==
> * Split the moving and editing of the dt-
On Tue, 10 Jul 2018 23:44:09 +0100
David Howells wrote:
> sfd = fsopen("ext4", FSOPEN_CLOEXEC);
> write(sfd, "s /dev/sdb1"); // note I'm ignoring write's length arg
> write(sfd, "o noatime");
> write(sfd, "o acl");
> write(sfd, "o user_attr");
> write(sfd, "o i
Another driver turned up that is missing linux/mod_devicetable.h after
the device IDs are split out from linux/platform_device.h:
drivers/extcon/extcon-max3355.c:127:34: error: array type has incomplete
element type 'struct of_device_id'
static const struct of_device_id max3355_match_table[] = {
On Tue, Jul 03, 2018 at 05:04:11PM +0200, Marcel Ziswiler wrote:
> From: Marcel Ziswiler
>
> On ams AS3722, power on when AC OK is enabled by default.
> Making this option as disable by default and enable only
> when platform need this explicitly.
>
> Signed-off-by: Laxman Dewangan
> Reviewed-b
On Wed, Jul 11, 2018 at 09:20:03AM +0200, Ard Biesheuvel wrote:
> On 11 July 2018 at 03:09, Yandong.Zhao wrote:
> > From: Yandong Zhao
> >
> > It does not matter if the caller of may_use_simd() migrates to
> > another cpu after the call, but it is still important that the
> > kernel_neon_busy per
On Wed, 2018-07-11 at 11:34 +0200, Peter Zijlstra wrote:
> On Tue, Jul 10, 2018 at 03:26:29PM -0700, Yu-cheng Yu wrote:
> >
> > +/* MSR_IA32_U_CET and MSR_IA32_S_CET bits */
> > +#define MSR_IA32_CET_SHSTK_EN 0x0001
> > +#define MSR_IA32_CET_WRSS_EN 0x000
I'm announcing the release of the 4.17.6 kernel.
All users of the 4.17 kernel series must upgrade.
The updated 4.17.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.17.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index e4ddbad49636..1a885c8f82ef 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 17
-SUBLEVEL = 5
+SUBLEVEL = 6
EXTRAVERSION =
NAME = Merciless Moray
diff --git a/arch/arm/boot/dts/am3517.dtsi b
I'm announcing the release of the 4.14.55 kernel.
All users of the 4.14 kernel series must upgrade.
The updated 4.14.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.14.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index de0955d8dfa3..0700feaaa6cf 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
# SPDX-License-Identifier: GPL-2.0
VERSION = 4
PATCHLEVEL = 14
-SUBLEVEL = 54
+SUBLEVEL = 55
EXTRAVERSION =
NAME = Petit Gorille
diff --git a/arch/s390/kernel/entry.S b/arch
On Wed, 2018-07-11 at 17:27 +0200, Peter Zijlstra wrote:
> On Wed, Jul 11, 2018 at 07:58:09AM -0700, Yu-cheng Yu wrote:
> >
> > On Wed, 2018-07-11 at 11:45 +0200, Peter Zijlstra wrote:
> > >
> > > On Tue, Jul 10, 2018 at 03:26:30PM -0700, Yu-cheng Yu wrote:
> > > >
> > > >
> > > > diff --git a/
diff --git a/Makefile b/Makefile
index b10646531fcd..c4544293db10 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 9
-SUBLEVEL = 111
+SUBLEVEL = 112
EXTRAVERSION =
NAME = Roaring Lionus
diff --git a/arch/arm/boot/dts/imx6q.dtsi b/arch/arm/boot/dts/imx6q.dtsi
index
I'm announcing the release of the 4.9.112 kernel.
All users of the 4.9 kernel series must upgrade.
The updated 4.9.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.9.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 20a11fd36656..b842298a5970 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 139
+SUBLEVEL = 140
EXTRAVERSION =
NAME = Blurry Fish Butt
diff --git a/arch/arm/boot/dts/imx6q.dtsi b/arch/arm/boot/dts/imx6q.dtsi
ind
I'm announcing the release of the 4.4.140 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
diff --git a/Makefile b/Makefile
index 2288ed3b8674..c498ff938a9c 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 3
PATCHLEVEL = 18
-SUBLEVEL = 114
+SUBLEVEL = 115
EXTRAVERSION =
NAME = Diseased Newt
diff --git a/arch/x86/lib/cmdline.c b/arch/x86/lib/cmdline.c
index 422db000d72
301 - 400 of 875 matches
Mail list logo
