[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20220125230645.097dad3a@gandalf.local.home>
Date: Tue, 25 Jan 2022 23:06:45 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Masami Hiramatsu <mhiramat@...nel.org>
Cc: Kees Cook <keescook@...omium.org>,
Stephen Rothwell <sfr@...b.auug.org.au>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Linux Next Mailing List <linux-next@...r.kernel.org>,
Beau Belgrave <beaub@...ux.microsoft.com>
Subject: Re: linux-next: build failure after merge of the kspp tree
On Wed, 26 Jan 2022 12:52:52 +0900
Masami Hiramatsu <mhiramat@...nel.org> wrote:
> > On Wed, 26 Jan 2022 09:35:38 +0900
> > Masami Hiramatsu <mhiramat@...nel.org> wrote:
> >
> > > I think Kees' idea seems better. If you and Beau are good, I will update
> > > the macros for __rel_loc. (This requires to change some user-space
> > > application which Beau is making too.)
> >
> > If Beau is OK with it, I'm OK with it too. I need to release a new version
> > of libtraceevent anyway, and I can make the update for that too.
> >
> > Who's adding the patch (if Beau says it's OK), you or Kees?
>
> This will update the __rel_loc spec, so I'll do it :)
As I replied to the other email, I don't think we want to do this.
As "rel" means relative, I think it makes more sense to keep it as is, and
not have it just be from the data section. That may be even more confusing.
But I'll wait for Beau to answer.
Note, I added both your and Kees patches to my queue and I'm currently
testing it. You can see what I'm testing here:
https://git.kernel.org/pub/scm/linux/kernel/git/rostedt/linux-trace.git/log/?h=ftrace/core
-- Steve
Powered by blists - more mailing lists