linux-kernel - [PATCH 0/1] lockdep: fix warning: print_lock

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

Message-ID: <20190519062946.27040-1-jhubbard@nvidia.com>
Date:   Sat, 18 May 2019 23:29:45 -0700
From:   John Hubbard <jhubbard@...dia.com>
To:     LKML <linux-kernel@...r.kernel.org>,
        Frederic Weisbecker <frederic@...nel.org>
CC:     John Hubbard <jhubbard@...dia.com>,
        Andrew Morton <akpm@...ux-foundation.org>,
        Linus Torvalds <torvalds@...ux-foundation.org>,
        "Paul E . McKenney" <paulmck@...ux.vnet.ibm.com>,
        Peter Zijlstra <peterz@...radead.org>,
        Thomas Gleixner <tglx@...utronix.de>,
        Will Deacon <will.deacon@....com>
Subject: [PATCH 0/1] lockdep: fix warning: print_lock_trace defined but not used

Hi,

I ran across this minor warning while building against today's linux.git.

The proposed trivial fix leaves it a little fragile from a "what if someone
adds a new call to print_lock_trace()" point of view, but I believe that it
makes the current combination of ifdefs accurate, anyway.

Cc: Frederic Weisbecker <frederic@...nel.org>
Cc: Andrew Morton <akpm@...ux-foundation.org>
Cc: Linus Torvalds <torvalds@...ux-foundation.org>
Cc: Paul E. McKenney <paulmck@...ux.vnet.ibm.com>
Cc: Peter Zijlstra <peterz@...radead.org>
Cc: Thomas Gleixner <tglx@...utronix.de>
Cc: Will Deacon <will.deacon@....com>

John Hubbard (1):
  lockdep: fix warning: print_lock_trace defined but not used

 kernel/locking/lockdep.c | 3 +++
 1 file changed, 3 insertions(+)

-- 
2.21.0