From: Steven Rostedt <rostedt@goodmis.org>
To: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
Cc: <peterz@infradead.org>, <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>,
<linux-mediatek@lists.infradead.org>, <matthias.bgg@gmail.com>,
<mhelsley@vmware.com>, <samitolvanen@google.com>,
<yj.chiang@mediatek.com>
Subject: Re: [PATCH v4] recordmcount: Correct st_shndx handling
Date: Wed, 16 Jun 2021 20:23:02 -0400 [thread overview]
Message-ID: <20210616202302.18522133@rorschach.local.home> (raw)
In-Reply-To: <20210616120227.6fc005c3@gandalf.local.home>
On Wed, 16 Jun 2021 12:02:27 -0400
Steven Rostedt <rostedt@goodmis.org> wrote:
> On Wed, 16 Jun 2021 23:41:26 +0800
> Mark-PK Tsai <mark-pk.tsai@mediatek.com> wrote:
>
> > From: Peter Zijlstra <peterz@infradead.org>
> >
> > One should only use st_shndx when >SHN_UNDEF and <SHN_LORESERVE. When
> > SHN_XINDEX, then use .symtab_shndx. Otherwise use 0.
> >
> > This handles the case: st_shndx >= SHN_LORESERVE && st_shndx != SHN_XINDEX.
> >
> > Reported-by: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org>
> > Tested-by: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
> > [handle endianness of sym->st_shndx]
> > Signed-off-by: Mark-PK Tsai <mark-pk.tsai@mediatek.com>
> > ---
>
> Thanks, I pulled this in and started the testing.
>
It passed my normal tests. I'll run my cross compile test, and I just
pushed it to linux-next. I'll wait a few days before I push it to Linus.
-- Steve
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2021-06-17 0:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-16 15:41 [PATCH v4] recordmcount: Correct st_shndx handling Mark-PK Tsai
2021-06-16 16:02 ` Steven Rostedt
2021-06-17 0:23 ` Steven Rostedt [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=20210616202302.18522133@rorschach.local.home \
--to=rostedt@goodmis.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark-pk.tsai@mediatek.com \
--cc=matthias.bgg@gmail.com \
--cc=mhelsley@vmware.com \
--cc=peterz@infradead.org \
--cc=samitolvanen@google.com \
--cc=yj.chiang@mediatek.com \
/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;
as well as URLs for NNTP newsgroup(s).