linux-kernel - Re: [PATCH 08/27] staging: lustre: avoid to use bio->bi

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: <alpine.LFD.2.20.1604101527310.3112@casper.infradead.org>
Date:	Sun, 10 Apr 2016 15:37:42 +0100 (BST)
From:	James Simmons <jsimmons@...radead.org>
To:	Christoph Hellwig <hch@...radead.org>
cc:	Ming Lei <tom.leiming@...il.com>, Jens Axboe <axboe@...com>,
	linux-kernel@...r.kernel.org, linux-block@...r.kernel.org,
	Boaz Harrosh <boaz@...xistor.com>,
	Oleg Drokin <oleg.drokin@...el.com>,
	Andreas Dilger <andreas.dilger@...el.com>,
	Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
	"John L. Hammond" <john.hammond@...el.com>,
	Frank Zago <fzago@...y.com>,
	Mike Rapoport <mike.rapoport@...il.com>,
	Kent Overstreet <kent.overstreet@...il.com>,
	Julia Lawall <Julia.Lawall@...6.fr>,
	Al Viro <viro@...iv.linux.org.uk>,
	"moderated list:STAGING - LUSTRE PARALLEL FILESYSTEM" 
	<lustre-devel@...ts.lustre.org>,
	"open list:STAGING SUBSYSTEM" <devel@...verdev.osuosl.org>
Subject: Re: [PATCH 08/27] staging: lustre: avoid to use bio->bi_vcnt
 directly

> The lloop driver should be removed entirely - use the loop driver
> instead.

I talked with Andreas last week at our annual Lustre users group meeting 
about this. The reason I was told for existance is that some users were
using files on a Lustre file system with the loop back device. The 
performance was really bad at the time so a lloop was developed to 
overcome those limitations. Its been a long time so perhaps its time
to look at the default loop driver again to see if can perform now. If
it doesn't we will go the route of reworking the lloop driver in the
spirit of the cryptoloop device.