linux-kernel - RE: [patch] clean up unused kiocb 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: <000101c6ddbc$334248d0$ff0da8c0@amr.corp.intel.com>
Date:	Thu, 21 Sep 2006 13:26:20 -0700
From:	"Chen, Kenneth W" <kenneth.w.chen@...el.com>
To:	"'Zach Brown'" <zach.brown@...cle.com>
Cc:	"'Andrew Morton'" <akpm@...l.org>,
	"'Suparna Bhattacharya'" <suparna@...ibm.com>,
	<linux-kernel@...r.kernel.org>, "linux-aio" <linux-aio@...ck.org>
Subject: RE: [patch] clean up unused kiocb variables

Zach Brown wrote on Thursday, September 21, 2006 12:34 PM
> Chen, Kenneth W wrote:
> > Any reason why we keep these two variables around for kiocb structure?
> 
> If there is a good one I've forgotten it.
> 
> > They are not used anywhere.
> 
> Indeed.


Let's remove them.  We can always add them back if there is a need.


> The ki_retried users all seem pretty questionable, too.  How about
> removing all that stuff?

Suparna wanted them around for debug purpose at one point.  I don't know
whether that is still the case right now.  At least I can wrap it around
with #if DEBUG.

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