linux-kernel - [PATCH -v2 0/3] Patchset for fixing poison failure of THP.

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

Date:	Fri, 28 Jan 2011 14:52:30 +0900
From:	Jin Dongming <jin.dongming@...css.fujitsu.com>
To:	Andi Kleen <andi@...stfloor.org>,
	Andrea Arcangeli <aarcange@...hat.com>
CC:	AKPM　 <akpm@...ux-foundation.org>,
	Huang Ying <ying.huang@...el.com>,
	Hidetoshi Seto <seto.hidetoshi@...fujitsu.com>,
	LKLM <linux-kernel@...r.kernel.org>
Subject: [PATCH -v2 0/3] Patchset for fixing poison failure of THP.

I found the following problems while testing the poison of THP:
    1. If the poisoned THP is failed to be split, the process could not be
       killed.
    2. The reported address with sigbus is the address of the head page.
       This will make that the unexpected process on Guest OS(running on KVM)
       to be killed.
    3. The test of poisoned tail page always fails. This is because the lru
       check of THP is done always, though the tail page is not set with
       PG_lru flag.

To resolve the above problems, I made the following patches.

Jin Dongming (3):
      [PATCH 1/3] Fix splitting poisoned THP.
      [PATCH 2/3] Fix the wrong reported address of poisoned THP.
      [PATCH 3/3] Fix unsuitable behavior for poisoned tail pages of THP.

 mm/huge_memory.c    |    7 ++++-
 mm/memory-failure.c |   84 +++++++++++++++++++++++++++++++++++++++-----------
 2 files changed, 71 insertions(+), 20 deletions(-)

--
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/