linux-kernel - Re: [PATCH] NFS: Don't use debug-printk-only local variables

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: <1221.1380194659@warthog.procyon.org.uk>
Date:	Thu, 26 Sep 2013 12:24:19 +0100
From:	David Howells <dhowells@...hat.com>
To:	Olof Johansson <olof@...om.net>
Cc:	dhowells@...hat.com, Trond Myklebust <Trond.Myklebust@...app.com>,
	linux-nfs@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] NFS: Don't use debug-printk-only local variables

Olof Johansson <olof@...om.net> wrote:

> Due to commit 996a2493ed5d3a8d5db03b560fcbbf1ca3f10897 (NFS:
> Use i_writecount to control whether to get an fscache cookie in
> nfs_open(), in two instances a local variable is only used in debug
> print statements. Said statements might be compiled out, which results
> in unused variable warnings:

Yeah, Fengguang's magic compile farm has also complained about that.

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