linux-kernel - Re: sync_file_range(SYNC_FILE_RANGE

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: <Pine.LNX.4.64.0805301451020.19914@blonde.site>
Date:	Fri, 30 May 2008 14:58:09 +0100 (BST)
From:	Hugh Dickins <hugh@...itas.com>
To:	Pavel Machek <pavel@...e.cz>
cc:	kernel list <linux-kernel@...r.kernel.org>,
	"Rafael J. Wysocki" <rjw@...k.pl>
Subject: Re: sync_file_range(SYNC_FILE_RANGE_WRITE) blocks?

On Fri, 30 May 2008, Pavel Machek wrote:
> 
> sync_file_range(SYNC_FILE_RANGE_WRITE) blocks ... which makes problem
> for s2disk: there we want to start writeout as early as possible
> (system is going to shut down after write, and we need the data on
> disk).
> 
> Unfortuantely, sync_file_range(SYNC_FILE_RANGE_WRITE) blocks, which
> does not work for us. Is there non-blocking variant? "Start writeout
> on this fd, but don't block me"?

I guess there are lots of reasons why it may block (get rescheduled)
briefly, but why would that matter to you?  Are you saying that its
whole design has got broken somehow, and now SYNC_FILE_RANGE_WRITE
is behaving as if SYNC_FILE_RANGE_WAIT_AFTER had been supplied too?

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