All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kara <jack@suse.cz>
To: Dave Chinner <david@fromorbit.com>
Cc: Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
	linux-ext4@vger.kernel.org, Hugh Dickins <hughd@google.com>,
	linux-mm@kvack.org
Subject: Re: Hole punching and mmap races
Date: Fri, 18 May 2012 15:32:50 +0200	[thread overview]
Message-ID: <20120518133250.GC5589@quack.suse.cz> (raw)
In-Reply-To: <20120518101210.GX25351@dastard>

On Fri 18-05-12 20:12:10, Dave Chinner wrote:
> On Fri, May 18, 2012 at 01:28:29AM +0200, Jan Kara wrote:
> > On Thu 17-05-12 17:43:08, Dave Chinner wrote:
> > > On Wed, May 16, 2012 at 03:04:45PM +0200, Jan Kara wrote:
> > > > On Wed 16-05-12 12:14:23, Dave Chinner wrote:
> > > IIRC, it's a rare case (that I consider insane, BTW):  read from a
> > > file with into a buffer that is a mmap()d region of the same file
> > > that has not been faulted in yet.....
> >   With punch hole, the race is less insane - just punching hole in the area
> > which is accessed via mmap could race in a bad way AFAICS.
> 
> Seems the simple answer to me is to prevent page faults while hole
> punching, then....
  Yes, that's what I was suggesting in the beginning :) And I was asking
whether people are OK with another lock in the page fault path (in
particular in ->page_mkwrite) or whether someone has a better idea (e.g.
taking mmap_sem in the hole punching path seems possible but I'm not sure
whether that would be considered acceptable abuse).

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kara <jack@suse.cz>
To: Dave Chinner <david@fromorbit.com>
Cc: Jan Kara <jack@suse.cz>, Hugh Dickins <hughd@google.com>,
	xfs@oss.sgi.com, linux-mm@kvack.org,
	linux-fsdevel@vger.kernel.org, linux-ext4@vger.kernel.org
Subject: Re: Hole punching and mmap races
Date: Fri, 18 May 2012 15:32:50 +0200	[thread overview]
Message-ID: <20120518133250.GC5589@quack.suse.cz> (raw)
In-Reply-To: <20120518101210.GX25351@dastard>

On Fri 18-05-12 20:12:10, Dave Chinner wrote:
> On Fri, May 18, 2012 at 01:28:29AM +0200, Jan Kara wrote:
> > On Thu 17-05-12 17:43:08, Dave Chinner wrote:
> > > On Wed, May 16, 2012 at 03:04:45PM +0200, Jan Kara wrote:
> > > > On Wed 16-05-12 12:14:23, Dave Chinner wrote:
> > > IIRC, it's a rare case (that I consider insane, BTW):  read from a
> > > file with into a buffer that is a mmap()d region of the same file
> > > that has not been faulted in yet.....
> >   With punch hole, the race is less insane - just punching hole in the area
> > which is accessed via mmap could race in a bad way AFAICS.
> 
> Seems the simple answer to me is to prevent page faults while hole
> punching, then....
  Yes, that's what I was suggesting in the beginning :) And I was asking
whether people are OK with another lock in the page fault path (in
particular in ->page_mkwrite) or whether someone has a better idea (e.g.
taking mmap_sem in the hole punching path seems possible but I'm not sure
whether that would be considered acceptable abuse).

								Honza
-- 
Jan Kara <jack@suse.cz>
SUSE Labs, CR

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Jan Kara <jack@suse.cz>
To: Dave Chinner <david@fromorbit.com>
Cc: Jan Kara <jack@suse.cz>,
	linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com,
	linux-ext4@vger.kernel.org, Hugh Dickins <hughd@google.com>,
	linux-mm@kvack.org
Subject: Re: Hole punching and mmap races
Date: Fri, 18 May 2012 15:32:50 +0200	[thread overview]
Message-ID: <20120518133250.GC5589@quack.suse.cz> (raw)
In-Reply-To: <20120518101210.GX25351@dastard>

