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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [day] [month] [year] [list]
Date:	Wed, 14 Oct 2015 04:39:06 +0000 (GMT)
From:	Daeho Jeong <daeho.jeong@...sung.com>
To:	"tytso@....edu" <tytso@....edu>
Cc:	"linux-ext4@...r.kernel.org" <linux-ext4@...r.kernel.org>
Subject: Question about ext4_free_blocks() Behavior for Per-File Data
 Journaling Mode

Hi. I have a question about ext4_free_blocks() behavior for per-file data journaling
mode. AFAIUI, in ext4_free_blocks(), it doesn't invoke ext4_forget() function for
data blocks of a per-file data journaling enabled file, because all the data blocks
of the file are not linked to the block device's address space of the file, but the
address space of the inode of the file, so any data blocks of the file cannot be
found by sb_find_get_block() function. It seems a bug, but I am not sure.
Is this a problem?

I think that, in ext4_free_blocks(), we have to find buffer heads of the file's data
,which are journaled, and transfer the found buffer heads to ext4_forget() in
order to forget and revoke the buffer head related journal record. For that, 
we might need to transfer the logical block numbers of the buffer heads of 
files' data blocks to ext4_free_blocks(). Do you have a better idea to resolve
this problem?

Powered by blists - more mailing lists