From: Christoph Hellwig <hch-jcswGhMUV9g@public.gmane.org>
To: Andrew Morton <akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org,
hch-jcswGhMUV9g@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: sync_file_range.2: add some big WARNINGS
Date: Tue, 22 Sep 2009 13:40:52 +0200 [thread overview]
Message-ID: <20090922114052.GA1521@lst.de> (raw)
In-Reply-To: <20090921131519.875b4608.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
On Mon, Sep 21, 2009 at 01:15:19PM -0700, Andrew Morton wrote:
> The syscall is all about dirty memory management and userspace control
> over IO timing/volume. Trying to use it for data integrity purposes is a
> bit perverse.
Yes, its is. But that needs to be clearly documented. If you have
better wording to make it crystal clear you're welcome.
Additionally I have a half-backed patch to allow it calling into ->fsync
to actually make it usable as a fdatasync_range/fsync_range, but I
wonder if we should just add those as syscalls instead.
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2009-09-22 11:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-27 18:01 sync_file_range.2: add some big WARNINGS Christoph Hellwig
[not found] ` <20090827180116.GB31605-jcswGhMUV9g@public.gmane.org>
2009-09-20 5:34 ` Michael Kerrisk
[not found] ` <cfd18e0f0909192234l57ad4ec0rda34dcb83e355c5e-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-09-21 20:15 ` Andrew Morton
[not found] ` <20090921131519.875b4608.akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org>
2009-09-22 11:40 ` Christoph Hellwig [this message]
[not found] ` <20090922114052.GA1521-jcswGhMUV9g@public.gmane.org>
2009-09-22 18:47 ` Andrew Morton
2009-09-30 15:47 ` Christoph Hellwig
2009-12-04 15:25 ` Christoph Hellwig
2010-01-09 14:49 ` Christoph Hellwig
[not found] ` <20100109144910.GA30167-jcswGhMUV9g@public.gmane.org>
2010-01-17 5:48 ` Michael Kerrisk
[not found] ` <cfd18e0f1001162148w78c3ebe8u9d54fdeb7dac8892-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-01-17 9:58 ` Christoph Hellwig
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090922114052.GA1521@lst.de \
--to=hch-jcswghmuv9g@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=mtk.manpages-gM/Ye1E23mwN+BqQ9rBEUg@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox