Hi,
On Tue, Mar 14, 2017 at 11:15:25PM +0100, Sebastian Schmidt wrote:
> I was debugging some mysterious high CPU usage and tracked it down to
> monitoring daemon regularly calling stat*() on an NFS automount
> directory. The problem is triggered when mount.nfs passes mount()
Hi,
On Tue, Mar 14, 2017 at 11:15:25PM +0100, Sebastian Schmidt wrote:
> I was debugging some mysterious high CPU usage and tracked it down to
> monitoring daemon regularly calling stat*() on an NFS automount
> directory. The problem is triggered when mount.nfs passes mount()
Hi,
I was debugging some mysterious high CPU usage and tracked it down to
monitoring daemon regularly calling stat*() on an NFS automount
directory. The problem is triggered when mount.nfs passes mount() an
addr= that points to an unreachable address (i.e. connecting fails
immediately).
One way
Hi,
I was debugging some mysterious high CPU usage and tracked it down to
monitoring daemon regularly calling stat*() on an NFS automount
directory. The problem is triggered when mount.nfs passes mount() an
addr= that points to an unreachable address (i.e. connecting fails
immediately).
One way
When building without CONFIG_PRINTK, we need to provide a stub
check_syslog_permissions. As there is no way to turn on the
dmesg_restrict sysctl without CONFIG_PRINTK, return success.
Reported-by: Jim Davis
Signed-off-by: Sebastian Schmidt
---
include/linux/syslog.h | 8
1 file
Hi all,
On Thu, Nov 13, 2014 at 11:21:18AM -0800, Kees Cook wrote:
> > This looks to come from your "Honor dmesg_restrict sysctl on dmesg dumps"
> > patch
Oops, you are right.
> > The randconfig doesn't have CONFIG_PRINTK. I guess we need to provide a
> > stub
> > in to cover this.
>
>
Hi all,
On Thu, Nov 13, 2014 at 11:21:18AM -0800, Kees Cook wrote:
This looks to come from your Honor dmesg_restrict sysctl on dmesg dumps
patch
Oops, you are right.
The randconfig doesn't have CONFIG_PRINTK. I guess we need to provide a
stub
in linux/syslog.h to cover this.
When building without CONFIG_PRINTK, we need to provide a stub
check_syslog_permissions. As there is no way to turn on the
dmesg_restrict sysctl without CONFIG_PRINTK, return success.
Reported-by: Jim Davis jim.ep...@gmail.com
Signed-off-by: Sebastian Schmidt y...@yath.de
---
include/linux
information could have been leaked there.
Other log types are unaffected.
Signed-off-by: Sebastian Schmidt
---
fs/pstore/inode.c | 22 ++
include/linux/syslog.h | 1 +
kernel/printk/printk.c | 2 +-
3 files changed, 24 insertions(+), 1 deletion(-)
diff --git a/fs
information could have been leaked there.
Other log types are unaffected.
Signed-off-by: Sebastian Schmidt y...@yath.de
---
fs/pstore/inode.c | 22 ++
include/linux/syslog.h | 1 +
kernel/printk/printk.c | 2 +-
3 files changed, 24 insertions(+), 1 deletion(-)
diff
10 matches
Mail list logo
