linux-kernel - Unallocate inodes created with new

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>] [day] [month] [year] [list]

Message-ID: <op.ua2z8tcrpodc4a@twindruff>
Date:	Tue, 13 May 2008 09:25:31 +0200
From:	BoozooK <boozook@...e.fr>
To:	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Unallocate inodes created with new_inode()

Hello,
I'm currently writing a simple read-only filesystem based on a device. I  
use the new_inode function (which is defined in inode.c) to allocate my  
inodes and my driver holds a list of the allocated inodes in order to  
destroy them in the end, but I don't know how I should destroy them (I  
mean with which function). I currently get a "Busy inodes after unmount"  
message after unmounting my filesystem.

Thanks in advance,
BoozooK.
--
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/