On Fri 18-05-12 20:12:10, Dave Chinner wrote:
> On Fri, May 18, 2012 at 01:28:29AM +0200, Jan Kara wrote:
> > On Thu 17-05-12 17:43:08, Dave Chinner wrote:
> > > On Wed, May 16, 2012 at 03:04:45PM +0200, Jan Kara wrote:
> > > > On Wed 16-05-12 12:14:23, Dave Chinner wrote:
> > > IIRC, it's a rare case (that I consider insane, BTW):  read from a
> > > file with into a buffer that is a mmap()d region of the same file
> > > that has not been faulted in yet.....
> >   With punch hole, the race is less insane - just punching hole in the area
> > which is accessed via mmap could race in a bad way AFAICS.
> 
> Seems the simple answer to me is to prevent page faults while hole
> punching, then....
  Yes, that's what I was suggesting in the beginning :) And I was asking
whether people are OK with another lock in the page fault path (in
particular in ->page_mkwrite) or whether someone has a better idea (e.g.
taking mmap_sem in the hole punching path seems possible but I'm not sure
whether that would be considered acceptable abuse).

								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>

  reply	other threads:[~2012-05-18 13:33 UTC|newest]

Thread overview: 56+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-15 22:48 Hole punching and mmap races Jan Kara
2012-05-15 22:48 ` Jan Kara
2012-05-15 22:48 ` Jan Kara
2012-05-16  2:14 ` Dave Chinner
2012-05-16  2:14   ` Dave Chinner
2012-05-16  2:14   ` Dave Chinner
2012-05-16 13:04   ` Jan Kara
2012-05-16 13:04     ` Jan Kara
2012-05-16 13:04     ` Jan Kara
2012-05-17  7:43     ` Dave Chinner
2012-05-17  7:43       ` Dave Chinner
2012-05-17  7:43       ` Dave Chinner
2012-05-17 23:28       ` Jan Kara
2012-05-17 23:28         ` Jan Kara
2012-05-17 23:28         ` Jan Kara
2012-05-18 10:12         ` Dave Chinner
2012-05-18 10:12           ` Dave Chinner
2012-05-18 10:12           ` Dave Chinner
2012-05-18 13:32           ` Jan Kara [this message]
2012-05-18 13:32             ` Jan Kara
2012-05-18 13:32             ` Jan Kara
2012-05-19  1:40             ` Dave Chinner
2012-05-19  1:40               ` Dave Chinner
2012-05-24 12:35               ` Jan Kara
2012-05-24 12:35                 ` Jan Kara
2012-05-24 12:35                 ` Jan Kara
2012-06-05  5:51                 ` Dave Chinner
2012-06-05  5:51                   ` Dave Chinner
2012-06-05  5:51                   ` Dave Chinner
2012-06-05  6:22                   ` Marco Stornelli
2012-06-05  6:22                     ` Marco Stornelli
2012-06-05  6:22                     ` Marco Stornelli
2012-06-05 23:15                   ` Jan Kara
2012-06-05 23:15                     ` Jan Kara
2012-06-05 23:15                     ` Jan Kara
2012-06-06  0:06                     ` Dave Chinner
2012-06-06  0:06                       ` Dave Chinner
2012-06-06  0:06                       ` Dave Chinner
2012-06-06  9:58                       ` Jan Kara
2012-06-06  9:58                         ` Jan Kara
2012-06-06  9:58                         ` Jan Kara
2012-06-06 13:36                         ` Dave Chinner
2012-06-06 13:36                           ` Dave Chinner
2012-06-06 13:36                           ` Dave Chinner
2012-06-07 21:58                           ` Jan Kara
2012-06-07 21:58                             ` Jan Kara
2012-06-07 21:58                             ` Jan Kara
2012-06-08  0:57                             ` Dave Chinner
2012-06-08  0:57                               ` Dave Chinner
2012-06-08 21:36                               ` Jan Kara
2012-06-08 21:36                                 ` Jan Kara
2012-06-08 23:06                                 ` Dave Chinner
2012-06-08 23:06                                   ` Dave Chinner
2012-06-12  8:56                                   ` Jan Kara
2012-06-12  8:56                                     ` Jan Kara
2012-06-12  8:56                                     ` 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=20120518133250.GC5589@quack.suse.cz \
    --to=jack@suse.cz \
    --cc=david@fromorbit.com \
    --cc=hughd@google.com \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=xfs@oss.sgi.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.