From: Theodore Tso <tytso@mit.edu>
To: Dmitri Monakhov <dmonakhov@openvz.org>
Cc: linux-ext4@vger.kernel.org
Subject: Re: [PATCH] ext3/4: Clear pagep after write_begin() has failed
Date: Sun, 22 Feb 2009 22:12:30 -0500 [thread overview]
Message-ID: <20090223031230.GA19739@mit.edu> (raw)
In-Reply-To: <1234898659-4686-1-git-send-email-dmonakhov@openvz.org>
On Tue, Feb 17, 2009 at 10:24:19PM +0300, Dmitri Monakhov wrote:
> Seems there is no strict rule to for this case. In fact everybody
> just ignored this variable after write_begin() has failed.
> This was true until ext4_defrag_partial(). So let's follows simple
> rule similar to block_write_begin().
I've checked the latest ext4_defrag_partial, and it doesn't reference
the page variable if write_begin() failed....
- Ted
next prev parent reply other threads:[~2009-02-23 3:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-17 19:24 [PATCH] ext3/4: Clear pagep after write_begin() has failed Dmitri Monakhov
2009-02-23 3:12 ` Theodore Tso [this message]
2009-02-24 10:11 ` Dmitri Monakhov
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=20090223031230.GA19739@mit.edu \
--to=tytso@mit.edu \
--cc=dmonakhov@openvz.org \
--cc=linux-ext4@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 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).