From: Andrew Morton <akpm@linux-foundation.org>
To: Jan Kara <jack@suse.com>
Cc: linux-mm@kvack.org, linux-fsdevel@vger.kernel.org,
Al Viro <viro@ZenIV.linux.org.uk>,
Dmitry Vyukov <dvyukov@google.com>
Subject: Re: [PATCH] mm: Make sendfile(2) killable
Date: Thu, 15 Oct 2015 13:46:44 -0700 [thread overview]
Message-ID: <20151015134644.c072dd7ce26a74d8daa26a12@linux-foundation.org> (raw)
In-Reply-To: <1444653923-22111-1-git-send-email-jack@suse.com>
On Mon, 12 Oct 2015 14:45:23 +0200 Jan Kara <jack@suse.com> wrote:
> Currently a simple program below issues a sendfile(2) system call which
> takes about 62 days to complete in my test KVM instance.
Geeze some people are impatient.
> int fd;
> off_t off = 0;
>
> fd = open("file", O_RDWR | O_TRUNC | O_SYNC | O_CREAT, 0644);
> ftruncate(fd, 2);
> lseek(fd, 0, SEEK_END);
> sendfile(fd, fd, &off, 0xfffffff);
>
> Now you should not ask kernel to do a stupid stuff like copying 256MB in
> 2-byte chunks and call fsync(2) after each chunk but if you do, sysadmin
> should have a way to stop you.
>
> We actually do have a check for fatal_signal_pending() in
> generic_perform_write() which triggers in this path however because we
> always succeed in writing something before the check is done, we return
> value > 0 from generic_perform_write() and thus the information about
> signal gets lost.
ah.
> Fix the problem by doing the signal check before writing anything. That
> way generic_perform_write() returns -EINTR, the error gets propagated up
> and the sendfile loop terminates early.
>
> ...
>
> --- a/mm/filemap.c
> +++ b/mm/filemap.c
> @@ -2488,6 +2488,11 @@ again:
> break;
> }
>
> + if (fatal_signal_pending(current)) {
> + status = -EINTR;
> + break;
> + }
> +
> status = a_ops->write_begin(file, mapping, pos, bytes, flags,
> &page, &fsdata);
> if (unlikely(status < 0))
> @@ -2525,10 +2530,6 @@ again:
> written += copied;
>
> balance_dirty_pages_ratelimited(mapping);
> - if (fatal_signal_pending(current)) {
> - status = -EINTR;
> - break;
> - }
> } while (iov_iter_count(i));
>
> return written ? written : status;
This won't work, will it? If user hits ^C after we've written a few
pages, `written' is non-zero and the same thing happens?
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2015-10-15 20:46 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-12 12:45 Jan Kara
2015-10-15 20:46 ` Andrew Morton [this message]
2015-10-16 6:40 ` Jan Kara
2015-10-16 21:05 ` Andrew Morton
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=20151015134644.c072dd7ce26a74d8daa26a12@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=dvyukov@google.com \
--cc=jack@suse.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=viro@ZenIV.linux.org.uk \
/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