From: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com> To: Linus Torvalds <torvalds@linux-foundation.org> Cc: Laura Abbott <labbott@redhat.com>, "Tobin C. Harding" <me@tobin.cc>, "kernel-hardening@lists.openwall.com" <kernel-hardening@lists.openwall.com>, "Jason A. Donenfeld" <Jason@zx2c4.com>, "Theodore Ts'o" <tytso@mit.edu>, Kees Cook <keescook@chromium.org>, Paolo Bonzini <pbonzini@redhat.com>, Tycho Andersen <tycho@docker.com>, "Roberts, William C" <william.c.roberts@intel.com>, Tejun Heo <tj@kernel.org>, Jordan Glover <Golden_Miller83@protonmail.ch>, Greg KH <gregkh@linuxfoundation.org>, Petr Mladek <pmladek@suse.com>, Joe Perches <joe@perches.com>, Ian Campbell <ijc@hellion.org.uk>, Sergey Senozhatsky <sergey.senozhatsky@gmail.com>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <wilal.deacon@arm.com>, Steven Rostedt <rostedt@goodmis.org>, Chris Fries <cfries@google.com>, Dave Weinstein <olorin@google.com>, Daniel Micay <danielmicay@gmail.com>, Djalal Harouni <tixxdz@gmail.com>, Linux Kernel Mailing List <linux-kernel@vger.kernel.org>, Network Development <netdev@vger.kernel.org>, David Miller <davem@davemloft.net> Subject: Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl Date: Thu, 9 Nov 2017 10:24:32 +0530 [thread overview] Message-ID: <CAPDLWs-yd13yh4NKpB4msAxcG6BeXMSohfpU_Vv2RJFc5ApddA@mail.gmail.com> (raw) In-Reply-To: <CAPDLWs8jyL3W_sGmHtw4Uw=8U_OYfeWJd_BpBLE7zvO4c6Z_8g@mail.gmail.com> On Thu, Nov 9, 2017 at 10:13 AM, Kaiwan N Billimoria <kaiwan.billimoria@gmail.com> wrote: >> But I don't know if there is anything else than the profiling code >> that _really_ wants access to /proc/kallsyms in user space as a >> regular user. > Front-ends to ftrace, like trace-cmd? [from the trace-cmd git repo (Steve Rostedt, pl stand up, pl stand up :-) Documentation/trace-cmd-restore.1.txt : ... *-k* kallsyms:: Used with *-c*, it overrides where to read the kallsyms file from. By default, /proc/kallsyms is used. *-k* will override the file to read the kallsyms from. This can be useful if the trace.dat file to create is from another machine. Just copy the /proc/kallsyms file locally, and use *-k* to point to that file. ... ] > Am unsure about this, but kprobes? (/jprobes/kretprobes), and by > extension, wrappers over this infra (like SystemTap)? > I (hazily) recollect a script I once wrote (years back though) that > collects kernel virtual addresses off of kallsyms for the purpose of > passing them to a 'helper' kernel module that uses kprobes. I realize > that 'modern' kprobes exposes APIs that just require the symbolic name > & that they're anyway at kernel privilege... but the point is, a > usermode script was picking up and passing the kernel addresses. > > Also, what about kernel addresses exposed via System.map? > Oh, just checked, it's root rw only.. pl ignore.
WARNING: multiple messages have this Message-ID (diff)
From: Kaiwan N Billimoria <kaiwan.billimoria@gmail.com> To: Linus Torvalds <torvalds@linux-foundation.org> Cc: Laura Abbott <labbott@redhat.com>, "Tobin C. Harding" <me@tobin.cc>, "kernel-hardening@lists.openwall.com" <kernel-hardening@lists.openwall.com>, "Jason A. Donenfeld" <Jason@zx2c4.com>, "Theodore Ts'o" <tytso@mit.edu>, Kees Cook <keescook@chromium.org>, Paolo Bonzini <pbonzini@redhat.com>, Tycho Andersen <tycho@docker.com>, "Roberts, William C" <william.c.roberts@intel.com>, Tejun Heo <tj@kernel.org>, Jordan Glover <Golden_Miller83@protonmail.ch>, Greg KH <gregkh@linuxfoundation.org>, Petr Mladek <pmladek@suse.com>, Joe Perches <joe@perches.com>, Ian Campbell <ijc@hellion.org.uk>, Sergey Senozhatsky <sergey.senozhatsky@gmail.com>, Catalin Marinas <catalin.marinas@arm.com>, Will Deacon <wilal.deacon@arm.com>, Steven Rostedt <rostedt@goodmis.org>, Subject: Re: [kernel-hardening] [PATCH v4] scripts: add leaking_addresses.pl Date: Thu, 9 Nov 2017 10:24:32 +0530 [thread overview] Message-ID: <CAPDLWs-yd13yh4NKpB4msAxcG6BeXMSohfpU_Vv2RJFc5ApddA@mail.gmail.com> (raw) In-Reply-To: <CAPDLWs8jyL3W_sGmHtw4Uw=8U_OYfeWJd_BpBLE7zvO4c6Z_8g@mail.gmail.com> On Thu, Nov 9, 2017 at 10:13 AM, Kaiwan N Billimoria <kaiwan.billimoria@gmail.com> wrote: >> But I don't know if there is anything else than the profiling code >> that _really_ wants access to /proc/kallsyms in user space as a >> regular user. > Front-ends to ftrace, like trace-cmd? [from the trace-cmd git repo (Steve Rostedt, pl stand up, pl stand up :-) Documentation/trace-cmd-restore.1.txt : ... *-k* kallsyms:: Used with *-c*, it overrides where to read the kallsyms file from. By default, /proc/kallsyms is used. *-k* will override the file to read the kallsyms from. This can be useful if the trace.dat file to create is from another machine. Just copy the /proc/kallsyms file locally, and use *-k* to point to that file. ... ] > Am unsure about this, but kprobes? (/jprobes/kretprobes), and by > extension, wrappers over this infra (like SystemTap)? > I (hazily) recollect a script I once wrote (years back though) that > collects kernel virtual addresses off of kallsyms for the purpose of > passing them to a 'helper' kernel module that uses kprobes. I realize > that 'modern' kprobes exposes APIs that just require the symbolic name > & that they're anyway at kernel privilege... but the point is, a > usermode script was picking up and passing the kernel addresses. > > Also, what about kernel addresses exposed via System.map? > Oh, just checked, it's root rw only.. pl ignore.
next prev parent reply other threads:[~2017-11-09 4:54 UTC|newest] Thread overview: 98+ messages / expand[flat|nested] mbox.gz Atom feed top 2017-11-07 10:32 [PATCH v4] scripts: add leaking_addresses.pl Tobin C. Harding 2017-11-07 10:32 ` [kernel-hardening] " Tobin C. Harding 2017-11-07 10:32 ` Tobin C. Harding 2017-11-07 10:50 ` Greg KH 2017-11-07 10:50 ` [kernel-hardening] " Greg KH 2017-11-07 10:50 ` Greg KH 2017-11-07 20:51 ` Tobin C. Harding 2017-11-07 20:51 ` [kernel-hardening] " Tobin C. Harding 2017-11-07 20:51 ` Tobin C. Harding 2017-11-07 13:56 ` David Laight 2017-11-07 13:56 ` [kernel-hardening] " David Laight 2017-11-07 13:56 ` David Laight 2017-11-07 20:58 ` Tobin C. Harding 2017-11-07 20:58 ` [kernel-hardening] " Tobin C. Harding 2017-11-07 20:58 ` Tobin C. Harding 2017-11-07 21:11 ` Linus Torvalds 2017-11-07 21:11 ` [kernel-hardening] " Linus Torvalds 2017-11-07 21:11 ` Linus Torvalds 2017-11-07 15:51 ` Petr Mladek 2017-11-07 15:51 ` [kernel-hardening] " Petr Mladek 2017-11-07 15:51 ` Petr Mladek 2017-11-07 20:39 ` Tobin C. Harding 2017-11-07 20:39 ` [kernel-hardening] " Tobin C. Harding 2017-11-07 20:39 ` Tobin C. Harding 2017-11-07 23:36 ` [kernel-hardening] " Laura Abbott 2017-11-07 23:36 ` Laura Abbott 2017-11-08 0:59 ` Linus Torvalds 2017-11-08 0:59 ` Linus Torvalds 2017-11-08 0:59 ` Linus Torvalds 2017-11-08 20:39 ` Linus Torvalds 2017-11-08 20:39 ` Linus Torvalds 2017-11-08 20:39 ` Linus Torvalds 2017-11-09 4:43 ` Kaiwan N Billimoria 2017-11-09 4:43 ` Kaiwan N Billimoria 2017-11-09 4:43 ` Kaiwan N Billimoria 2017-11-09 4:54 ` Kaiwan N Billimoria [this message] 2017-11-09 4:54 ` Kaiwan N Billimoria 2017-11-09 4:54 ` Kaiwan N Billimoria 2017-11-09 18:11 ` Steven Rostedt 2017-11-09 18:11 ` Steven Rostedt 2017-11-09 18:11 ` Steven Rostedt 2017-11-10 3:03 ` Kaiwan N Billimoria 2017-11-10 3:03 ` Kaiwan N Billimoria 2017-11-10 3:03 ` Kaiwan N Billimoria 2017-11-08 1:13 ` Tobin C. Harding 2017-11-08 1:13 ` Tobin C. Harding 2017-11-08 12:10 ` [kernel-hardening] " Michael Ellerman 2017-11-08 12:10 ` Michael Ellerman 2017-11-08 12:10 ` Michael Ellerman 2017-11-08 21:16 ` Tobin C. Harding 2017-11-08 21:16 ` Tobin C. Harding 2017-11-08 22:48 ` Tobin C. Harding 2017-11-08 22:48 ` Tobin C. Harding 2017-11-09 0:49 ` Michael Ellerman 2017-11-09 0:49 ` Michael Ellerman 2017-11-09 0:49 ` Michael Ellerman 2017-11-09 2:08 ` Tobin C. Harding 2017-11-09 2:08 ` Tobin C. Harding 2017-11-10 22:12 ` [kernel-hardening] " Frank Rowand 2017-11-10 22:12 ` Frank Rowand 2017-11-12 11:49 ` Michael Ellerman 2017-11-12 11:49 ` Michael Ellerman 2017-11-12 11:49 ` Michael Ellerman 2017-11-12 18:02 ` Frank Rowand 2017-11-12 18:02 ` Frank Rowand 2017-11-12 21:18 ` Tobin C. Harding 2017-11-12 21:18 ` Tobin C. Harding 2017-11-13 1:06 ` Michael Ellerman 2017-11-13 1:06 ` Michael Ellerman 2017-11-13 1:06 ` Michael Ellerman 2017-11-10 13:56 ` kaiwan.billimoria 2017-11-10 13:56 ` kaiwan.billimoria 2017-11-12 22:21 ` Tobin C. Harding 2017-11-12 22:21 ` Tobin C. Harding 2017-11-13 5:46 ` kaiwan.billimoria 2017-11-13 5:46 ` kaiwan.billimoria 2017-11-13 6:08 ` Tobin C. Harding 2017-11-13 6:08 ` Tobin C. Harding 2017-11-13 6:52 ` Kaiwan N Billimoria 2017-11-13 6:52 ` Kaiwan N Billimoria 2017-11-20 15:39 ` [kernel-hardening] " Petr Mladek 2017-11-20 15:39 ` Petr Mladek 2017-11-19 23:56 ` [kernel-hardening] " Tobin C. Harding 2017-11-19 23:56 ` Tobin C. Harding 2017-11-11 23:10 ` Kirill A. Shutemov 2017-11-11 23:10 ` [kernel-hardening] " Kirill A. Shutemov 2017-11-11 23:10 ` Kirill A. Shutemov 2017-11-12 23:06 ` Tobin C. Harding 2017-11-12 23:06 ` [kernel-hardening] " Tobin C. Harding 2017-11-12 23:06 ` Tobin C. Harding 2017-11-13 3:37 ` Kirill A. Shutemov 2017-11-13 3:37 ` [kernel-hardening] " Kirill A. Shutemov 2017-11-13 3:37 ` Kirill A. Shutemov 2017-11-13 4:35 ` Tobin C. Harding 2017-11-13 4:35 ` [kernel-hardening] " Tobin C. Harding 2017-11-13 4:35 ` Tobin C. Harding 2017-11-13 5:27 ` [kernel-hardening] " Kaiwan N Billimoria 2017-11-13 5:27 ` Kaiwan N Billimoria
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=CAPDLWs-yd13yh4NKpB4msAxcG6BeXMSohfpU_Vv2RJFc5ApddA@mail.gmail.com \ --to=kaiwan.billimoria@gmail.com \ --cc=Golden_Miller83@protonmail.ch \ --cc=Jason@zx2c4.com \ --cc=catalin.marinas@arm.com \ --cc=cfries@google.com \ --cc=danielmicay@gmail.com \ --cc=davem@davemloft.net \ --cc=gregkh@linuxfoundation.org \ --cc=ijc@hellion.org.uk \ --cc=joe@perches.com \ --cc=keescook@chromium.org \ --cc=kernel-hardening@lists.openwall.com \ --cc=labbott@redhat.com \ --cc=linux-kernel@vger.kernel.org \ --cc=me@tobin.cc \ --cc=netdev@vger.kernel.org \ --cc=olorin@google.com \ --cc=pbonzini@redhat.com \ --cc=pmladek@suse.com \ --cc=rostedt@goodmis.org \ --cc=sergey.senozhatsky@gmail.com \ --cc=tixxdz@gmail.com \ --cc=tj@kernel.org \ --cc=torvalds@linux-foundation.org \ --cc=tycho@docker.com \ --cc=tytso@mit.edu \ --cc=wilal.deacon@arm.com \ --cc=william.c.roberts@intel.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.