On Wed 18-04-18 23:07:12, Tetsuo Handa wrote:
> >From 3f396857d23d4bf1fac4d4332316b5ba0af6d2f9 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa
> Date: Wed, 18 Apr 2018 23:00:53 +0900
> Subject: [PATCH v2] fs, elf: don't complain MAP_FIXED_NOREPLACE unless
>
On Wed 18-04-18 23:07:12, Tetsuo Handa wrote:
> >From 3f396857d23d4bf1fac4d4332316b5ba0af6d2f9 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa
> Date: Wed, 18 Apr 2018 23:00:53 +0900
> Subject: [PATCH v2] fs, elf: don't complain MAP_FIXED_NOREPLACE unless
> -EEXIST error.
>
> Commit
On Thu, Apr 19, 2018 at 01:49:41PM +0800, Fengguang Wu wrote:
Hello,
FYI this warning dates back to v4.16-rc5 .
It's rather rare and often happen together with other errors.
Sorry, that should be 0day didn't catch this particular WARNING.
So it just occasionally show up in the context of
On Thu, Apr 19, 2018 at 01:49:41PM +0800, Fengguang Wu wrote:
Hello,
FYI this warning dates back to v4.16-rc5 .
It's rather rare and often happen together with other errors.
Sorry, that should be 0day didn't catch this particular WARNING.
So it just occasionally show up in the context of
Quoting David Collins (2018-03-22 18:30:06)
> On 03/21/2018 12:07 PM, Stephen Boyd wrote:
> > Quoting David Collins (2018-03-16 18:09:10)
> >> diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig
> >> index 097f617..e0ecd0a 100644
> >> --- a/drivers/regulator/Kconfig
> >> +++
Quoting David Collins (2018-03-22 18:30:06)
> On 03/21/2018 12:07 PM, Stephen Boyd wrote:
> > Quoting David Collins (2018-03-16 18:09:10)
> >> diff --git a/drivers/regulator/Kconfig b/drivers/regulator/Kconfig
> >> index 097f617..e0ecd0a 100644
> >> --- a/drivers/regulator/Kconfig
> >> +++
On Wed, Apr 18, 2018 at 06:02:50PM +0900, Masami Hiramatsu wrote:
> On Mon, 16 Apr 2018 21:07:47 -0700
> Joel Fernandes wrote:
>
> > With TRACE_IRQFLAGS, we call trace_ API too many times. We don't need
> > to if local_irq_restore or local_irq_save didn't actually do anything.
On Wed, Apr 18, 2018 at 06:02:50PM +0900, Masami Hiramatsu wrote:
> On Mon, 16 Apr 2018 21:07:47 -0700
> Joel Fernandes wrote:
>
> > With TRACE_IRQFLAGS, we call trace_ API too many times. We don't need
> > to if local_irq_restore or local_irq_save didn't actually do anything.
> >
> > This
On Wed, 2018-04-18 at 07:47 +0200, Mike Galbraith wrote:
> On Tue, 2018-04-17 at 15:21 +0100, Matt Fleming wrote:
> > Hi guys,
> >
> > We've seen a bug in one of our SLE kernels where the cpu stopper
> > thread ("migration/15") is entering idle balance. This then triggers
> > active load balance.
On Wed, 2018-04-18 at 07:47 +0200, Mike Galbraith wrote:
> On Tue, 2018-04-17 at 15:21 +0100, Matt Fleming wrote:
> > Hi guys,
> >
> > We've seen a bug in one of our SLE kernels where the cpu stopper
> > thread ("migration/15") is entering idle balance. This then triggers
> > active load balance.
On Wed, Apr 18, 2018 at 06:53:30AM -0700, Raj, Ashok wrote:
> On Wed, Apr 18, 2018 at 02:22:12PM +0200, Borislav Petkov wrote:
> > On Wed, Apr 18, 2018 at 02:08:40PM +0200, Vitezslav Samel wrote:
> > > I switched to firmware-in-kernel early loading and that works OK.
>
> firmware-in-kernel means
On Wed, Apr 18, 2018 at 06:53:30AM -0700, Raj, Ashok wrote:
> On Wed, Apr 18, 2018 at 02:22:12PM +0200, Borislav Petkov wrote:
> > On Wed, Apr 18, 2018 at 02:08:40PM +0200, Vitezslav Samel wrote:
> > > I switched to firmware-in-kernel early loading and that works OK.
>
> firmware-in-kernel means
On Wed, Apr 18, 2018 at 10:21:25PM -0700, Alexei Starovoitov wrote:
> On Thu, Apr 19, 2018 at 01:12:49PM +0800, Leo Yan wrote:
> > On Wed, Apr 18, 2018 at 09:47:45PM -0700, Alexei Starovoitov wrote:
> > > On Thu, Apr 19, 2018 at 09:34:05AM +0800, Leo Yan wrote:
> > > > The code defines macro
On Wed, Apr 18, 2018 at 10:21:25PM -0700, Alexei Starovoitov wrote:
> On Thu, Apr 19, 2018 at 01:12:49PM +0800, Leo Yan wrote:
> > On Wed, Apr 18, 2018 at 09:47:45PM -0700, Alexei Starovoitov wrote:
> > > On Thu, Apr 19, 2018 at 09:34:05AM +0800, Leo Yan wrote:
> > > > The code defines macro
When sending control commands, virtio net sets up several buffers for
DMA. The buffers are all part of the net device which means it's
actually allocated by kvmalloc so it's in theory (on extreme memory
pressure) possible to get a vmalloc'ed buffer which on some platforms
means we can't DMA there.
Programming vids (adding or removing them) still passes
guest-endian values in the DMA buffer. That's wrong
if guest is big-endian and when virtio 1 is enabled.
Note: this is on top of a previous patch:
virtio_net: split out ctrl buffer
Fixes: 9465a7a6f ("virtio_net: enable v1.0
When sending control commands, virtio net sets up several buffers for
DMA. The buffers are all part of the net device which means it's
actually allocated by kvmalloc so it's in theory (on extreme memory
pressure) possible to get a vmalloc'ed buffer which on some platforms
means we can't DMA there.
Programming vids (adding or removing them) still passes
guest-endian values in the DMA buffer. That's wrong
if guest is big-endian and when virtio 1 is enabled.
Note: this is on top of a previous patch:
virtio_net: split out ctrl buffer
Fixes: 9465a7a6f ("virtio_net: enable v1.0
Here are a couple of fixes related to the virtio control buffer.
Lightly tested on x86 only.
Michael S. Tsirkin (3):
virtio_net: split out ctrl buffer
virtio_net: fix adding vids on big-endian
virtio_net: sparse annotation fix
drivers/net/virtio_net.c | 68
Here are a couple of fixes related to the virtio control buffer.
Lightly tested on x86 only.
Michael S. Tsirkin (3):
virtio_net: split out ctrl buffer
virtio_net: fix adding vids on big-endian
virtio_net: sparse annotation fix
drivers/net/virtio_net.c | 68
offloads is a buffer in virtio format, should use
the __virtio64 tag.
Signed-off-by: Michael S. Tsirkin
---
drivers/net/virtio_net.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
index f84fe04..c5b11f2
offloads is a buffer in virtio format, should use
the __virtio64 tag.
Signed-off-by: Michael S. Tsirkin
---
drivers/net/virtio_net.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/virtio_net.c b/drivers/net/virtio_net.c
index f84fe04..c5b11f2 100644
---
On Thu, Apr 19, 2018 at 01:12:49PM +0800, Leo Yan wrote:
> On Wed, Apr 18, 2018 at 09:47:45PM -0700, Alexei Starovoitov wrote:
> > On Thu, Apr 19, 2018 at 09:34:05AM +0800, Leo Yan wrote:
> > > The code defines macro 'PAGE_OFFSET' and uses it to decide if the
> > > address is in kernel space or
On Thu, Apr 19, 2018 at 01:12:49PM +0800, Leo Yan wrote:
> On Wed, Apr 18, 2018 at 09:47:45PM -0700, Alexei Starovoitov wrote:
> > On Thu, Apr 19, 2018 at 09:34:05AM +0800, Leo Yan wrote:
> > > The code defines macro 'PAGE_OFFSET' and uses it to decide if the
> > > address is in kernel space or
On Thu, Apr 19, 2018 at 08:01:49AM +0300, Michael S. Tsirkin wrote:
> When sending control commands, virtio net sets up several buffers for
> DMA. The buffers are all part of the net device which means it's
> actually allocated by kvmalloc so in theory (on extreme memory pressure)
> it's possible
On Thu, Apr 19, 2018 at 08:01:49AM +0300, Michael S. Tsirkin wrote:
> When sending control commands, virtio net sets up several buffers for
> DMA. The buffers are all part of the net device which means it's
> actually allocated by kvmalloc so in theory (on extreme memory pressure)
> it's possible
On Wed, 18 Apr 2018, Joe Perches wrote:
> On Thu, 2018-04-19 at 06:40 +0200, Julia Lawall wrote:
> >
> > On Wed, 18 Apr 2018, Joe Perches wrote:
> >
> > > On Tue, 2018-04-17 at 17:07 +0800, yuank...@codeaurora.org wrote:
> > > > Hi julia,
> > > >
> > > > On 2018-04-15 05:19 AM, Julia Lawall
On Wed, 18 Apr 2018, Joe Perches wrote:
> On Thu, 2018-04-19 at 06:40 +0200, Julia Lawall wrote:
> >
> > On Wed, 18 Apr 2018, Joe Perches wrote:
> >
> > > On Tue, 2018-04-17 at 17:07 +0800, yuank...@codeaurora.org wrote:
> > > > Hi julia,
> > > >
> > > > On 2018-04-15 05:19 AM, Julia Lawall
Several people have asked me to write this and I think one person was
maybe working on writing it themselves...
The point of this check is to find place which might be vulnerable to
the Spectre vulnerability. In the kernel we have the array_index_nospec()
macro which turns off speculation.
Several people have asked me to write this and I think one person was
maybe working on writing it themselves...
The point of this check is to find place which might be vulnerable to
the Spectre vulnerability. In the kernel we have the array_index_nospec()
macro which turns off speculation.
On Wed, Apr 18, 2018 at 09:47:45PM -0700, Alexei Starovoitov wrote:
> On Thu, Apr 19, 2018 at 09:34:05AM +0800, Leo Yan wrote:
> > 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
On Wed, Apr 18, 2018 at 09:47:45PM -0700, Alexei Starovoitov wrote:
> On Thu, Apr 19, 2018 at 09:34:05AM +0800, Leo Yan wrote:
> > 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
On Wed, 18 Apr 2018 15:11:24 +0200
Christophe LEROY wrote:
> Le 18/04/2018 à 10:36, Mathieu Malaterre a écrit :
> > Christophe,
> >
> > On Wed, Apr 18, 2018 at 8:34 AM, Christophe LEROY
> > wrote:
> >>
> >>
> >> Le 17/04/2018 à 19:10, Mathieu
On Wed, 18 Apr 2018 15:11:24 +0200
Christophe LEROY wrote:
> Le 18/04/2018 à 10:36, Mathieu Malaterre a écrit :
> > Christophe,
> >
> > On Wed, Apr 18, 2018 at 8:34 AM, Christophe LEROY
> > wrote:
> >>
> >>
> >> Le 17/04/2018 à 19:10, Mathieu Malaterre a écrit :
> >>>
> >>> On Tue, Apr 17,
This implements a misc character device named "qrtr-tun" for the purpose
of allowing user space applications to implement endpoints in the qrtr
network.
This allows more advanced (and dynamic) testing of the qrtr code as well
as opens up the ability of tunneling qrtr over a network or USB link.
This implements a misc character device named "qrtr-tun" for the purpose
of allowing user space applications to implement endpoints in the qrtr
network.
This allows more advanced (and dynamic) testing of the qrtr code as well
as opens up the ability of tunneling qrtr over a network or USB link.
When sending control commands, virtio net sets up several buffers for
DMA. The buffers are all part of the net device which means it's
actually allocated by kvmalloc so in theory (on extreme memory pressure)
it's possible to get a vmalloc'ed buffer which on some platforms means
we can't DMA there.
When sending control commands, virtio net sets up several buffers for
DMA. The buffers are all part of the net device which means it's
actually allocated by kvmalloc so in theory (on extreme memory pressure)
it's possible to get a vmalloc'ed buffer which on some platforms means
we can't DMA there.
On Wed 18 Apr 16:28 PDT 2018, Evan Green wrote:
> From: Guenter Roeck
>
> Incoming Qualcomm changes for GENI, i2c [1], and cmd-db [2] are enabled
> with COMPILE_TEST in drivers/soc/qcom. For this to work, the Makefile
> in that directory has to be included unconditionally,
On Wed 18 Apr 16:28 PDT 2018, Evan Green wrote:
> From: Guenter Roeck
>
> Incoming Qualcomm changes for GENI, i2c [1], and cmd-db [2] are enabled
> with COMPILE_TEST in drivers/soc/qcom. For this to work, the Makefile
> in that directory has to be included unconditionally, rather than only
> if
> Subject: Re: [PATCH v2] storvsc: Set up correct queue depth values for IDE
> devices
>
>
> Long,
>
> > Can you take a look at the following patch?
>
> >> > + max_sub_channels =
> >> > +(num_cpus - 1) / storvsc_vcpus_per_sub_channel;
>
> What happens if num_cpus = 1?
If
> Subject: Re: [PATCH v2] storvsc: Set up correct queue depth values for IDE
> devices
>
>
> Long,
>
> > Can you take a look at the following patch?
>
> >> > + max_sub_channels =
> >> > +(num_cpus - 1) / storvsc_vcpus_per_sub_channel;
>
> What happens if num_cpus = 1?
If
On Thu, 2018-04-19 at 06:40 +0200, Julia Lawall wrote:
>
> On Wed, 18 Apr 2018, Joe Perches wrote:
>
> > On Tue, 2018-04-17 at 17:07 +0800, yuank...@codeaurora.org wrote:
> > > Hi julia,
> > >
> > > On 2018-04-15 05:19 AM, Julia Lawall wrote:
> > > > On Wed, 11 Apr 2018, Joe Perches wrote:
> >
On Thu, 2018-04-19 at 06:40 +0200, Julia Lawall wrote:
>
> On Wed, 18 Apr 2018, Joe Perches wrote:
>
> > On Tue, 2018-04-17 at 17:07 +0800, yuank...@codeaurora.org wrote:
> > > Hi julia,
> > >
> > > On 2018-04-15 05:19 AM, Julia Lawall wrote:
> > > > On Wed, 11 Apr 2018, Joe Perches wrote:
> >
On Thu, Apr 19, 2018 at 09:34:05AM +0800, Leo Yan wrote:
> 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
On Thu, Apr 19, 2018 at 09:34:05AM +0800, Leo Yan wrote:
> 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
On Wed, 18 Apr 2018, Joe Perches wrote:
> On Tue, 2018-04-17 at 17:07 +0800, yuank...@codeaurora.org wrote:
> > Hi julia,
> >
> > On 2018-04-15 05:19 AM, Julia Lawall wrote:
> > > On Wed, 11 Apr 2018, Joe Perches wrote:
> > >
> > > > On Thu, 2018-04-12 at 08:22 +0200, Julia Lawall wrote:
> > >
On Wed, 18 Apr 2018, Joe Perches wrote:
> On Tue, 2018-04-17 at 17:07 +0800, yuank...@codeaurora.org wrote:
> > Hi julia,
> >
> > On 2018-04-15 05:19 AM, Julia Lawall wrote:
> > > On Wed, 11 Apr 2018, Joe Perches wrote:
> > >
> > > > On Thu, 2018-04-12 at 08:22 +0200, Julia Lawall wrote:
> > >
On Wed, 2018-04-18 at 21:01 +, mario.limoncie...@dell.com wrote:
> >
> > > [...]
> > > Srinivas,
> > >
> > > Do you know why Runtime PM is defaulting to disabled for all of
> > > these
> > > devices? Is that a default kernel policy problem or a distro
> > > policy
> > > problem?
> >
> >
On Wed, 2018-04-18 at 21:01 +, mario.limoncie...@dell.com wrote:
> >
> > > [...]
> > > Srinivas,
> > >
> > > Do you know why Runtime PM is defaulting to disabled for all of
> > > these
> > > devices? Is that a default kernel policy problem or a distro
> > > policy
> > > problem?
> >
> >
Hi all,
Changes since 20180418:
New tree: modules-fixes
I have added a patch to the arm-current tree to fix build problems
discovered overnight.
The sound-asoc tree lost its build failure.
Non-merge commits (relative to Linus' tree): 1055
1121 files changed, 36028 insertions(+), 19043
Hi all,
Changes since 20180418:
New tree: modules-fixes
I have added a patch to the arm-current tree to fix build problems
discovered overnight.
The sound-asoc tree lost its build failure.
Non-merge commits (relative to Linus' tree): 1055
1121 files changed, 36028 insertions(+), 19043
On Thursday 19 April 2018 05:57 AM, Daniel Kurtz wrote:
Hi Vijendar,
On Wed, Apr 18, 2018 at 5:02 AM Vijendar Mukunda
wrote:
With in ACP, There are three I2S controllers can be
configured/enabled ( I2S SP, I2S MICSP, I2S BT).
Default enabled I2S controller
On Thursday 19 April 2018 05:57 AM, Daniel Kurtz wrote:
Hi Vijendar,
On Wed, Apr 18, 2018 at 5:02 AM Vijendar Mukunda
wrote:
With in ACP, There are three I2S controllers can be
configured/enabled ( I2S SP, I2S MICSP, I2S BT).
Default enabled I2S controller instance is I2S SP.
This patch
Christoph,
> The default already is to never bounce, so the call is a no-op.
Applied to 4.18/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
Christoph,
> The default already is to never bounce, so the call is a no-op.
Applied to 4.18/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
Christoph,
> The default already is to never bounce, so the call is a no-op.
Applied to 4.18/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
Christoph,
> The default already is to never bounce, so the call is a no-op.
Applied to 4.18/scsi-queue. Thanks!
--
Martin K. Petersen Oracle Linux Engineering
On Sat, Apr 14, 2018 at 9:17 PM, Kai-Heng Feng
wrote:
> Hi Satish,
>
>> On 2018Mar21, at 00:57, Kai-Heng Feng wrote:
>>
>> Satish Baddipadige wrote:
>>
>>> On Thu, Feb 15, 2018 at 7:37 PM, Siva Reddy
On Sat, Apr 14, 2018 at 9:17 PM, Kai-Heng Feng
wrote:
> Hi Satish,
>
>> On 2018Mar21, at 00:57, Kai-Heng Feng wrote:
>>
>> Satish Baddipadige wrote:
>>
>>> On Thu, Feb 15, 2018 at 7:37 PM, Siva Reddy Kallam
>>> wrote:
On Mon, Feb 12, 2018 at 10:59 AM, Siva Reddy Kallam
wrote:
>
On 18-04-18, 08:56, Markus Mayer wrote:
> From: Jim Quinlan
>
> If the SCMI cpufreq driver is supported, we bail, so that the new
> approach can be used.
>
> Signed-off-by: Jim Quinlan
> Signed-off-by: Markus Mayer
> ---
>
On 18-04-18, 08:56, Markus Mayer wrote:
> From: Jim Quinlan
>
> If the SCMI cpufreq driver is supported, we bail, so that the new
> approach can be used.
>
> Signed-off-by: Jim Quinlan
> Signed-off-by: Markus Mayer
> ---
> drivers/cpufreq/brcmstb-avs-cpufreq.c | 16
> 1 file
On 18-04-18, 08:56, Markus Mayer wrote:
> From: Markus Mayer
>
> This debug code was helpful while developing the driver, but it isn't
> being used for anything anymore.
>
> Signed-off-by: Markus Mayer
> ---
> drivers/cpufreq/Kconfig.arm |
On 18-04-18, 08:56, Markus Mayer wrote:
> From: Markus Mayer
>
> This debug code was helpful while developing the driver, but it isn't
> being used for anything anymore.
>
> Signed-off-by: Markus Mayer
> ---
> drivers/cpufreq/Kconfig.arm | 10 --
>
On Thursday 12 April 2018 10:14 PM, santosh.shilim...@oracle.com wrote:
> On 4/11/18 9:53 PM, Keerthy wrote:
>> From: Dave Gerlach
>>
>> After an RTC+DDR cycle we lose sram context so emif pm functions present
>> in sram are lost. We can check if the first byte of the original
On Thursday 12 April 2018 10:14 PM, santosh.shilim...@oracle.com wrote:
> On 4/11/18 9:53 PM, Keerthy wrote:
>> From: Dave Gerlach
>>
>> After an RTC+DDR cycle we lose sram context so emif pm functions present
>> in sram are lost. We can check if the first byte of the original
>> code in DDR
James,
>
>> I do not know when it is merge-window. About the apply version, it does not
>> have limited.
>
> 'git fetch' Linus' tree and look at the tags. 'v4.16' lost its '-rc' suffixes,
> and there isn't a 'v4.17-rc1' yet, so we are still in the merge window.
>
> Linus sends a message to
James,
>
>> I do not know when it is merge-window. About the apply version, it does not
>> have limited.
>
> 'git fetch' Linus' tree and look at the tags. 'v4.16' lost its '-rc' suffixes,
> and there isn't a 'v4.17-rc1' yet, so we are still in the merge window.
>
> Linus sends a message to
Colin,
> Rename macros MPI_FCPORTPAGE0_SUPPORT_SPEED_UKNOWN and
> MPI_FCPORTPAGE0_CURRENT_SPEED_UKNOWN to add in missing N in UNKNOWN
Applied to 4.18/scsi-queue. Thanks.
--
Martin K. Petersen Oracle Linux Engineering
Colin,
> Rename macros MPI_FCPORTPAGE0_SUPPORT_SPEED_UKNOWN and
> MPI_FCPORTPAGE0_CURRENT_SPEED_UKNOWN to add in missing N in UNKNOWN
Applied to 4.18/scsi-queue. Thanks.
--
Martin K. Petersen Oracle Linux Engineering
On Thu, 19 Apr 2018, at 12:22, Joel Stanley wrote:
> The ast2500 has an additional reset register that contains resets not
> present in the ast2400. This enables support for this register, and adds
> the one reset line that is controlled by it.
>
> Signed-off-by: Joel Stanley
On Thu, 19 Apr 2018, at 12:22, Joel Stanley wrote:
> The ast2500 has an additional reset register that contains resets not
> present in the ast2400. This enables support for this register, and adds
> the one reset line that is controlled by it.
>
> Signed-off-by: Joel Stanley
The duplication is
The initializing of q->root_blkg is currently outside of queue lock
and rcu, so the blkg may be destroied before the initializing, which
may cause dangling/null references. On the other side, the destroys
of blkg are protected by queue lock or rcu. Put the initializing
inside the queue lock and
The initializing of q->root_blkg is currently outside of queue lock
and rcu, so the blkg may be destroied before the initializing, which
may cause dangling/null references. On the other side, the destroys
of blkg are protected by queue lock or rcu. Put the initializing
inside the queue lock and
The comment before blkg_create() in blkcg_init_queue() was moved
from blkcg_activate_policy() by commit ec13b1d6f0a0457312e615, but
it does not suit for the new context.
Signed-off-by: Jiang Biao
Signed-off-by: Wen Yang
CC: Tejun Heo
The comment before blkg_create() in blkcg_init_queue() was moved
from blkcg_activate_policy() by commit ec13b1d6f0a0457312e615, but
it does not suit for the new context.
Signed-off-by: Jiang Biao
Signed-off-by: Wen Yang
CC: Tejun Heo
CC: Jens Axboe
---
block/blk-cgroup.c | 6 +-
1 file
When longer interface names are used, the action names exposed in
/proc/interrupts and /proc/irq/* maybe truncated. For example, when
using the predictable name algorithm in systemd on a HiSilicon D05,
I see:
ubuntu@d05-3:~$ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //'
When longer interface names are used, the action names exposed in
/proc/interrupts and /proc/irq/* maybe truncated. For example, when
using the predictable name algorithm in systemd on a HiSilicon D05,
I see:
ubuntu@d05-3:~$ grep enahisic2i0-tx /proc/interrupts | sed 's/.* //'
On Wed, Apr 18, 2018 at 01:38:43PM -0700, Eric Dumazet wrote:
>
>
> On 04/18/2018 10:55 AM, Michael S. Tsirkin wrote:
>
> > Imagine you want to pass some data to card.
> > Natural thing is to just put it in a variable and start DMA.
> > However DMA API disallows stack access nowdays,
> > so
On Wed, Apr 18, 2018 at 01:38:43PM -0700, Eric Dumazet wrote:
>
>
> On 04/18/2018 10:55 AM, Michael S. Tsirkin wrote:
>
> > Imagine you want to pass some data to card.
> > Natural thing is to just put it in a variable and start DMA.
> > However DMA API disallows stack access nowdays,
> > so
On Wed, 2018-04-18 at 20:18 -0700, Stephen Boyd wrote:
> Quoting sean.w...@mediatek.com (2018-04-18 03:24:54)
> > From: Sean Wang
> >
> > Add bindings to g3dsys providing necessary clock and reset control to
> > Mali-450.
> >
> > Signed-off-by: Sean Wang
On Wed, 2018-04-18 at 20:18 -0700, Stephen Boyd wrote:
> Quoting sean.w...@mediatek.com (2018-04-18 03:24:54)
> > From: Sean Wang
> >
> > Add bindings to g3dsys providing necessary clock and reset control to
> > Mali-450.
> >
> > Signed-off-by: Sean Wang
> > ---
> >
Marcos Paulo de Souza writes:
> Found while inspecting the code that handles the setgroups procfs
> file.
What perchance might be the advantage of introducing multiple exits
into proc_setgroups_write?
I strongly suspect that if you look at the generated code it will
Marcos Paulo de Souza writes:
> Found while inspecting the code that handles the setgroups procfs
> file.
What perchance might be the advantage of introducing multiple exits
into proc_setgroups_write?
I strongly suspect that if you look at the generated code it will
be worse after your patch.
On Wed, Apr 11, 2018 at 08:28:32PM +0200, Jan Glauber wrote:
>
> @@ -1362,7 +1373,17 @@ static int test_comp(struct crypto_comp *tfm,
> goto out;
> }
>
> - if (dlen != ctemplate[i].outlen) {
> + ilen = dlen;
> + dlen =
On Wed, Apr 11, 2018 at 08:28:32PM +0200, Jan Glauber wrote:
>
> @@ -1362,7 +1373,17 @@ static int test_comp(struct crypto_comp *tfm,
> goto out;
> }
>
> - if (dlen != ctemplate[i].outlen) {
> + ilen = dlen;
> + dlen =
Long,
> Can you take a look at the following patch?
>> > + max_sub_channels =
>> > + (num_cpus - 1) / storvsc_vcpus_per_sub_channel;
What happens if num_cpus = 1?
--
Martin K. Petersen Oracle Linux Engineering
Long,
> Can you take a look at the following patch?
>> > + max_sub_channels =
>> > + (num_cpus - 1) / storvsc_vcpus_per_sub_channel;
What happens if num_cpus = 1?
--
Martin K. Petersen Oracle Linux Engineering
On Mon, Apr 09, 2018 at 11:42:31AM +0300, Gilad Ben-Yossef wrote:
>
> Please look again. The stub version of cc_is_hw_key() doing that is being
> replaced in this patch.
The point is that the existing mechanism was unused before and this
is new code. So you can't really point to the stubbed-out
On Mon, Apr 09, 2018 at 11:42:31AM +0300, Gilad Ben-Yossef wrote:
>
> Please look again. The stub version of cc_is_hw_key() doing that is being
> replaced in this patch.
The point is that the existing mechanism was unused before and this
is new code. So you can't really point to the stubbed-out
On Tue, Jan 02, 2018 at 03:58:01PM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 61233580f1f33c50e159c50e24d80ffd2ba2e06b
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console
On Tue, Jan 02, 2018 at 03:58:01PM -0800, syzbot wrote:
> Hello,
>
> syzkaller hit the following crash on
> 61233580f1f33c50e159c50e24d80ffd2ba2e06b
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/master
> compiler: gcc (GCC) 7.1.1 20170620
> .config is attached
> Raw console
On Thu, Apr 19, 2018 at 12:54:16AM +, Dey, Megha wrote:
>
> Yeah I think I misunderstood. I think what you mean is to remove mcryptd.c
> completely and avoid the extra layer of indirection to call the underlying
> algorithm, instead call it directly, correct?
>
> So currently we have 3
On Thu, Apr 19, 2018 at 12:54:16AM +, Dey, Megha wrote:
>
> Yeah I think I misunderstood. I think what you mean is to remove mcryptd.c
> completely and avoid the extra layer of indirection to call the underlying
> algorithm, instead call it directly, correct?
>
> So currently we have 3
Anson Huang
Best Regards!
> -Original Message-
> From: Stephen Boyd [mailto:sb...@kernel.org]
> Sent: Thursday, April 19, 2018 11:18 AM
> To: Anson Huang ; Shawn Guo
>
> Cc: mark.rutl...@arm.com; devicet...@vger.kernel.org;
>
Anson Huang
Best Regards!
> -Original Message-
> From: Stephen Boyd [mailto:sb...@kernel.org]
> Sent: Thursday, April 19, 2018 11:18 AM
> To: Anson Huang ; Shawn Guo
>
> Cc: mark.rutl...@arm.com; devicet...@vger.kernel.org;
> mturque...@baylibre.com; linux-...@vger.kernel.org;
On Thu, Apr 19, 2018 at 08:56:28AM +1000, NeilBrown wrote:
>
> I don't want to do that - I just want the documentation to be correct
> (or at least, not be blatantly incorrect). The function does not sleep,
> and is safe to call with spin locks held.
> Do we need to spell out when it can be
On Thu, Apr 19, 2018 at 08:56:28AM +1000, NeilBrown wrote:
>
> I don't want to do that - I just want the documentation to be correct
> (or at least, not be blatantly incorrect). The function does not sleep,
> and is safe to call with spin locks held.
> Do we need to spell out when it can be
Quoting sean.w...@mediatek.com (2018-04-18 03:24:54)
> From: Sean Wang
>
> Add bindings to g3dsys providing necessary clock and reset control to
> Mali-450.
>
> Signed-off-by: Sean Wang
> ---
> .../bindings/arm/mediatek/mediatek,g3dsys.txt
Quoting sean.w...@mediatek.com (2018-04-18 03:24:54)
> From: Sean Wang
>
> Add bindings to g3dsys providing necessary clock and reset control to
> Mali-450.
>
> Signed-off-by: Sean Wang
> ---
> .../bindings/arm/mediatek/mediatek,g3dsys.txt | 30
> ++
Why isn't this
1 - 100 of 1686 matches
Mail list logo