linux-kernel - Re: NULL inode->i_mapping in generic_sync_sb

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: <x497hv7tke4.fsf@segfault.boston.devel.redhat.com>
Date:	Wed, 07 Oct 2009 09:15:47 -0400
From:	Jeff Moyer <jmoyer@...hat.com>
To:	Nick Piggin <npiggin@...e.de>
Cc:	Nick Piggin <npiggin@...ell.com>, Christoph Hellwig <hch@....de>,
	linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: NULL inode->i_mapping in generic_sync_sb_inodes

Nick Piggin <npiggin@...e.de> writes:

>> hch mentioned that it would be good to instrument to what file system
>> the inode belonged.  Anything else you'd like to look at?
>
> Not too sure. I guess i_state. Maybe you could take s_umount lock
> and see if it is still mounted?
>
> Actually most useful will be to find all places where i_mapping is
> set to NULL, and record in the inode some callchain for the last
> site which set i_mapping to NULL. Dump this stack when you hit the
> bug.

Well, I can't find a single place where i_mapping is set to NULL.  ;-)
I'll see what I can dig up.

Cheers,
Jeff
--
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/