>-Original Message-
>From: Herbert Xu [mailto:herb...@gondor.apana.org.au]
>Sent: Wednesday, April 18, 2018 4:01 AM
>To: Dey, Megha
>Cc: linux-kernel@vger.kernel.org; linux-cry...@vger.kernel.org;
>da...@davemloft.net
>Subject: Re: [PATCH V8 1/5] crypto:
From: Murali Karicheri
Date: Tue, 17 Apr 2018 17:30:29 -0400
> K2G SoC is another variant of Keystone family of SoCs. This patch
> series add support for NetCP driver on this SoC. The QMSS found on
> K2G SoC is a cut down version of the QMSS found on other keystone
> devices
On 4/18/2018 5:46 PM, Paul Moore wrote:
> On Wed, Apr 18, 2018 at 8:41 PM, Casey Schaufler
> wrote:
>> On 4/18/2018 4:47 PM, Paul Moore wrote:
>>> On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote:
Implement the proc fs write to set the
The member auxv in prctl_mm_map structure which be shared with
userspace is pointer type, but the kernel supporting COMPAT didn't
handle it. This patch fix the compat handling for prctl syscall.
Signed-off-by: Li Bin
---
kernel/sys.c | 42
On (04/18/18 16:04), Petr Mladek wrote:
[..]
> > diff --git a/kernel/printk/printk.c b/kernel/printk/printk.c
> > index 2f4af216bd6e..86f0b337cbf6 100644
> > --- a/kernel/printk/printk.c
> > +++ b/kernel/printk/printk.c
> > @@ -1888,6 +1888,7 @@ asmlinkage int vprintk_emit(int facility, int level,
On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote:
> Add container ID auxiliary records to secure computing and abnormal end
> standalone records.
>
> Signed-off-by: Richard Guy Briggs
> ---
> kernel/auditsc.c | 10 --
> 1 file changed, 8
The code defines macro 'PAGE_OFFSET' and uses it to decide if the
address is in kernel space or not. But different architecture has
different 'PAGE_OFFSET' so this program cannot be used for all
platforms.
This commit changes to check returned pointer from ksym_search() to
judge if the address
This commit handles NULL pointer returned by ksym_search() to directly
print address hexadecimal value, the change is applied in 'trace_event',
'spintest' and 'offwaketime' programs.
Signed-off-by: Leo Yan
---
samples/bpf/offwaketime_user.c | 5 +
Structure 'syms' is used to store kernel symbol info by reading proc fs
node '/proc/kallsyms', this structure is declared with 30 entries
and static linked into bss section. For most case the kernel symbols
has less than 30 entries, so it's safe to define so large array, but
the side
This patch series is minor fixes and cleanup for bpf load and samples
code. The first one patch is typo fixing; patch 0002 is refactor for
dynamically allocate memory for kernel symbol structures; the last
three patches are mainly related with refactor with function
ksym_search(), the main
Fix typo by replacing 'iif' with 'if'.
Signed-off-by: Leo Yan
---
samples/bpf/bpf_load.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/samples/bpf/bpf_load.c b/samples/bpf/bpf_load.c
index bebe418..28e4678 100644
--- a/samples/bpf/bpf_load.c
+++
Function ksym_search() is used to parse address and return the symbol
structure, when the address is out of range for kernel symbols it
returns the symbol structure of kernel '_stext' entry; this introduces
confusion and it misses the chance to intuitively tell the address is
out of range.
This
Hello
I write to you based on a request by an investor for
funding/investment in your project.
My name is Christopher Gregson, a financial consultant with Williams
Group UK Properties Limited.
My reason for contacting you is that my client who is a politician,
has an urgent need to invest a
> On Apr 18, 2018, at 9:06 PM, Li Bin wrote:
>
> The member auxv in prctl_mm_map structure which be shared with
> userspace is pointer type, but the kernel supporting COMPAT didn't
> handle it. This patch fix the compat handling for prctl syscall.
>
> Signed-off-by:
We wake up klogd very late - only when current console_sem owner
is done pushing pending kernel messages to the serial/net consoles.
In some cases this results in lost syslog messages, because kernel
log buffer is a circular buffer and if we don't wakeup syslog long
enough there are chances that
On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote:
> Audit events could happen in a network namespace outside of a task
> context due to packets received from the net that trigger an auditing
> rule prior to being associated with a running task. The network
> namespace
From: NeilBrown
Date: Thu, 19 Apr 2018 09:09:05 +1000
> On Wed, Apr 18 2018, Herbert Xu wrote:
>
>> On Wed, Apr 18, 2018 at 04:47:01PM +1000, NeilBrown wrote:
>>> grow_decision and shink_decision no longer exist, so remove
>>> the remaining references to them.
>>>
>>>
Thank you, I am studying the problem.
Pavel
On Wed, Apr 18, 2018 at 9:31 PM, Fengguang Wu wrote:
> On Wed, Apr 18, 2018 at 06:38:25PM -0500, Dennis Zhou wrote:
>>Hi,
>>
>>On Wed, Apr 18, 2018 at 09:55:53PM +0800, Fengguang Wu wrote:
>>>
>>> Hello,
>>>
>>> FYI here is a
Hi, Gary,
On Wed, 2018-04-18 at 16:51 -0400, Hook, Gary wrote:
> On 4/18/2018 4:16 PM, Mehta, Sohil wrote:
> >
> > On Wed, 2018-04-18 at 08:31 +, Yang, Shunyong wrote:
> > >
> > > Maybe the original design is to call debugfs_initialized() before
> > > calling debugfs_create_xxx()?
> > I am
On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote:
> Add container ID auxiliary record(s) to NETFILTER_PKT event standalone
> records. Iterate through all potential container IDs associated with a
> network namespace.
>
> Signed-off-by: Richard Guy Briggs
On 4/18/18 6:54 PM, jiang.bi...@zte.com.cn wrote:
by chance, did you check whether this may cause problems with bfq,
being the latter not protected by the queue lock as cfq?
>>> Checked the bfq code, bfq seems never used blkcg lock derectly, and
>>> update of blkg in the common code is
On Thu, Apr 19, 2018 at 09:51:16AM +0800, jianchao.wang wrote:
> Hi Ming
>
> Thanks for your kindly response.
>
> On 04/18/2018 11:40 PM, Ming Lei wrote:
> >> Regarding to this patchset, it is mainly to fix the dependency between
> >> nvme_timeout and nvme_dev_disable, as your can see:
> >>
On Wed, Apr 18, 2018 at 07:37:59PM -0500, Kim Phillips wrote:
> On Tue, 17 Apr 2018 11:27:26 +0900
> Namhyung Kim wrote:
> > On Mon, Apr 16, 2018 at 05:48:11PM -0500, Kim Phillips wrote:
> > > > a perf/urgent from last week (commit 918965d4897) + this patch:
> > > >
> > > >
On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote:
> Add container ID auxiliary record to mark, watch and tree rule
> configuration standalone records.
>
> Signed-off-by: Richard Guy Briggs
> ---
> kernel/audit_fsnotify.c | 5 -
>
Hi guys, :)
On Wed, Apr 18, 2018 at 09:49:24AM -0400, Steven Rostedt wrote:
> On Wed, 18 Apr 2018 18:34:34 +0900
> Masami Hiramatsu wrote:
>
> > On Fri, 13 Apr 2018 10:44:32 -0400
> > Steven Rostedt wrote:
> >
> > > On Fri, 13 Apr 2018 09:24:34 -0500
On 4/18/2018 4:47 PM, Paul Moore wrote:
> On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote:
>> Implement the proc fs write to set the audit container ID of a process,
>> emitting an AUDIT_CONTAINER record to document the event.
>> ...
>>
>> diff --git
在 2018年4月19日,上午3:42,Andrew Morton 写道:
>
> On Tue, 17 Apr 2018 15:05:32 +0800 Chengguang Xu wrote:
>
>> When specifying iocharset/codepage multiple times in a mount,
>> current option parsing will cause inaccurate refcount of nls
>> module. Hence,
Hi Shameerali,
On 2018/4/18 19:05, Shameerali Kolothum Thodi wrote:
>
>
>> -Original Message-
>> From: linux-arm-kernel [mailto:linux-arm-kernel-boun...@lists.infradead.org]
>> On Behalf Of Yisheng Xie
>> Sent: Thursday, March 29, 2018 8:04 AM
>> To: Neil Leeder
On (04/18/18 11:10), Steven Rostedt wrote:
>
> > > Calling wake_up_klogd() will grab the rq lock and give us a A-B<->B-A
> > > locking order.
> >
> > wake_up_klogd() uses the lockless irq_work_queue(). So it is actually
> > safe.
>
> I didn't look at the code. OK then we don't need to worry
From: Haiyang Zhang
Date: Tue, 17 Apr 2018 15:31:47 -0700
> From: Haiyang Zhang
>
> This patch adds the NetVSP v6 and 6.1 message structures, and includes
> these versions into NetVSC/NetVSP version negotiation process.
>
> Signed-off-by:
On Fri, Mar 16, 2018 at 5:00 AM, Richard Guy Briggs wrote:
> Add container ID auxiliary records to configuration change, feature set change
> and user generated standalone records.
>
> Signed-off-by: Richard Guy Briggs
> ---
> kernel/audit.c | 50
On Wed, Apr 18, 2018 at 06:38:25PM -0500, Dennis Zhou wrote:
>Hi,
>
>On Wed, Apr 18, 2018 at 09:55:53PM +0800, Fengguang Wu wrote:
>>
>> Hello,
>>
>> FYI here is a slightly different boot error in mainline kernel 4.17.0-rc1.
>> It also dates back to v4.16 .
>>
>> It occurs in 4 out of 4 boots.
>>
Hi,
while checking bug [1], I noticed that jiffies based timing loops like
expire = jiffies + timeout + 1;
while (!time_after(jiffies, expire))
do_something;
can last shorter than expected (that is less than timeout). This happens
at least on an Intel Geminilake
On 04/18/18 at 06:01pm, Rahul Lakkireddy wrote:
> On Wednesday, April 04/18/18, 2018 at 11:45:46 +0530, Dave Young wrote:
> > Hi Rahul,
> > On 04/17/18 at 01:14pm, Rahul Lakkireddy wrote:
> > > On production servers running variety of workloads over time, kernel
> > > panic can happen sporadically
Hi Ming
Thanks for your kindly response.
On 04/18/2018 11:40 PM, Ming Lei wrote:
>> Regarding to this patchset, it is mainly to fix the dependency between
>> nvme_timeout and nvme_dev_disable, as your can see:
>> nvme_timeout will invoke nvme_dev_disable, and nvme_dev_disable have to
>> depend
From: Eric Long
This patch will move the Spreadtrum DMA request mode and interrupt type
into one head file for user to configure.
Signed-off-by: Eric Long
Signed-off-by: Baolin Wang
---
Changes since v1:
- No updates.
From: Eric Long
This patch adds one 'struct sprd_dma_config' structure to save Spreadtrum
DMA configuration for each DMA channel. Meanwhile we also did some optimization
for sprd_dma_config() and sprd_dma_prep_dma_memcpy() to prepare to configure
DMA from users.
Define the DMA data width type to make code more readable.
Signed-off-by: Baolin Wang
---
Changes since v1:
- No updates.
---
drivers/dma/sprd-dma.c | 14 +++---
1 file changed, 11 insertions(+), 3 deletions(-)
diff --git a/drivers/dma/sprd-dma.c
From: Eric Long
This patch adds the 'device_config' and 'device_prep_slave_sg' interfaces
for users to configure DMA.
Signed-off-by: Eric Long
Signed-off-by: Baolin Wang
---
Changes since v1:
- The request mode and
From: Eric Long
Define the DMA transfer step type to make code more readable.
Signed-off-by: Eric Long
Signed-off-by: Baolin Wang
---
Changes since v1:
- Convert enum structure to macros definition for DMA step type.
Hi Ingo,
Any comments about that?
Now, When users want to support node hotplug with KASLR, they use
'mem=' to restrict the boot-up memory to the first node memory size.
If we want to boot up some hotpluggable node, their memory can't be
shown.
IMO, only few machines can support physical NUMA
On Thu, Apr 19, 2018 at 10:17:57AM +0800, Fengguang Wu wrote:
>Hello,
>
>FYI this happens in mainline kernel 4.17.0-rc1.
>It at least dates back to v4.15-rc1 .
>
>The regression was reported before
>
> https://lkml.org/lkml/2017/11/30/33
>
>Where the last message from Dmitry mentions that
> On Apr 18, 2018, at 9:06 PM, Li Bin wrote:
>
> The member auxv in prctl_mm_map structure which be shared with
> userspace is pointer type, but the kernel supporting COMPAT didn't
> handle it. This patch fix the compat handling for prctl syscall.
I would propose an
On 04/17/18 22:53, kbuild test robot wrote:
Fixes: d5898e19c0d7 ("spi: pxa2xx: Use core message processing loop")
Signed-off-by: Fengguang Wu
---
spi-pxa2xx.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/spi/spi-pxa2xx.c b/drivers/spi/spi-pxa2xx.c
Hi Rahul,
On 04/17/18 at 01:14pm, Rahul Lakkireddy wrote:
> On production servers running variety of workloads over time, kernel
> panic can happen sporadically after days or even months. It is
> important to collect as much debug logs as possible to root cause
> and fix the problem, that may not
Hi, Gary and Sohil,
On Tue, 2018-04-17 at 13:38 -0400, Hook, Gary wrote:
> On 4/13/2018 8:08 PM, Mehta, Sohil wrote:
> >
> > On Fri, 2018-04-06 at 08:17 -0500, Gary R Hook wrote:
> > >
> > >
> > > +
> > > +void amd_iommu_debugfs_setup(struct amd_iommu *iommu)
> > > +{
> > > + char
On Tue, 2018-04-10 at 13:22 -0400, Waiman Long wrote:
> It was observed occasionally in PowerPC systems that there was reader
> who had not been woken up but that its waiter->task had been cleared.
>
> One probable cause of this missed wakeup may be the fact that the
> waiter->task and the task
> -Original Message-
> From: Robin Murphy [mailto:robin.mur...@arm.com]
> Sent: Tuesday, April 17, 2018 10:23 PM
> To: Nipun Gupta ; robh...@kernel.org;
> frowand.l...@gmail.com
> Cc: will.dea...@arm.com; mark.rutl...@arm.com; catalin.mari...@arm.com;
> h...@lst.de;
As Miklos reported and suggested:
This pattern repeats two times in trace_uprobe.c and in
kernel/events/core.c as well:
ret = kern_path(filename, LOOKUP_FOLLOW, );
if (ret)
goto fail_address_parse;
inode = igrab(d_inode(path.dentry));
path_put();
And
As Miklos reported and suggested:
This pattern repeats two times in trace_uprobe.c and in
kernel/events/core.c as well:
ret = kern_path(filename, LOOKUP_FOLLOW, );
if (ret)
goto fail_address_parse;
inode = igrab(d_inode(path.dentry));
path_put();
And
On 04/17/18 02:01, Hans de Goede wrote:
> Hi,
>
> On 17-04-18 07:14, Randy Dunlap wrote:
>> From: Randy Dunlap
>>
>> The extcon-axp288 driver selects USB_ROLE_SWITCH, but the USB
>> Makefile does not currently build drivers/usb/common/ (where
>> USB_ROLE_SWITCH code is) unless USB_COMMON is set,
On 2018-04-17 18:54, Lars-Peter Clausen wrote:
> On 04/17/2018 04:53 PM, Peter Ujfalusi wrote:
>> On 2018-04-17 16:58, Lars-Peter Clausen wrote:
> There are two options.
>
> Either you extend the generic interfaces so it can cover your usecase in a
> generic way. E.g. the ability
Le 17/04/2018 à 19:10, Mathieu Malaterre a écrit :
On Tue, Apr 17, 2018 at 6:49 PM, Christophe LEROY
wrote:
Le 17/04/2018 à 18:45, Mathieu Malaterre a écrit :
On Tue, Apr 17, 2018 at 12:49 PM, Christophe Leroy
wrote:
This option does dead code and data elimination with the linker by
When running stress-ng on 4.14.34 mainline on x86, I ran into a
"kernel stack regs has bad 'bp' value" warning [1].
Let me know if any more information/debug is useful.
Thanks,
Daniel
-- [1]
WARNING: kernel stack regs at 880638ad76b8 in
stress-ng-af-al:32670 has bad 'bp' value
On 04/17/2018 11:57 PM, Dongwon Kim wrote:
On Tue, Apr 17, 2018 at 09:59:28AM +0200, Daniel Vetter wrote:
On Mon, Apr 16, 2018 at 12:29:05PM -0700, Dongwon Kim wrote:
Yeah, I definitely agree on the idea of expanding the use case to the
general domain where dmabuf sharing is used. However,
Fixes: ef0010a30935 ("vsprintf: don't use 'restricted_pointer()'
when not restricting") for /sys/module/*/sections/.text file.
Reading file /proc/modules shows the correct address:
[root@s35lp76 ~]# cat /proc/modules | egrep '^qeth_l2'
qeth_l2 94208 1 - Live 0x03ff80401000
and reading file
On 2018-04-17 18:42, Vinod Koul wrote:
> On Tue, Apr 17, 2018 at 04:46:43PM +0300, Peter Ujfalusi wrote:
>
>> @@ -709,6 +709,11 @@ struct dma_filter {
>> * be called after period_len bytes have been transferred.
>> * @device_prep_interleaved_dma: Transfer expression in a generic way.
>>
Bonjour, je suis le Sgt. Brenda Wilson, originaire de Lake Jackson au Texas aux
tats-Unis. Jai personnellement fait une recherche spciale
et je suis tomb sur votre information. Je suis en train de vous
crire ce Message de la base militaire amricaine de Kaboul en
Afghanistan. Jai une
On Wed, Apr 18, 2018 at 10:43:26AM +0530, Naresh Kamboju wrote:
> On 17 April 2018 at 21:27, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.16.3 release.
> > There are 68 patches in this series, all will be posted as a response
> > to this one. If anyone
On Tue, Apr 17, 2018 at 03:03:52PM -0600, Shuah Khan wrote:
> On 04/17/2018 09:57 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.16.3 release.
> > There are 68 patches in this series, all will be posted as a response
> > to this one. If anyone has any
On Freitag, 23. März 2018 15:48:51 CEST Sricharan R wrote:
> Add the common data for all dk07 based boards.
>
> Reviewed-by: Abhishek Sahu
> Signed-off-by: Sricharan R
> ---
> arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1.dtsi | 69
> +++
> 1 file changed, 69 insertions(+)
On Freitag, 23. März 2018 15:48:48 CEST Sricharan R wrote:
> Add the common parts for the dk04 boards.
>
> Reviewed-by: Abhishek Sahu
> Signed-off-by: Sricharan R
> ---
> arch/arm/boot/dts/qcom-ipq4019-ap.dk04.1.dtsi | 115
> ++
> arch/arm/boot/dts/qcom-ipq4019.dtsi
Hi Phil,
On Fri, Apr 13, 2018 at 9:47 AM, Phil Edworthy
wrote:
> Hi Hoan,
>
> On 13 April 2018 17:37 Hoan Tran wrote:
>> On Fri, Apr 13, 2018 at 1:51 AM, Phil Edworthy wrote:
>> > The DesignWare GPIO IP can be configured for either 1 interrupt or 1
>> > per GPIO in port A, but the driver
On 2018-04-18 09:39, Peter Ujfalusi wrote:
>
>
> On 2018-04-17 18:42, Vinod Koul wrote:
>> On Tue, Apr 17, 2018 at 04:46:43PM +0300, Peter Ujfalusi wrote:
>>
>>> @@ -709,6 +709,11 @@ struct dma_filter {
>>> * be called after period_len bytes have been transferred.
>>> *
On 18/04/18 11:08, Alastair D'Silva wrote:
From: Alastair D'Silva
This patch adds a CPU feature bit to show whether the CPU has
the TIDR register available, enabling as_notify/wait in userspace.
Signed-off-by: Alastair D'Silva
Per my previous email:
Reviewed-by: Andrew Donnellan
--
Hello,
On Wed, Apr 18, 2018 at 03:16:45AM +0300, Alexander Popov wrote:
> Currently i2cdev_ioctl_rdwr() doesn't check i2c_msg len against zero
> before calling memdup_user(). If this len is zero memdup_user() returns
> ZERO_SIZE_PTR, which is later considered as valid since
>
On Mittwoch, 18. April 2018 08:59:46 CEST Sven Eckelmann wrote:
[...]
> I would not know how to disable QSEE on these boards and thus would assume
> that it should be part of this dtsi.
Just did some reviews of the reserved-memory regions in other QCA devices and
it looks like this tz and smem
On Tue 17-04-18 20:08:24, Matthew Wilcox wrote:
> On Wed, Apr 18, 2018 at 11:29:12AM +0900, Minchan Kim wrote:
> > If there are heavy memory pressure, page allocation with __GFP_NOWAIT
> > fails easily although it's order-0 request.
> > I got below warning 9 times for normal boot.
> >
> > [
Hi Sven,
On 4/18/2018 12:29 PM, Sven Eckelmann wrote:
> On Freitag, 23. März 2018 15:48:51 CEST Sricharan R wrote:
>> Add the common data for all dk07 based boards.
>>
>> Reviewed-by: Abhishek Sahu
>> Signed-off-by: Sricharan R
>> ---
>> arch/arm/boot/dts/qcom-ipq4019-ap.dk07.1.dtsi | 69
>>
On 18/04/18 11:08, Alastair D'Silva wrote:
From: Alastair D'Silva
Switch the use of TIDR on it's CPU feature, rather than assuming it
is available based on architecture.
Signed-off-by: Alastair D'Silva
Reviewed-by: Andrew Donnellan
--
Andrew Donnellan OzLabs, ADL Canberra
[[ I mistyped linux-kernel the first time I sent these, so
resending. Please reply to this set. Sorry - neilb ]]
Some of these have been posted before and a couple
received an Ack from Herbert, but haven't appeared in any git tree
yet.
Another (the first) has been sent but received no ack.
Neither rhashtable_walk_enter() or rhltable_walk_enter() sleep, so
remove the comments which suggest that they do.
Signed-off-by: NeilBrown
---
include/linux/rhashtable.h |3 ---
lib/rhashtable.c |3 ---
2 files changed, 6 deletions(-)
diff --git a/include/linux/rhashtable.h
The documentation claims that when rhashtable_walk_start_check()
detects a resize event, it will rewind back to the beginning
of the table. This is not true. We need to set ->slot and
->skip to be zero for it to be true.
Acked-by: Herbert Xu
Signed-off-by: NeilBrown
---
lib/rhashtable.c |
grow_decision and shink_decision no longer exist, so remove
the remaining references to them.
Signed-off-by: NeilBrown
---
include/linux/rhashtable.h | 33 ++---
1 file changed, 14 insertions(+), 19 deletions(-)
diff --git a/include/linux/rhashtable.h
If the sequence:
obj = rhashtable_walk_next(iter);
rhashtable_walk_stop(iter);
rhashtable_remove_fast(ht, >head, params);
rhashtable_walk_start(iter);
races with another thread inserting or removing
an object on the same hash chain, a subsequent
rhashtable_walk_next() is not
Hi Sven,
On 4/18/2018 12:37 PM, Sven Eckelmann wrote:
> On Mittwoch, 18. April 2018 08:59:46 CEST Sven Eckelmann wrote:
> [...]
>> I would not know how to disable QSEE on these boards and thus would assume
>> that it should be part of this dtsi.
>
>
> Just did some reviews of the
rhashtable_walk_prev() returns the object returned by
the previous rhashtable_walk_next(), providing it is still in the
table (or was during this grace period).
This works even if rhashtable_walk_stop() and rhashtable_talk_start()
have been called since the last rhashtable_walk_next().
If there
Reading file /proc/modules shows the correct address:
[root@s35lp76 ~]# cat /proc/modules | egrep '^qeth_l2'
qeth_l2 94208 1 - Live 0x03ff80401000
and reading file /sys/module/qeth_l2/sections/.text
[root@s35lp76 ~]# cat /sys/module/qeth_l2/sections/.text
0x18ea8363
displays a random
Hi Doug,
Patch looks good to me, I just have some minor comments.
On Wed, Apr 18, 2018 at 5:31 AM, Douglas Anderson wrote:
> In of_get_regulation_constraints() we were taking the result of
> of_map_mode() (an unsigned int) and assigning it to an int. We were
> then checking whether this value
When a walk of an rhashtable is interrupted with rhastable_walk_stop()
and then rhashtable_walk_start(), the location to restart from is based
on a 'skip' count in the current hash chain, and this can be incorrect
if insertions or deletions have happened. This does not happen when
the walk is not
Hi Peter,
On Tue, 17 Apr 2018 15:10:48 +0200
Peter Rosin wrote:
> With bus-type/bus-width properties in the endpoint nodes, the video-
> interface of the connection can be specified for cases where the
> heuristic fails to select the correct output mode. This can happen
> e.g. if not all RGB
On Wed, Apr 18, 2018 at 09:14:36AM +0200, Thomas Richter wrote:
> Reading file /proc/modules shows the correct address:
> [root@s35lp76 ~]# cat /proc/modules | egrep '^qeth_l2'
> qeth_l2 94208 1 - Live 0x03ff80401000
>
> and reading file /sys/module/qeth_l2/sections/.text
> [root@s35lp76 ~]#
2018-04-17 20:47 GMT+08:00 Arnd Bergmann :
> On Mon, Apr 16, 2018 at 11:06 AM, Greentime Hu wrote:
>> 2018-04-16 11:58 GMT+08:00 Guenter Roeck :
>>
>> This built failure is because the toolchain version you used is not
>> supported the latest intrinsic function/macro.
>> We are sending the latest
On Wed 18-04-18 11:29:12, Minchan Kim wrote:
> If there are heavy memory pressure, page allocation with __GFP_NOWAIT
> fails easily although it's order-0 request.
> I got below warning 9 times for normal boot.
>
> [ 17.072747] c0 0 : page allocation failure: order:0,
>
--
--
Attn: Beneficiary,
Compliments of the day. This is an official notification from the
International Monetary Fund (IMF) after due consideration of the
rigorous/difficult process engaged by Banks/financial home and
delivery agents/Courier companies in payment of your long awaited
On 04/18/2018 09:17 AM, Tobin C. Harding wrote:
> On Wed, Apr 18, 2018 at 09:14:36AM +0200, Thomas Richter wrote:
>> Reading file /proc/modules shows the correct address:
>> [root@s35lp76 ~]# cat /proc/modules | egrep '^qeth_l2'
>> qeth_l2 94208 1 - Live 0x03ff80401000
>>
>> and reading file
On 17 April 2018 at 21:28, Greg Kroah-Hartman
wrote:
> This is the start of the stable review cycle for the 4.14.35 release.
> There are 49 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.
>
>
On Wed, 2018-04-18 at 05:58 +, Yang, Shunyong wrote:
> Hi, Gary and Sohil,
>
> On Tue, 2018-04-17 at 13:38 -0400, Hook, Gary wrote:
> > On 4/13/2018 8:08 PM, Mehta, Sohil wrote:
> > >
> > > On Fri, 2018-04-06 at 08:17 -0500, Gary R Hook wrote:
> > > >
> > > >
> > > > +
> > > > +void
On 04/17/2018 12:08 PM, Oleksandr Andrushchenko wrote:
On 04/17/2018 12:04 PM, Daniel Vetter wrote:
On Tue, Apr 17, 2018 at 10:40:12AM +0300, Oleksandr Andrushchenko wrote:
From: Oleksandr Andrushchenko
Even if xen-front allocates its buffers from contiguous memory
those are still not
On Tue, 17 Apr 2018 15:10:50 +0200
Peter Rosin wrote:
> This beats the heuristic that the connector is involved in what format
> should be output for cases where this fails.
>
> E.g. if there is a bridge that changes format between the encoder and the
> connector, or if some of the RGB pins
This looks like a binder bug, but none of the Android devs are CC'd.
The've probably already seen it, but let me forward it to them.
regards,
dan carpenter
On Tue, Apr 17, 2018 at 06:02:02PM -0700, syzbot wrote:
> Hello,
>
> syzbot hit the following crash on upstream commit
>
On 18/04/18 11:08, Alastair D'Silva wrote:
From: Alastair D'Silva
Signed-off-by: Alastair D'Silva
This looks better.
Acked-by: Andrew Donnellan
---
Documentation/accelerators/ocxl.rst | 11 +++
1 file changed, 11 insertions(+)
diff --git a/Documentation/accelerators/ocxl.rst
On 2018-04-18 09:16, Boris Brezillon wrote:
> Hi Peter,
>
> On Tue, 17 Apr 2018 15:10:48 +0200
> Peter Rosin wrote:
>
>> With bus-type/bus-width properties in the endpoint nodes, the video-
>> interface of the connection can be specified for cases where the
>> heuristic fails to select the
With lockdep enabled, when trigger nvme_remove, suspicious RCU
usage warning will be printed out.
Fix it with adding srcu_read_lock/unlock in it.
Signed-off-by: Jianchao Wang
---
drivers/nvme/host/nvme.h | 9 +++--
1 file changed, 7 insertions(+), 2 deletions(-)
diff --git
Hi Amit,
> AOSP use userspace firmware loader to load firmwares, which will
> return -EAGAIN in case qca/rampatch_00440302.bin is not found.
> Since there is no rampatch for dragonboard820c QCA controller
> revision, just make it work as is.
>
> CC: Loic Poulain
> CC: Nicolas Dechesne
> CC:
On Wed, Apr 18, 2018 at 09:38:39AM +0300, Oleksandr Andrushchenko wrote:
> On 04/17/2018 11:57 PM, Dongwon Kim wrote:
> > On Tue, Apr 17, 2018 at 09:59:28AM +0200, Daniel Vetter wrote:
> > > On Mon, Apr 16, 2018 at 12:29:05PM -0700, Dongwon Kim wrote:
> 3.2 Backend exports dma-buf to xen-front
>
On Mon, Apr 16, 2018 at 09:13:22AM -0700, Linus Torvalds wrote:
> See for example commit 8c06c7740d19 ("x86/pti: Leave kernel text
> global for !PCID") and in particular the performance numbers (that's
> an Atom microserver, but it was chosen due to lack of PCID).
Okay, I checked this on 32 bit
On Tue, 17 Apr 2018 15:10:51 +0200
Peter Rosin wrote:
> When the of-graph points to a tda998x-compatible HDMI encoder, register
> as a component master and bind to the encoder/connector provided by
> the tda998x driver.
Can't we do the opposite: make the tda998x driver expose its devices as
drm
Hi,
On Mittwoch, 18. April 2018 12:45:20 CEST Sricharan R wrote:
> Right, will add the above change to soc.dtsi in V6. Does that sound ok for
> you ?
I have submitted a patch for this now [1] because I need this for OpenWrt
(sooner rather than later). And I am not sure whether it is good to
Hi Thierry,
> This patchset enables the Qualcomm BT controller QCA6174 node in the
> device tree of the db820c board. This allows the bluetooth chipset to
> be probed and registered against the hci layer by using the serdev
> framework.
>
> This patchset also contains the documentation for the
801 - 900 of 1686 matches
Mail list logo