[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20190221163726.9f4db72bd38be953b74419eb@kernel.org>
Date: Thu, 21 Feb 2019 16:37:26 +0900
From: Masami Hiramatsu <mhiramat@...nel.org>
To: Steven Rostedt <rostedt@...dmis.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>,
Andy Lutomirski <luto@...capital.net>,
Linux List Kernel Mailing <linux-kernel@...r.kernel.org>,
Ingo Molnar <mingo@...nel.org>,
Andrew Morton <akpm@...ux-foundation.org>,
stable <stable@...r.kernel.org>,
Changbin Du <changbin.du@...il.com>,
Jann Horn <jannh@...gle.com>,
Kees Cook <keescook@...omium.org>,
Andy Lutomirski <luto@...nel.org>
Subject: Re: [PATCH 1/2 v2] kprobe: Do not use uaccess functions to access
kernel memory that can fault
On Wed, 20 Feb 2019 11:42:17 -0500
Steven Rostedt <rostedt@...dmis.org> wrote:
> On Thu, 21 Feb 2019 01:04:53 +0900
> Masami Hiramatsu <mhiramat@...nel.org> wrote:
>
> > > What about just adding 'u' to the end of the offset? Say you have a
> > > data structure in kernel space that has a field in user space you want
> > > to reference?
> > >
> > >
> > > field_val=+8u(+0(%si))
> >
> > Ah, that looks good :~) thank you for this idea!
>
> <bike-shed>
>
> Hmm, I wonder if we should make it +u8 or u+8? as +8u may be confused
> as unsigned? Like 8ULL. I don't know. Kernel developers suck at
> naming :-p
I like +u8 since it is easier to implement :-p.
Thank you,
>
> </bike-shed>
>
> -- Steve
--
Masami Hiramatsu <mhiramat@...nel.org>
Powered by blists - more mailing lists