linux-kernel - Re: [PATCH] GHES: Fix cached error-status

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: <87oafmw5g4.fsf@yhuang-dev.intel.com>
Date:	Mon, 26 Oct 2015 13:43:07 +0800
From:	"Huang\, Ying" <ying.huang@...ux.intel.com>
To:	Borislav Petkov <bp@...e.de>
Cc:	"Luck\, Tony" <tony.luck@...el.com>,
	Davidlohr Bueso <dave@...olabs.net>,
	"Huang\, Ying" <ying.huang@...el.com>,
	"Rafael J. Wysocki" <rjw@...ysocki.net>,
	"linux-acpi\@vger.kernel.org" <linux-acpi@...r.kernel.org>,
	"linux-kernel\@vger.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] GHES: Fix cached error-status

Borislav Petkov <bp@...e.de> writes:

> On Mon, Oct 26, 2015 at 11:20:35AM +0800, Huang, Ying wrote:
>> In ghes_estatus_caches[], for caches with same contents, the cache with
>> biggest (newest) cache->time_in should be the first.  So if we found one
>> cache with too small (old) cache->time_in, we can say there are no cache
>> with same contents and bigger (newer) cache->time_in, so that we can
>> make decision (break) earlier.
>
> Well, for starters, this should be documented in the code so that people
> looking at it would not need to scratch their heads over that break
> statement there.

Yes.  Will do it.

Best Regards,
Huang, Ying
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/