linux-kernel - Re: [RFC][PATCH] mm/page_isolation: tracing: trace all test_pages

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]

Message-ID: <4f680b5a-9076-3ba4-caea-bdd6eafeb899@redhat.com>
Date:   Tue, 31 Aug 2021 16:53:31 +0200
From:   David Hildenbrand <david@...hat.com>
To:     "George G. Davis" <george_davis@...tor.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        "open list:MEMORY MANAGEMENT" <linux-mm@...ck.org>,
        open list <linux-kernel@...r.kernel.org>
Cc:     Eugeniu Rosca <erosca@...adit-jv.com>,
        "George G. Davis" <davis.george@...mens.com>
Subject: Re: [RFC][PATCH] mm/page_isolation: tracing: trace all
 test_pages_isolated failures

On 23.08.21 22:28, George G. Davis wrote:
> From: "George G. Davis" <davis.george@...mens.com>
> 
> Some test_pages_isolated failure conditions don't include trace points.
> For debugging issues caused by "pinned" pages, make sure to trace all
> calls whether they succeed or fail. In this case, a failure case did not
> result in a trace point. So add the missing failure case in
> test_pages_isolated traces.

In which setups did you actually run into these cases?


-- 
Thanks,

David / dhildenb