[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <80b0882f77d267293ea8b8d040bffe6032e1285e.camel@intel.com>
Date: Wed, 16 Mar 2022 19:42:57 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "keescook@...omium.org" <keescook@...omium.org>
CC: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"viro@...iv.linux.org.uk" <viro@...iv.linux.org.uk>,
"Williams, Dan J" <dan.j.williams@...el.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
"ebiederm@...ssion.com" <ebiederm@...ssion.com>,
"Chatre, Reinette" <reinette.chatre@...el.com>,
"linux-fsdevel@...r.kernel.org" <linux-fsdevel@...r.kernel.org>,
"Luck, Tony" <tony.luck@...el.com>,
"Hansen, Dave" <dave.hansen@...el.com>,
"Brown, Len" <len.brown@...el.com>
Subject: Re: [PATCH 1/3] x86: Separate out x86_regset for 32 and 64 bit
On Wed, 2022-03-16 at 12:06 -0700, Edgecombe, Richard P wrote:
> But even adding a comment to the base file has surprisingly wide
> effects. It caused the __bug_table section table to get code
> generated
> with different instructions, not just line numbers constants
> changing.
Err... I suppose this is probably because they are not actually
instructions and so should be expected, duh.
Powered by blists - more mailing lists