linux-ext4 - Re: freeze

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

Message-ID: <20121009214915.GD27882@quack.suse.cz>
Date:	Tue, 9 Oct 2012 23:49:15 +0200
From:	Jan Kara <jack@...e.cz>
To:	Prashant Shah <pshah.mumbai@...il.com>
Cc:	Jan Kara <jack@...e.cz>, Eric Sandeen <sandeen@...hat.com>,
	linux-ext4@...r.kernel.org
Subject: Re: freeze_bdev hangs

On Mon 08-10-12 22:05:38, Prashant Shah wrote:
> Hi,
> 
> On Mon, Oct 8, 2012 at 9:49 PM, Jan Kara <jack@...e.cz> wrote:
> >   And what tool are you using for monitoring?
> 
> I am using printk(). A custom module that changes the make_request_fn
> of the block device to a custom callback. In the callback I am
> printing the request bio details and passing the bio back to the
> original make_request_fn.
  OK. There are several ways how I could imagine you hit ino == 0. Either
someone is using direct IO or inode is a block device inode...

								Honza
--
To unsubscribe from this list: send the line "unsubscribe linux-ext4" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html