From: Jan Kara <jack@suse.cz>
To: Nick Piggin <npiggin@gmail.com>
Cc: Jan Kara <jack@suse.cz>, Jeff Moyer <jmoyer@redhat.com>,
KOSAKI Motohiro <kosaki.motohiro@gmail.com>,
Michael Kerrisk <mtk.manpages@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
linux-man@vger.kernel.org, linux-mm@kvack.org, mgorman@suse.de,
Andrea Arcangeli <aarcange@redhat.com>,
Woodman <lwoodman@redhat.com>
Subject: Re: [PATCH] Describe race of direct read and fork for unaligned buffers
Date: Wed, 2 May 2012 11:18:37 +0200 [thread overview]
Message-ID: <20120502091837.GC16976@quack.suse.cz> (raw)
In-Reply-To: <CAPa8GCCnvvaj0Do7sdrdfsvbcAf0zBe3ssXn45gMfDKCcvJWxA@mail.gmail.com>
On Wed 02-05-12 19:09:54, Nick Piggin wrote:
> On 2 May 2012 18:17, Jan Kara <jack@suse.cz> wrote:
> > On Wed 02-05-12 01:50:46, Nick Piggin wrote:
>
> >> KOSAKI-san is correct, I think.
> >>
> >> The race is something like this:
> >>
> >> DIO-read
> >> page = get_user_pages()
> >> fork()
> >> COW(page)
> >> touch(page)
> >> DMA(page)
> >> page_cache_release(page);
> >>
> >> So whether parent or child touches the page, determines who gets the
> >> actual DMA target, and who gets the copy.
> > OK, this is roughly what I understood from original threads as well. So
> > if our buffer is page aligned and its size is page aligned, you would hit
> > the corruption only if you do modify the buffer while IO to / from that buffer
> > is in progress. And that would seem like a really bad programming practice
> > anyway. So I still believe that having everything page size aligned will
> > effectively remove the problem although I agree it does not aim at the core
> > of it.
>
> I see what you mean.
>
> I'm not sure, though. For most apps it's bad practice I think. If you get into
> realm of sophisticated, performance critical IO/storage managers, it would
> not surprise me if such concurrent buffer modifications could be allowed.
> We allow exactly such a thing in our pagecache layer. Although probably
> those would be using shared mmaps for their buffer cache.
>
> I think it is safest to make a default policy of asking for IOs against private
> cow-able mappings to be quiesced before fork, so there are no surprises
> or reliance on COW details in the mm. Do you think?
Yes, I agree that (and MADV_DONTFORK) is probably the best thing to have
in documentation. Otherwise it's a bit too hairy...
Honza
--
Jan Kara <jack@suse.cz>
SUSE Labs, CR
--
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/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2012-05-02 9:18 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-30 9:30 [PATCH] Describe race of direct read and fork for unaligned buffers Jan Kara
2012-04-30 13:41 ` Jeff Moyer
2012-04-30 14:30 ` Mel Gorman
2012-05-01 5:50 ` Michael Kerrisk (man-pages)
2012-05-01 6:49 ` Nick Piggin
2012-05-01 14:31 ` KOSAKI Motohiro
2012-05-01 14:37 ` KOSAKI Motohiro
2012-05-01 15:11 ` Jeff Moyer
2012-05-01 15:34 ` KOSAKI Motohiro
2012-05-01 15:38 ` Jeff Moyer
2012-05-01 15:50 ` Nick Piggin
2012-05-01 23:51 ` Andrea Arcangeli
2012-05-02 8:17 ` Jan Kara
2012-05-02 9:09 ` Nick Piggin
2012-05-02 9:18 ` Jan Kara [this message]
2012-05-02 19:14 ` KOSAKI Motohiro
2012-05-02 19:23 ` Jan Kara
2012-05-02 19:25 ` KOSAKI Motohiro
2012-05-05 11:28 ` Michael Kerrisk (man-pages)
2012-05-05 15:29 ` KOSAKI Motohiro
2012-05-08 23:10 ` Nick Piggin
2012-05-09 5:35 ` Michael Kerrisk (man-pages)
2012-05-09 7:01 ` Nick Piggin
2012-05-09 7:18 ` Michael Kerrisk (man-pages)
2012-05-10 15:00 ` Jan Kara
2012-05-01 16:15 ` KOSAKI Motohiro
2012-05-01 17:56 ` Michael Kerrisk (man-pages)
2012-05-02 0:34 ` Nick Piggin
2012-05-02 3:04 ` Hugh Dickins
2012-05-02 3:10 ` Nick Piggin
2012-05-02 9:20 ` Jan Kara
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=20120502091837.GC16976@quack.suse.cz \
--to=jack@suse.cz \
--cc=aarcange@redhat.com \
--cc=jmoyer@redhat.com \
--cc=kosaki.motohiro@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-man@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lwoodman@redhat.com \
--cc=mgorman@suse.de \
--cc=mtk.manpages@gmail.com \
--cc=npiggin@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).