linux-kernel - Re: [PATCH] blkdev: flush disk cache on ->fsync

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] [day] [month] [year] [list]

Message-ID: <20091013113101.GZ9228@kernel.dk>
Date:	Tue, 13 Oct 2009 13:31:01 +0200
From:	Jens Axboe <jens.axboe@...cle.com>
To:	Christoph Hellwig <hch@....de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [PATCH] blkdev: flush disk cache on ->fsync

On Tue, Oct 13 2009, Christoph Hellwig wrote:
> On Mon, Oct 12, 2009 at 05:07:13PM +0200, Jens Axboe wrote:
> > On Sat, Oct 10 2009, Christoph Hellwig wrote:
> > > Is anyone going to pick up this patch?
> > 
> > I can pick it up for .33. I think it looks good, but it's probably
> > something we should add up front.
> 
> Given that it's impossible to get data to a raw block device reliably
> without this I think it's .32 material.  Especially given how small
> the patch is and how long it's been out there..

Yes I agree, but it's also not a regression since this has been the
situation for eternity. So why not just accept .33 and we can push it to
-stable after that?

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