From: Josh Poimboeuf <jpoimboe@kernel.org>
To: Mikulas Patocka <mpatocka@redhat.com>
Cc: Peter Zijlstra <peterz@infradead.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Josh Poimboeuf <jpoimboe@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] objtool: fix objtool regression on x32 systems
Date: Wed, 18 May 2022 11:08:25 -0700 [thread overview]
Message-ID: <20220518180825.k4pvac42dlfdgdkd@treble> (raw)
In-Reply-To: <alpine.LRH.2.02.2205180813200.22292@file01.intranet.prod.int.rdu2.redhat.com>
On Wed, May 18, 2022 at 09:28:57AM -0400, Mikulas Patocka wrote:
>
>
> On Mon, 16 May 2022, Peter Zijlstra wrote:
>
> > On Mon, May 16, 2022 at 11:56:21AM -0400, Mikulas Patocka wrote:
> > >
> > > With this patch, the compiled kernel works. With kernels 5.17 or older, it
> > > also works. I bisected it and the breakage is caused by the commit
> > > 4abff6d48dbc.
> >
> > Sure; but it works doesn't mean there aren't more latent issues. ILP32
> > hosted (cross) builds just aren't a thing I've ever considered. If we
> > really want to go support that then we should at least audit the whole
> > thing.
> >
> > A quick look seems to suggest at least all the 'offset' fields should be
> > u64 or something. The only reason that works is because -mcmodel=kernel
> > keeps everything in the 2G range to make s32 immediates work. But it
> > isn't right.
>
> There are many 'offset' variables and its hard to determine which should
> be 64-bit. Would it be possible to commit this patch, so that kernel 5.18
> can be compiled on x32 distributions? And you can do code refactoring in
> the next merge window.
I believe Peter is going ahead with merging this for 5.18, and your v2
looks identical to what he already has here:
https://git.kernel.org/pub/scm/linux/kernel/git/peterz/queue.git/log/?h=objtool/urgent
--
Josh
prev parent reply other threads:[~2022-05-18 18:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-16 15:06 [PATCH] " Mikulas Patocka
2022-05-16 15:41 ` Peter Zijlstra
2022-05-16 15:56 ` Mikulas Patocka
2022-05-16 21:25 ` Peter Zijlstra
2022-05-17 8:26 ` David Laight
2022-05-17 9:42 ` Peter Zijlstra
2022-05-18 13:28 ` [PATCH v2] " Mikulas Patocka
2022-05-18 18:08 ` Josh Poimboeuf [this message]
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=20220518180825.k4pvac42dlfdgdkd@treble \
--to=jpoimboe@kernel.org \
--cc=jpoimboe@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=peterz@infradead.org \
--cc=torvalds@linux-foundation.org \
/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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®