linux-kernel - Re: Is VFS behavior fine?

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: <486CE247.5020904@linux.vnet.ibm.com>
Date:	Thu, 03 Jul 2008 11:29:27 -0300
From:	Breno Leitao <leitao@...ux.vnet.ibm.com>
To:	Artem.Bityutskiy@...ia.com
CC:	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Christoph Hellwig <hch@...radead.org>,
	linux-fsdevel@...r.kernel.org,
	Hunter Adrian <ext-Adrian.Hunter@...ia.com>
Subject: Re: Is VFS behavior fine?

Artem Bityutskiy wrote:
> The result of it was that the '->delete_inode()' operation for
> the 'xxx' directory inode is not called. It is not called even
> after 'cd /'. However, if we do not do the 'touch tmp' command
> (which actually fails), '->delete_inode()' _is_ called for 'xxx'.
>
> So 'touch tmp' has a side effect. You may notice this by watching
> 'cat /proc/slabinfo | grep dentry' while running the following
> script:
I tried to reproduce this on my system using an EXT3 filesystem, leaving 
the script running the entire night. When I wake up I found that the 
system disk was full. So, besides the memory issue, this problem also 
consume some bytes on your filesystem.
--
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/