linux-kernel - Re: [PATCH 4.19 68/81] ACPICA: ACPI 6.3: PPTT add additional fields in Processor Structure Flags

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] [thread-next>] [day] [month] [year] [list]

Date:   Thu, 17 Oct 2019 08:59:33 -0700
From:   Greg Kroah-Hartman <gregkh@...uxfoundation.org>
To:     Pavel Machek <pavel@...x.de>
Cc:     linux-kernel@...r.kernel.org, stable@...r.kernel.org,
        Erik Schmauss <erik.schmauss@...el.com>,
        Bob Moore <robert.moore@...el.com>,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        John Garry <john.garry@...wei.com>,
        Sasha Levin <sashal@...nel.org>
Subject: Re: [PATCH 4.19 68/81] ACPICA: ACPI 6.3: PPTT add additional fields
 in Processor Structure Flags

On Thu, Oct 17, 2019 at 10:59:12AM +0200, Pavel Machek wrote:
> Hi!
> 
> > From: Erik Schmauss <erik.schmauss@...el.com>
> > 
> > Commit b5eab512e7cffb2bb37c4b342b5594e9e75fd486 upstream.
> 
> So this introduces another format of "upstream" information. So far I
> had this:
> 
> 		ma = re.match(".*Upstream commit ([0-9a-f]*) .*", l)
> 		...
>                 ma = re.match("commit ([0-9a-f]*) upstream[.]*", l)

do a case-insensitive search :)

> I believe this information belongs to the signoff area; it is
> important to know who pushed patch to the upstream and who is pusing
> it to the stable.
> 
> Could we just introduce "Upstream: <sha1>" tag and use it? It would
> improve consistency...

It would, I have plans for that, been busy with other stuff...

thanks,

greg k-h