linux-kernel - Re: [PATCH v4] recordmcount: Correct st

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20210616202302.18522133@rorschach.local.home>
Date:   Wed, 16 Jun 2021 20:23:02 -0400
From:   Steven Rostedt <rostedt@...dmis.org>
To:     Mark-PK Tsai <mark-pk.tsai@...iatek.com>
Cc:     <peterz@...radead.org>, <linux-arm-kernel@...ts.infradead.org>,
        <linux-kernel@...r.kernel.org>,
        <linux-mediatek@...ts.infradead.org>, <matthias.bgg@...il.com>,
        <mhelsley@...are.com>, <samitolvanen@...gle.com>,
        <yj.chiang@...iatek.com>
Subject: Re: [PATCH v4] recordmcount: Correct st_shndx handling

On Wed, 16 Jun 2021 12:02:27 -0400
Steven Rostedt <rostedt@...dmis.org> wrote:

> On Wed, 16 Jun 2021 23:41:26 +0800
> Mark-PK Tsai <mark-pk.tsai@...iatek.com> wrote:
> 
> > From: Peter Zijlstra <peterz@...radead.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@...iatek.com>
> > Signed-off-by: Peter Zijlstra (Intel) <peterz@...radead.org>
> > Tested-by: Mark-PK Tsai <mark-pk.tsai@...iatek.com>
> > [handle endianness of sym->st_shndx]
> > Signed-off-by: Mark-PK Tsai <mark-pk.tsai@...iatek.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