From: Andrea Arcangeli <andrea@suse.de>
To: Andrew Morton <akpm@zip.com.au>
Cc: Alexander Viro <viro@math.psu.edu>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] truncate fixes
Date: Mon, 7 Jan 2002 04:58:57 +0100 [thread overview]
Message-ID: <20020107045857.K1561@athlon.random> (raw)
In-Reply-To: <3C36DEA9.AEA2A402@zip.com.au>, <3C36DEA9.AEA2A402@zip.com.au>; <20020107034654.G1561@athlon.random> <3C3911F1.63E55E90@zip.com.au>
In-Reply-To: <3C3911F1.63E55E90@zip.com.au>; from akpm@zip.com.au on Sun, Jan 06, 2002 at 07:11:45PM -0800
On Sun, Jan 06, 2002 at 07:11:45PM -0800, Andrew Morton wrote:
> Andrea Arcangeli wrote:
> >
> > I prefer my fix that simply recalls the ->truncate callback if -ENOSPC
> > is returned by prepare_write. vmtruncate seems way overkill,
>
> Actually, vmtruncate will trim the page off the inode as well as the
> blocks from the file. I don't think there's necessarily a problem
> with having a page wholly outside i_size, but..
agreed, a truncate_inode_pages before ->truncate is needed, or after an
extension the old bh could be still there mapped to random in the
leftover page. But still the whole vmtruncate looks overkill, there
cannot be vm mappings in the way of our truncate because in
prepare_write we worked after the i_size if truncate will later do
something. pages in the middle if i_size cannot be mapped either, so if
it was a partial write that still couldn't be mapped.
Andrea
next prev parent reply other threads:[~2002-01-07 3:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-05 11:08 [patch] truncate fixes Andrew Morton
2002-01-07 2:46 ` Andrea Arcangeli
2002-01-07 2:53 ` Andrew Morton
2002-01-07 3:16 ` Andrea Arcangeli
2002-01-07 5:24 ` Alexander Viro
2002-01-07 3:11 ` Andrew Morton
2002-01-07 3:58 ` Andrea Arcangeli [this message]
2002-01-07 3:32 ` Andrea Arcangeli
2002-01-07 3:48 ` Andrew Morton
2002-01-07 4:12 ` Andrea Arcangeli
2002-01-07 4:28 ` Andrew Morton
2002-01-07 5:09 ` Andrea Arcangeli
2002-01-07 12:41 ` Daniel Phillips
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=20020107045857.K1561@athlon.random \
--to=andrea@suse.de \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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