lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Tue, 16 Apr 2019 08:33:06 -0400
From:   Steven Rostedt <>
To:     Kees Cook <>
Cc:     Olof Johansson <>,
        Alexei Starovoitov <>,
        Joel Fernandes <>,
        Joel Fernandes <>,
        Linux Kernel Mailing List <>,
        Qais Yousef <>,
        Dietmar Eggemann <>,
        Manoj Rao <>,
        Andrew Morton <>,
        Alexei Starovoitov <>,
        atish patra <>,
        Daniel Colascione <>,
        Dan Williams <>,
        Greg Kroah-Hartman <>,
        Guenter Roeck <>,
        Jonathan Corbet <>,
        Karim Yaghmour <>,
        Android Kernel Team <>,
        "open list:DOCUMENTATION" <>,
        "open list:KERNEL SELFTEST FRAMEWORK" 
        Masahiro Yamada <>,
        Masami Hiramatsu <>,
        Randy Dunlap <>,
        Shuah Khan <>, Yonghong Song <>
Subject: Re: [PATCH v5 1/3] Provide in-kernel headers to make extending
 kernel easier

On Mon, 15 Apr 2019 22:50:10 -0500
Kees Cook <> wrote:

> On Mon, Apr 15, 2019 at 9:41 AM Steven Rostedt <> wrote:
> > I agree with this assessment. We shouldn't use config.gz as precedence
> > for this solution. config.gz should have been in debugfs to begin with,
> > but I don't believe debugfs was around when config.gz was introduced.
> > (Don't have time to look into the history of the two).  
> I don't agree with this: /proc/config.gz is used by a lot of tools
> that do sanity-check of running systems. This isn't _debugging_...
> it's verifying correct kernel builds. It's a fancy version of checking
> /proc/version.

Then we should perhaps make a new file system call tarballs ;-)


and place everything there. That way it removes it from /proc (which is
the worse place for that) and also makes it something other than debug.
That's what I did for tracefs.

-- Steve

Powered by blists - more mailing lists