All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Dmitry Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org, linux-fsdevel@vger.kernel.org, jack@suse.cz
Subject: Re: [PATCH 1/2] ext4: grab write access inside ext4_file_dio_write
Date: Wed, 20 Mar 2013 12:54:40 +0000	[thread overview]
Message-ID: <20130320125440.GN21522@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1363783698-28092-1-git-send-email-dmonakhov@openvz.org>

On Wed, Mar 20, 2013 at 04:48:17PM +0400, Dmitry Monakhov wrote:
> We are responsible hold write count before any fs-speciffic modifications
> This patch should fix following warning:

NAK.  The right way to do it is to lift the damn thing out of ->aio_write()
completely.  See the last 3 commits in vfs.git#experimental...

      parent reply	other threads:[~2013-03-20 12:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-20 12:48 [PATCH 1/2] ext4: grab write access inside ext4_file_dio_write Dmitry Monakhov
2013-03-20 12:48 ` [PATCH 2/2] fs: prevent null pointer dereference for fs-less devices Dmitry Monakhov
2013-03-20 12:54 ` Al Viro [this message]

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=20130320125440.GN21522@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=dmonakhov@openvz.org \
    --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.