From: Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, hch@infradead.org, jack@suse.cz,
reiserfs-devel@vger.kernel.org, jeffm@suse.com,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] reiserfs: Truncate blocks not used by a write (v2)
Date: Wed, 16 Sep 2009 14:48:15 -0700 [thread overview]
Message-ID: <20090916144815.e544b319.akpm@linux-foundation.org> (raw)
In-Reply-To: <1253121912-20718-1-git-send-email-jack@suse.cz>
On Wed, 16 Sep 2009 19:25:12 +0200
Jan Kara <jack@suse.cz> wrote:
> It can happen that write does not use all the blocks allocated in write_begin
> either because of some filesystem error (like ENOSPC) or because page with
> data to write has been removed from memory. We truncate these blocks so that
> we don't have dangling blocks beyond i_size.
This clashes a bit with the kill-the-bkl/reiserfs stuff in linux-next.
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Morton <akpm@linux-foundation.org>
To: Jan Kara <jack@suse.cz>
Cc: linux-kernel@vger.kernel.org, hch@infradead.org, jack@suse.cz,
reiserfs-devel@vger.kernel.org, jeffm@suse.com,
Frederic Weisbecker <fweisbec@gmail.com>
Subject: Re: [PATCH] reiserfs: Truncate blocks not used by a write (v2)
Date: Wed, 16 Sep 2009 14:48:15 -0700 [thread overview]
Message-ID: <20090916144815.e544b319.akpm@linux-foundation.org> (raw)
In-Reply-To: <1253121912-20718-1-git-send-email-jack@suse.cz>
On Wed, 16 Sep 2009 19:25:12 +0200
Jan Kara <jack@suse.cz> wrote:
> It can happen that write does not use all the blocks allocated in write_begin
> either because of some filesystem error (like ENOSPC) or because page with
> data to write has been removed from memory. We truncate these blocks so that
> we don't have dangling blocks beyond i_size.
This clashes a bit with the kill-the-bkl/reiserfs stuff in linux-next.
next prev parent reply other threads:[~2009-09-16 21:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-16 17:25 [PATCH] reiserfs: Truncate blocks not used by a write (v2) Jan Kara
2009-09-16 21:48 ` Andrew Morton [this message]
2009-09-16 21:48 ` Andrew Morton
2009-09-17 0:56 ` Frederic Weisbecker
2009-09-17 1:56 ` Stephen Rothwell
2009-10-08 12:48 ` Frederic Weisbecker
2009-10-08 23:11 ` Stephen Rothwell
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=20090916144815.e544b319.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=fweisbec@gmail.com \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=jeffm@suse.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-devel@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.