All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ted Ts'o <tytso@mit.edu>
To: Jan Kara <jack@suse.cz>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [PATCH 0/3] Rewrite ext4_page_mkwrite, fix fs freezing
Date: Tue, 10 May 2011 20:30:12 -0400	[thread overview]
Message-ID: <20110511003012.GC6933@thunk.org> (raw)
In-Reply-To: <1305066574-1573-1-git-send-email-jack@suse.cz>

On Wed, May 11, 2011 at 12:29:31AM +0200, Jan Kara wrote:
> 
>   following three patches reimplement ext4_page_mkwrite() so that it returns
> locked pages (which is necessary for stable pages work and also for fixing of
> freezing code). As a bonus we also avoid taking i_alloc_sem as it's not
> necessary and use generic block_page_mkwrite() helper. The common delalloc
> path should be more straightforward now.

How does this relate to Darrick Wong's patches?  Are your patches in
addition to or instead of his?

					- Ted

  parent reply	other threads:[~2011-05-11  0:30 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 22:29 [PATCH 0/3] Rewrite ext4_page_mkwrite, fix fs freezing Jan Kara
2011-05-10 22:29 ` [PATCH 1/3] fs: Create __block_page_mkwrite() helper passing error values back Jan Kara
2011-05-17 15:09   ` Christoph Hellwig
2011-05-18  7:35     ` Jan Kara
2011-05-10 22:29 ` [PATCH 2/3] ext4: Rewrite ext4_page_mkwrite() to return locked page Jan Kara
2011-05-10 22:29 ` [PATCH 3/3] ext4: Block mmapped writes while the fs is frozen Jan Kara
2011-05-17 15:11   ` Christoph Hellwig
2011-05-18  7:56     ` Jan Kara
2011-05-18  8:07       ` Christoph Hellwig
2011-05-18 14:03         ` Eric Sandeen
2011-05-18 15:25           ` Jan Kara
2011-05-18 16:40             ` Eric Sandeen
2011-05-11  0:30 ` Ted Ts'o [this message]
2011-05-11  9:27   ` [PATCH 0/3] Rewrite ext4_page_mkwrite, fix fs freezing Jan Kara
2011-05-11 16:48     ` Darrick J. Wong
2011-05-11 17:03       ` Jan Kara
2011-05-11  7:33 ` Amir G.
2011-05-11  9:43   ` Jan Kara
2011-05-11 10:15     ` Amir G.

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=20110511003012.GC6933@thunk.org \
    --to=tytso@mit.edu \
    --cc=jack@suse.cz \
    --cc=linux-ext4@vger.kernel.org \
    --cc=linux-fsdevel@vger.kernel.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 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.