linux-kernel - Re: [xfs-masters] linux-next: manual merge of the xfs tree with Linus' tree

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: <4D93177B.50505@fusionio.com>
Date:	Wed, 30 Mar 2011 13:43:55 +0200
From:	Jens Axboe <jaxboe@...ionio.com>
To:	Christoph Hellwig <hch@....de>
CC:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [xfs-masters] linux-next: manual merge of the xfs tree with 
 Linus' tree

On 2011-03-29 22:08, Christoph Hellwig wrote:
> FYI, the blk_flush_plug call in ufs_truncate also seem to be almost
> certainly incorrect as it's followed by a yield.
> 
> That only leaves the RAID code as remaining modular users of it, and
> I suspect it really is something that shouldn't need to be exported.

Agree, once things have settled down we can reap the remaining and keep
it internal.

-- 
Jens Axboe

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