linux-kernel - Re: [patch] remove redundant iov segment check

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: <712B05B5-F7E2-4F19-9980-2CA95C5D15AC@oracle.com>
Date:	Tue, 2 Jan 2007 10:22:00 -0800
From:	Zach Brown <zach.brown@...cle.com>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	"Chen, Kenneth W" <kenneth.w.chen@...el.com>,
	Andrew Morton <akpm@...l.org>,
	linux-kernel <linux-kernel@...r.kernel.org>
Subject: Re: [patch] remove redundant iov segment check

>> I wonder if it wouldn't be better to make this change as part of a
>> larger change that moves towards an explicit iovec container struct
>> rather than bare 'struct iov *' and 'nr_segs' arguments.

> I suspect it should be rather trivial to get this started.  As a first
> step we simply add a
>
> struct iodesc {
> 	int nr_segs;
> 	struct iovec ioc[]
> };

Agreed, does anyone plan to try this in the near future?  I can  
always throw it at the bottom of the todo list :/.

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