On Mon, May 07, 2018 at 04:59:11PM -0400, Waiman Long wrote:
> diff --git a/ipc/ipc_sysctl.c b/ipc/ipc_sysctl.c
> index 49f9bf4..d62335f 100644
> --- a/ipc/ipc_sysctl.c
> +++ b/ipc/ipc_sysctl.c
> @@ -120,7 +120,8 @@ static int proc_ipc_sem_dointvec(struct ctl_table *table,
> int write,
> static
On Mon, May 07, 2018 at 04:59:09PM -0400, Waiman Long wrote:
> A user can write arbitrary integer values to msgmni and shmmni sysctl
> parameters without getting error, but the actual limit is really
> IPCMNI (32k). This can mislead users as they think they can get a
> value that is not real.
>
>
On 05/02/2018 11:06 AM, Eric W. Biederman wrote:
>
>>> and or users that may or may not exist. If you can find something that
>>> will care sure. We need to avoid breaking userspace and causing
>>> regressions. However as this stands it looks you are making maintenance
>>> of the kernel more
+ Robert Schwebel (who thankfully did the txt -> rst conversion for can.txt)
On 05/07/2018 11:35 AM, Mauro Carvalho Chehab wrote:
> As stated at:
>
> http://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html#footnotes
>
> A footnote should contain either a number, a reference
Le 18/04/2018 à 03:08, Alastair D'Silva a écrit :
From: Alastair D'Silva
Signed-off-by: Alastair D'Silva
---
Acked-by: Frederic Barrat
Fred
Documentation/accelerators/ocxl.rst | 11 +++
1 file
Le 18/04/2018 à 03:08, Alastair D'Silva a écrit :
From: Alastair D'Silva
In order for a userspace AFU driver to call the Power9 specific
OCXL_IOCTL_ENABLE_P9_WAIT, it needs to verify that it can actually
make that call.
Signed-off-by: Alastair D'Silva
Le 18/04/2018 à 03:08, Alastair D'Silva a écrit :
From: Alastair D'Silva
In order to successfully issue as_notify, an AFU needs to know the TID
to notify, which in turn means that this information should be
available in userspace so it can be communicated to the AFU.
Le 18/04/2018 à 03:08, Alastair D'Silva a écrit :
From: Alastair D'Silva
The function removes the process element from NPU cache.
Signed-off-by: Alastair D'Silva
---
Acked-by: Frederic Barrat
Le 18/04/2018 à 03:08, Alastair D'Silva a écrit :
From: Alastair D'Silva
The current implementation of TID allocation, using a global IDR, may
result in an errant process starving the system of available TIDs.
Instead, use task_pid_nr(), as mentioned by the original
Le 18/04/2018 à 03:08, Alastair D'Silva a écrit :
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: Frederic Barrat
Le 18/04/2018 à 03:08, Alastair D'Silva a écrit :
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
---
On Mon, 7 May 2018 06:35:51 -0300
Mauro Carvalho Chehab wrote:
> Solve those Sphinx warnings:
>
> ./include/linux/iio/iio.h:270: warning: Function parameter or member
> 'scan_type.sign' not described in 'iio_chan_spec'
> ./include/linux/iio/iio.h:270:
On Mon, 7 May 2018 13:51:21 +0530
Ravi Bangoria wrote:
> Hi Masami,
>
> On 05/04/2018 07:51 PM, Ravi Bangoria wrote:
> >
> >>> +}
> >>> +
> >>> +static void sdt_increment_ref_ctr(struct trace_uprobe *tu)
> >>> +{
> >>> + struct uprobe_map_info *info;
> >>> +
> >>> +
On 2018-05-07 08:49:08 [-0700], Tejun Heo wrote:
> Hello, Sebastian.
>
> On Fri, May 04, 2018 at 05:06:20PM +0200, Sebastian Andrzej Siewior wrote:
> > ata_sff_data_xfer_noirq() is invoked via the ->sff_data_xfer hook. The
> > latter is invoked by ata_pio_sector(), atapi_send_cdb() and
> >
Hello, Sebastian.
On Fri, May 04, 2018 at 05:06:20PM +0200, Sebastian Andrzej Siewior wrote:
> ata_sff_data_xfer_noirq() is invoked via the ->sff_data_xfer hook. The
> latter is invoked by ata_pio_sector(), atapi_send_cdb() and
> __atapi_pio_bytes() which in turn is invoked by ata_sff_hsm_move().
On Mon, May 07, 2018 at 06:35:46AM -0300, Mauro Carvalho Chehab wrote:
> The code example at rcupdate.h currently produce lots of warnings:
>
> ./include/linux/rcupdate.h:572: WARNING: Unexpected indentation.
> ./include/linux/rcupdate.h:576: WARNING: Unexpected indentation.
>
On Mon, 2018-05-07 at 15:37 +0300, Kalle Valo wrote:
> Mauro Carvalho Chehab writes:
>
> > Sphinx produces a lot of errors like this:
> > ./include/net/mac80211.h:2083: warning: bad line: >
> >
> > Signed-off-by: Mauro Carvalho Chehab
Mauro Carvalho Chehab writes:
> Sphinx produces a lot of errors like this:
> ./include/net/mac80211.h:2083: warning: bad line: >
>
> Signed-off-by: Mauro Carvalho Chehab
Randy already submitted a similar patch:
On Mon, May 07, 2018 at 06:35:43AM -0300, Mauro Carvalho Chehab wrote:
> The circular-buffers.txt is already in ReST format. So, move it to the
> core-api guide, where it belongs.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/00-INDEX
On Mon, May 07, 2018 at 06:35:41AM -0300, Mauro Carvalho Chehab wrote:
> The cachetlb.txt is already in ReST format. So, move it to the
> core-api guide, where it belongs.
>
> Signed-off-by: Mauro Carvalho Chehab
> ---
> Documentation/00-INDEX
Hi Boris,
Em Mon, 7 May 2018 11:46:50 +0200
Boris Brezillon escreveu:
> Hi Mauro,
> > diff --git a/include/linux/mtd/rawnand.h b/include/linux/mtd/rawnand.h
> > index 5dad59b31244..b986f94906df 100644
> > --- a/include/linux/mtd/rawnand.h
> > +++
Hi Mauro,
On Mon, 7 May 2018 06:35:52 -0300
Mauro Carvalho Chehab wrote:
> Gets rid of those warnings and better document the parameters.
>
> ./include/linux/mtd/rawnand.h:752: warning: Function parameter or member
> 'timings.sdr' not described in
Hi Masami,
On 05/04/2018 07:51 PM, Ravi Bangoria wrote:
>
>>> +}
>>> +
>>> +static void sdt_increment_ref_ctr(struct trace_uprobe *tu)
>>> +{
>>> + struct uprobe_map_info *info;
>>> +
>>> + uprobe_down_write_dup_mmap();
>>> + info = uprobe_build_map_info(tu->inode->i_mapping,
>>> +
On Mon, 7 May 2018 11:02:10 +0800
"dongbo (E)" wrote:
> From: Dong Bo
>
> Update vfio_add_group_dev description to match the current API.
>
> Signed-off-by: Dong Bo
> ---
> Documentation/vfio.txt | 5 ++---
> 1 file changed, 2
Hi, Alex.
On 2018/5/1 2:38, Alex Williamson wrote:
> On Fri, 20 Apr 2018 18:07:27 +0800
> "dongbo (E)" wrote:
>
>> From: Dong Bo
>>
>> Signed-off-by: Dong Bo
>> ---
>
> Hi Dong Bo,
>
> The patch is corrupted, please resend and also
> -Original Message-
> From: Randy Dunlap [mailto:rdun...@infradead.org]
> Sent: Monday, May 07, 2018 2:50 AM
> To: linux-bl...@vger.kernel.org; axboe
> Cc: LKML ; Caizhiyong
> ; Andrew Morton
On Sun, May 6, 2018 at 2:31 PM, Paul Moore wrote:
> On Thu, May 3, 2018 at 9:08 PM, Tyler Hicks wrote:
>> Seccomp received improved logging controls in v4.14. Applications can opt
>> into
>> logging of "handled" actions (SECCOMP_RET_TRAP,
On Thu, May 3, 2018 at 9:08 PM, Tyler Hicks wrote:
> Seccomp received improved logging controls in v4.14. Applications can opt into
> logging of "handled" actions (SECCOMP_RET_TRAP, SECCOMP_RET_TRACE,
> SECCOMP_RET_ERRNO) using the SECCOMP_FILTER_FLAG_LOG bit when loading
On Fri, May 04, 2018 at 02:13:59PM -0700, Kees Cook wrote:
> On Fri, May 4, 2018 at 2:11 PM, Andrea Parri
> wrote:
> > The LKMM project has moved to 'tools/memory-model/'.
> >
> > Signed-off-by: Andrea Parri
> > ---
> >
On Fri, May 4, 2018 at 2:11 PM, Andrea Parri
wrote:
> The LKMM project has moved to 'tools/memory-model/'.
>
> Signed-off-by: Andrea Parri
> ---
> Documentation/core-api/refcount-vs-atomic.rst | 2 +-
> 1 file changed, 1
On Thursday, May 3, 2018 9:08:14 PM EDT Tyler Hicks wrote:
> The decision to log a seccomp action will always be subject to the
> value of the kernel.seccomp.actions_logged sysctl, even for processes
> that are being inspected via the audit subsystem, in an upcoming patch.
> Therefore, we need to
t = thunderx2_uncore_event_init,
>> + .add= thunderx2_uncore_add,
>> + .del= thunderx2_uncore_del,
>> + .start = thunderx2_uncore_start,
>> + .stop = thunderx2_uncore_stop,
>> +
Hi Kim,
On 04/05/18 01:30, Kim Phillips wrote:
On Tue, 1 May 2018 12:54:05 +0100
Will Deacon wrote:
Hi Kim,
Hi Will, thanks for responding.
On Fri, Apr 27, 2018 at 11:56:25AM -0500, Kim Phillips wrote:
On Fri, 27 Apr 2018 17:09:14 +0100
Will Deacon
Sorry Ravi, I saved the new version for review and forgot about it... I'll
try to do this on weekend.
On 05/03, Ravi Bangoria wrote:
>
> On 04/17/2018 10:02 AM, Ravi Bangoria wrote:
> > Userspace Statically Defined Tracepoints[1] are dtrace style markers
> > inside userspace applications.
Hi Masami,
On 05/04/2018 10:18 AM, Masami Hiramatsu wrote:
>> +void uprobe_down_write_dup_mmap(void)
>> +{
>> +percpu_down_write(_mmap_sem);
>> +}
>> +
>> +void uprobe_up_write_dup_mmap(void)
>> +{
>> +percpu_up_write(_mmap_sem);
>> +}
>> +
> I'm not sure why these hunks are not done in
Em Fri, 04 May 2018 13:58:39 +0300
Jani Nikula escreveu:
> On Fri, 04 May 2018, Mauro Carvalho Chehab wrote:
> > From now on, I'll start using my @kernel.org as my development e-mail.
> >
> > As such, let's remove the entries that point
On Fri, 04 May 2018, Mauro Carvalho Chehab wrote:
> From now on, I'll start using my @kernel.org as my development e-mail.
>
> As such, let's remove the entries that point to the old
> mche...@s-opensource.com at MAINTAINERS file.
>
> For the files written with a
Hi Ravi,
I have some comments, please see below.
On Tue, 17 Apr 2018 10:02:41 +0530
Ravi Bangoria wrote:\
> diff --git a/include/linux/uprobes.h b/include/linux/uprobes.h
> index 7bd2760..2db3ed1 100644
> --- a/include/linux/uprobes.h
> +++
On Tue, 1 May 2018 12:54:05 +0100
Will Deacon wrote:
> Hi Kim,
Hi Will, thanks for responding.
> On Fri, Apr 27, 2018 at 11:56:25AM -0500, Kim Phillips wrote:
> > On Fri, 27 Apr 2018 17:09:14 +0100
> > Will Deacon wrote:
> > > On Fri, Apr 27, 2018 at
On Thursday, May 3, 2018 6:36:18 PM EDT Tyler Hicks wrote:
> On 05/03/2018 04:12 PM, Steve Grubb wrote:
> > On Thursday, May 3, 2018 4:51:36 PM EDT Tyler Hicks wrote:
> >> On 05/03/2018 03:48 PM, Paul Moore wrote:
> >>> On Thu, May 3, 2018 at 4:42 PM, Steve Grubb wrote:
>
On 05/03/2018 04:12 PM, Steve Grubb wrote:
> On Thursday, May 3, 2018 4:51:36 PM EDT Tyler Hicks wrote:
>> On 05/03/2018 03:48 PM, Paul Moore wrote:
>>> On Thu, May 3, 2018 at 4:42 PM, Steve Grubb wrote:
On Thursday, May 3, 2018 4:18:26 PM EDT Paul Moore wrote:
> On
On Thursday, May 3, 2018 4:51:36 PM EDT Tyler Hicks wrote:
> On 05/03/2018 03:48 PM, Paul Moore wrote:
> > On Thu, May 3, 2018 at 4:42 PM, Steve Grubb wrote:
> >> On Thursday, May 3, 2018 4:18:26 PM EDT Paul Moore wrote:
> >>> On Wed, May 2, 2018 at 2:18 PM, Steve Grubb
On 05/03/2018 03:48 PM, Paul Moore wrote:
> On Thu, May 3, 2018 at 4:42 PM, Steve Grubb wrote:
>> On Thursday, May 3, 2018 4:18:26 PM EDT Paul Moore wrote:
>>> On Wed, May 2, 2018 at 2:18 PM, Steve Grubb wrote:
On Wednesday, May 2, 2018 11:53:19 AM EDT
On Thu, May 3, 2018 at 4:42 PM, Steve Grubb wrote:
> On Thursday, May 3, 2018 4:18:26 PM EDT Paul Moore wrote:
>> On Wed, May 2, 2018 at 2:18 PM, Steve Grubb wrote:
>> > On Wednesday, May 2, 2018 11:53:19 AM EDT Tyler Hicks wrote:
>> >> The decision to log a
On Thursday, May 3, 2018 4:18:26 PM EDT Paul Moore wrote:
> On Wed, May 2, 2018 at 2:18 PM, Steve Grubb wrote:
> > On Wednesday, May 2, 2018 11:53:19 AM EDT Tyler Hicks wrote:
> >> The decision to log a seccomp action will always be subject to the
> >> value of the
On Wed, May 2, 2018 at 2:18 PM, Steve Grubb wrote:
> On Wednesday, May 2, 2018 11:53:19 AM EDT Tyler Hicks wrote:
>> The decision to log a seccomp action will always be subject to the
>> value of the kernel.seccomp.actions_logged sysctl, even for processes
>> that are being
On Thu, May 3, 2018 at 5:24 PM, Kirill A. Shutemov wrote:
> On Thu, May 03, 2018 at 04:09:56PM +0200, Andrey Konovalov wrote:
>> On Wed, May 2, 2018 at 7:25 PM, Andrey Konovalov
>> wrote:
>> I wasn't able to find anything that calls follow_page with
On Thu, May 03, 2018 at 04:09:56PM +0200, Andrey Konovalov wrote:
> On Wed, May 2, 2018 at 7:25 PM, Andrey Konovalov
> wrote:
> > On Wed, May 2, 2018 at 5:36 PM, Kirill A. Shutemov
> > wrote:
> >> On Wed, May 02, 2018 at 02:38:42PM +,
On Tue, 17 Apr 2018 10:02:37 +0530
Ravi Bangoria wrote:
> From: Ravi Bangoria
>
> Make function names more meaningful by adding vma_ prefix
> to them.
Actually, I would have done this patch before the first one, since the
first
On Tue, 17 Apr 2018 10:02:43 +0530
Ravi Bangoria wrote:
> From: Ravi Bangoria
>
> Reference counter gate the invocation of probe. If present,
> by default reference count is 0. Kernel needs to increment
> it before tracing the
On Tue, 17 Apr 2018 10:02:44 +0530
Ravi Bangoria wrote:
> From: Ravi Bangoria
>
> With this, perf buildid-cache will save SDT markers with reference
> counter in probe cache. Perf probe will be able to probe markers
> having
On Wed, May 2, 2018 at 7:25 PM, Andrey Konovalov wrote:
> On Wed, May 2, 2018 at 5:36 PM, Kirill A. Shutemov
> wrote:
>> On Wed, May 02, 2018 at 02:38:42PM +, Andrey Konovalov wrote:
>>> > Does having a tagged address here makes any
On 04/17/2018 10:02 AM, Ravi Bangoria wrote:
> Userspace Statically Defined Tracepoints[1] are dtrace style markers
> inside userspace applications. Applications like PostgreSQL, MySQL,
> Pthread, Perl, Python, Java, Ruby, Node.js, libvirt, QEMU, glib etc
> have these markers embedded in them.
On Wed, May 2, 2018 at 12:57 PM, Kees Cook wrote:
> On Wed, May 2, 2018 at 8:53 AM, Tyler Hicks wrote:
>> diff --git a/kernel/seccomp.c b/kernel/seccomp.c
>> index da78835..9029d9d 100644
>> --- a/kernel/seccomp.c
>> +++ b/kernel/seccomp.c
>> @@
On Wed, 2 May 2018, Tyler Hicks wrote:
> type=CONFIG_CHANGE msg=audit(1525275325.613:142): op=seccomp-logging
> actions=kill_process,kill_thread,errno,trace,log
> old-actions=kill_process,kill_thread,errno,trace,log res=1
>
> No audit records are generated when reading the actions_logged
On Wed, 2 May 2018, Tyler Hicks wrote:
> The function that converts a bitmask of seccomp actions that are
> allowed to be logged is currently only used for constructing the display
> string for the kernel.seccomp.actions_logged sysctl. That string wants a
> space character to be used for the
On Wed, 2 May 2018, Tyler Hicks wrote:
> Break the read and write paths of the kernel.seccomp.actions_logged
> sysctl into separate functions to maintain readability. An upcoming
> change will need to audit writes, but not reads, of this sysctl which
> would introduce too many conditional code
On Wednesday, May 2, 2018 11:53:19 AM EDT Tyler Hicks wrote:
> The decision to log a seccomp action will always be subject to the
> value of the kernel.seccomp.actions_logged sysctl, even for processes
> that are being inspected via the audit subsystem, in an upcoming patch.
> Therefore, we need
On Wed, May 2, 2018 at 5:36 PM, Kirill A. Shutemov
wrote:
> On Wed, May 02, 2018 at 02:38:42PM +, Andrey Konovalov wrote:
>> > Does having a tagged address here makes any difference? I couldn't hit a
>> > failure with my simple tests (LD_PRELOAD a library that
Daniel Vetter writes:
> This came up in discussions when reviewing drm patches.
>
> Cc: Eric Anholt
> Cc: linux-doc@vger.kernel.org
> Cc: Jonathan Corbet
> Signed-off-by: Daniel Vetter
>
> --
>
> Aside: I wonder
On Wed, May 2, 2018 at 8:53 AM, Tyler Hicks wrote:
> diff --git a/kernel/seccomp.c b/kernel/seccomp.c
> index da78835..9029d9d 100644
> --- a/kernel/seccomp.c
> +++ b/kernel/seccomp.c
> @@ -584,18 +584,13 @@ static inline void seccomp_log(unsigned long syscall,
> long
On 1 May 2018 at 23:00, Leo Yan wrote:
> The driver prints pcsr twice: the first time it uses specifier %px to
> print hexadecimal pcsr value and the second time uses specifier %pS for
> output kernel symbols.
>
> As suggested by Kees, using %pS should be sufficient and %px
On 05/01/2018 12:25 PM, Paul Moore wrote:
> On Tue, May 1, 2018 at 12:41 PM, Steve Grubb wrote:
>> On Tuesday, May 1, 2018 11:18:55 AM EDT Paul Moore wrote:
>>> On Fri, Apr 27, 2018 at 3:16 PM, Tyler Hicks wrote:
The decision to log a seccomp action
On Wed, May 02, 2018 at 02:38:42PM +, Andrey Konovalov wrote:
> > Does having a tagged address here makes any difference? I couldn't hit a
> > failure with my simple tests (LD_PRELOAD a library that randomly adds
> > tags to pointers returned by malloc).
>
> I think you're right,
On Thu, Apr 26, 2018 at 5:47 PM, Catalin Marinas
wrote:
> On Wed, Apr 18, 2018 at 08:53:12PM +0200, Andrey Konovalov wrote:
>> @@ -238,12 +239,15 @@ static inline void uaccess_enable_not_uao(void)
>> /*
>> * Sanitise a uaccess pointer such that it becomes NULL if above
Waiman Long writes:
> On 05/01/2018 10:18 PM, Eric W. Biederman wrote:
>>
>>> The sysctl parameters msgmni, shmmni and semmni have an inherent limit
>>> of IPC_MNI (32k). However, users may not be aware of that because they
>>> can write a value much higher than that without
On Thu, Apr 26, 2018 at 7:47 PM, Catalin Marinas
wrote:
My approach with this was to add untagging to every gup.c function
that is exposed for external use, but perhaps adding untagging only
where it is actually required is a better approach.
> On Wed, Apr 18, 2018 at
On Wed, 2018-05-02 at 16:02 +0200, Peter Zijlstra wrote:
> On Wed, May 02, 2018 at 09:47:00AM -0400, Waiman Long wrote:
>
> > > I've read half of the next patch that adds the isolation thing. And
> > > while that kludges around the whole root cgorup is magic thing, it
> > > doesn't help if you
On Thu, Apr 19, 2018 at 09:47:02AM -0400, Waiman Long wrote:
> diff --git a/Documentation/cgroup-v2.txt b/Documentation/cgroup-v2.txt
> index c970bd7..8d89dc2 100644
> --- a/Documentation/cgroup-v2.txt
> +++ b/Documentation/cgroup-v2.txt
> @@ -1484,6 +1484,31 @@ Cpuset Interface Files
> a
On Wed, May 02, 2018 at 09:47:00AM -0400, Waiman Long wrote:
> > I've read half of the next patch that adds the isolation thing. And
> > while that kludges around the whole root cgorup is magic thing, it
> > doesn't help if you move the above scenario on level down:
> >
> >
> > R
> > /
On 05/02/2018 09:42 AM, Peter Zijlstra wrote:
> On Wed, May 02, 2018 at 09:29:54AM -0400, Waiman Long wrote:
>> On 05/02/2018 06:24 AM, Peter Zijlstra wrote:
>>> On Thu, Apr 19, 2018 at 09:47:01AM -0400, Waiman Long wrote:
+ cpuset.sched_load_balance
+ A read-write single value file
On Wed, May 02, 2018 at 09:29:54AM -0400, Waiman Long wrote:
> On 05/02/2018 06:24 AM, Peter Zijlstra wrote:
> > On Thu, Apr 19, 2018 at 09:47:01AM -0400, Waiman Long wrote:
> >> + cpuset.sched_load_balance
> >> + A read-write single value file which exists on non-root cgroups.
> > Uhhm.. it
On 05/02/2018 06:24 AM, Peter Zijlstra wrote:
> On Thu, Apr 19, 2018 at 09:47:01AM -0400, Waiman Long wrote:
>> + cpuset.sched_load_balance
>> +A read-write single value file which exists on non-root cgroups.
> Uhhm.. it should very much exist in the root group too. Otherwise you
> cannot
On 05/01/2018 10:18 PM, Eric W. Biederman wrote:
>
>> The sysctl parameters msgmni, shmmni and semmni have an inherent limit
>> of IPC_MNI (32k). However, users may not be aware of that because they
>> can write a value much higher than that without getting any error or
>> notification. Reading
On Thu, Apr 26, 2018 at 6:42 PM, Bartosz Golaszewski wrote:
> 2018-04-26 14:07 GMT+02:00 Linus Walleij :
>> On Tue, Apr 10, 2018 at 10:30 PM, Bartosz Golaszewski wrote:
>>
>>> Board files constitute a significant part of the users of the
Hi Greg,
On Wed, May 2, 2018 at 1:10 PM, Greg Kroah-Hartman
wrote:
> On Wed, May 02, 2018 at 11:47:49AM +0200, Geert Uytterhoeven wrote:
>> On Sun, Apr 29, 2018 at 3:37 PM, Greg Kroah-Hartman
>> wrote:
>> > On Fri, Mar 30, 2018 at
On Wed, May 02, 2018 at 11:47:49AM +0200, Geert Uytterhoeven wrote:
> Hi Greg,
>
> On Sun, Apr 29, 2018 at 3:37 PM, Greg Kroah-Hartman
> wrote:
> > On Fri, Mar 30, 2018 at 09:47:44AM +0200, Boris Brezillon wrote:
> >> Document sysfs files/directories/symlinks exposed
On Thu, Apr 19, 2018 at 09:47:01AM -0400, Waiman Long wrote:
> + cpuset.sched_load_balance
> + A read-write single value file which exists on non-root cgroups.
Uhhm.. it should very much exist in the root group too. Otherwise you
cannot disable it there, which is required to allow smaller
Hi Greg,
On Sun, Apr 29, 2018 at 3:37 PM, Greg Kroah-Hartman
wrote:
> On Fri, Mar 30, 2018 at 09:47:44AM +0200, Boris Brezillon wrote:
>> Document sysfs files/directories/symlinks exposed by the I3C subsystem.
>>
>> Signed-off-by: Boris Brezillon
On Tue, May 01, 2018 at 10:29:46PM -0700, Kees Cook wrote:
> On Tue, May 1, 2018 at 10:00 PM, Leo Yan wrote:
> > The driver prints pcsr twice: the first time it uses specifier %px to
> > print hexadecimal pcsr value and the second time uses specifier %pS for
> > output kernel
On Tue, May 1, 2018 at 10:00 PM, Leo Yan wrote:
> The driver prints pcsr twice: the first time it uses specifier %px to
> print hexadecimal pcsr value and the second time uses specifier %pS for
> output kernel symbols.
>
> As suggested by Kees, using %pS should be sufficient
> The sysctl parameters msgmni, shmmni and semmni have an inherent limit
> of IPC_MNI (32k). However, users may not be aware of that because they
> can write a value much higher than that without getting any error or
> notification. Reading the parameters back will show the newly written
>
On 05/01/2018 04:58 PM, Tejun Heo wrote:
> Hello,
>
> On Tue, May 01, 2018 at 04:33:45PM -0400, Waiman Long wrote:
>> I think that will work too. We currently don't have a flag to make a
>> file visible on first-level children only, but it shouldn't be hard to
>> make one.
> I think it'd be fine
Hello,
On Tue, May 01, 2018 at 04:33:45PM -0400, Waiman Long wrote:
> I think that will work too. We currently don't have a flag to make a
> file visible on first-level children only, but it shouldn't be hard to
> make one.
I think it'd be fine to make the flag file exist on all !root cgroups
On 05/01/2018 03:51 PM, Tejun Heo wrote:
> Hello, Waiman.
>
> Sorry about the delay.
>
> On Thu, Apr 19, 2018 at 09:47:03AM -0400, Waiman Long wrote:
>> With the addition of "cpuset.cpus.isolated", it makes sense to add the
>> restriction that load balancing can only be turned off if the CPUs in
Hello, Waiman.
Sorry about the delay.
On Thu, Apr 19, 2018 at 09:47:03AM -0400, Waiman Long wrote:
> With the addition of "cpuset.cpus.isolated", it makes sense to add the
> restriction that load balancing can only be turned off if the CPUs in
> the isolated cpuset are subset of
On Tue, May 1, 2018 at 12:41 PM, Steve Grubb wrote:
> On Tuesday, May 1, 2018 11:18:55 AM EDT Paul Moore wrote:
>> On Fri, Apr 27, 2018 at 3:16 PM, Tyler Hicks wrote:
>> > The decision to log a seccomp action will always be subject to the
>> > value of
On Tuesday, May 1, 2018 11:18:55 AM EDT Paul Moore wrote:
> On Fri, Apr 27, 2018 at 3:16 PM, Tyler Hicks wrote:
> > The decision to log a seccomp action will always be subject to the
> > value of the kernel.seccomp.actions_logged sysctl, even for processes
> > that are
On Fri, Apr 27, 2018 at 3:16 PM, Tyler Hicks wrote:
> Seccomp logging for "handled" actions such as RET_TRAP, RET_TRACE, or
> RET_ERRNO can be very noisy for processes that are being audited. This
> patch modifies the seccomp logging behavior to treat processes that are
>
On Fri, Apr 27, 2018 at 3:16 PM, Tyler Hicks wrote:
> The decision to log a seccomp action will always be subject to the
> value of the kernel.seccomp.actions_logged sysctl, even for processes
> that are being inspected via the audit subsystem, in an upcoming patch.
>
On 04/30/2018 06:40 PM, Kees Cook wrote:
> I like this series overall, thanks! No objections from me. One thing I
> noted, though:
>
> On Fri, Apr 27, 2018 at 2:00 PM, Waiman Long wrote:
>> if (param->min && *param->min > val) {
>> if
Hi Kim,
On Fri, Apr 27, 2018 at 11:56:25AM -0500, Kim Phillips wrote:
> On Fri, 27 Apr 2018 17:09:14 +0100
> Will Deacon wrote:
> > On Fri, Apr 27, 2018 at 10:46:29AM -0500, Kim Phillips wrote:
> > > On Fri, 27 Apr 2018 15:37:20 +0100
> > > Will Deacon
I like this series overall, thanks! No objections from me. One thing I
noted, though:
On Fri, Apr 27, 2018 at 2:00 PM, Waiman Long wrote:
> if (param->min && *param->min > val) {
> if (clamp) {
> val =
On Fri, 20 Apr 2018 18:07:27 +0800
"dongbo (E)" wrote:
> From: Dong Bo
>
> Signed-off-by: Dong Bo
> ---
Hi Dong Bo,
The patch is corrupted, please resend and also include a commit log,
something as simple as "Update
On Mon, 30 Apr 2018 11:50:04 +1000
NeilBrown wrote:
> This patch simplifies the interface for first/next iteration and
> simplifies the code, while maintaining complete backward
> compatability. Now:
>
> - if ->start() is given a pos of zero, it should return an iterator
>
Hi Alan,
On 30/04/2018 16:35, Alan Douglas wrote:
> Hi Gustavo,
>
> On April 27, 2018, 4:57 p.m. Gustavo Pimentel wrote:
>> Add MSI-X support and update driver documentation accordingly.
>>
>> Add new driver parameter to allow interruption type selection.
>>
>> Modify the Legacy/MSI/MSI-X test
Hi Gustavo,
On April 27, 2018, 4:57 p.m. Gustavo Pimentel wrote:
> Add MSI-X support and update driver documentation accordingly.
>
> Add new driver parameter to allow interruption type selection.
>
> Modify the Legacy/MSI/MSI-X test process, by:
> - Add and use a specific register located in
On Wed, Mar 21, 2018 at 10:10:36AM +0530, Rajkumar Rampelli wrote:
> Add support for pwm HW driver which has only capture functionality.
> This helps to implement the PWM based Tachometer driver which reads
> the PWM output signals from electronic fans.
>
> PWM Tachometer captures the period and
Hi Greg,
On Sun, 29 Apr 2018 15:36:42 +0200
Greg Kroah-Hartman wrote:
> On Mon, Apr 23, 2018 at 07:56:46PM +0200, Greg Kroah-Hartman wrote:
> > On Mon, Apr 23, 2018 at 07:38:14PM +0200, Boris Brezillon wrote:
> > > Hi,
> > >
> > > On Fri, 30 Mar 2018 09:47:41
Hi Greg,
On Sun, 29 Apr 2018 15:37:00 +0200
Greg Kroah-Hartman wrote:
> On Fri, Mar 30, 2018 at 09:47:44AM +0200, Boris Brezillon wrote:
> > Document sysfs files/directories/symlinks exposed by the I3C subsystem.
> >
> > Signed-off-by: Boris Brezillon
401 - 500 of 9986 matches
Mail list logo