linux-kernel - Re: [PATCH] reiserfs: Truncate blocks not used by a write

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20090901181027.GF8242@duck.novell.com>
Date:	Tue, 1 Sep 2009 20:10:27 +0200
From:	Jan Kara <jack@...e.cz>
To:	Christoph Hellwig <hch@...radead.org>
Cc:	Jan Kara <jack@...e.cz>, Andrew Morton <akpm@...ux-foundation.org>,
	reiserfs-devel@...r.kernel.org, jeffm@...e.com,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH] reiserfs: Truncate blocks not used by a write

On Tue 01-09-09 13:42:56, Christoph Hellwig wrote:
> On Tue, Sep 01, 2009 at 05:55:54PM +0200, Jan Kara 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. 
> 
> vmtruncate is in the process of going away for 2.6.32.  Please use a
> filesystems-specific routine to just trim the blocks, similar to what
> the vmtruncate call in the generic write_begin helper is beeing replaced
> with in Nick's truncate patch series.
  Reiserfs does not have such helper (yet), that's why I've used
vmtruncate. But OK, I'll try to convert reiserfs to the new truncate
sequence and then make this fix use it...

								Honza
-- 
Jan Kara <jack@...e.cz>
SUSE Labs, CR
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/