All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Li, Xin3" <xin3.li@intel.com>
To: Nathan Chancellor <nathan@kernel.org>
Cc: Kees Cook <keescook@chromium.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arch@vger.kernel.org" <linux-arch@vger.kernel.org>,
	H.Peter Anvin <hpa@zytor.com>,
	Peter Zijlstra <peterz@infradead.org>,
	"llvm@lists.linux.dev" <llvm@lists.linux.dev>,
	"linux-kbuild@vger.kernel.org" <linux-kbuild@vger.kernel.org>
Subject: RE: upgrade the orphan section warning to a hard link error
Date: Sat, 22 Oct 2022 03:39:50 +0000	[thread overview]
Message-ID: <BN6PR1101MB21616DCC665F0C7285DB1DD3A82C9@BN6PR1101MB2161.namprd11.prod.outlook.com> (raw)
In-Reply-To: <Y1GLLnYsEC8lYTdp@dev-arch.thelio-3990X>

> > Do you want me to continue?  Or maybe it's easier for you to complete it?
> 
> Sure, I think it is reasonable for you to continue with this as you brought up the
> idea initially! Feel free to just take those diffs wholesale if they work and stick a
> 
>     Suggested-by: Nathan Chancellor <nathan@kernel.org>
> 
> or
> 
>     Co-developed-by: Nathan Chancellor <nathan@kernel.org>
>     Signed-off-by: Nathan Chancellor <nathan@kernel.org>
> 
> on the patch if you are so inclined or rework them in a way you see fit, I do not
> have a strong opinion.
> 
> > I will need to find resources to test the patch on other platforms besides x86.
> 
> In theory, we should have already cleaned up all these warnings when we
> enabled CONFIG_LD_ORPHAN_WARN for all these architectures, so that
> change should be a no-op. More testing is never a bad idea though :)
> 
> I can throw it into my LLVM testing matrix as well.

Hi Nathan,

I just sent out the patch
  https://lore.kernel.org/all/20221022030519.9505-2-xin3.li@intel.com/,
It's mostly based on what we have discussed here, please help to review it.

Thanks!
Xin

> 
> Cheers,
> Nathan

      parent reply	other threads:[~2022-10-22  3:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <BN6PR1101MB216105D169D482FC8C539059A8269@BN6PR1101MB2161.namprd11.prod.outlook.com>
2022-10-17 18:26 ` upgrade the orphan section warning to a hard link error Nathan Chancellor
2022-10-17 19:32   ` Kees Cook
2022-10-17 19:56     ` Nathan Chancellor
2022-10-20  5:17       ` Li, Xin3
2022-10-20 17:53         ` Nathan Chancellor
2022-10-21  1:58           ` Li, Xin3
2022-10-22  3:39           ` Li, Xin3 [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=BN6PR1101MB21616DCC665F0C7285DB1DD3A82C9@BN6PR1101MB2161.namprd11.prod.outlook.com \
    --to=xin3.li@intel.com \
    --cc=hpa@zytor.com \
    --cc=keescook@chromium.org \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kbuild@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=llvm@lists.linux.dev \
    --cc=nathan@kernel.org \
    --cc=peterz@infradead.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 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.