linux-kernel - Re: XFS Lock debugging noise or real problem?

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]

Date:	Wed, 13 Aug 2008 18:04:16 -0700
From:	Linda Walsh <xfs@...nx.org>
To:	xfs-oss <xfs@....sgi.com>, LKML <linux-kernel@...r.kernel.org>,
	Eric Sandeen <sandeen@...deen.net>,
	Dave Chinner <david@...morbit.com>
Subject: Re: XFS Lock debugging noise or real problem?

Dave Chinner wrote:
> I've asked the lockdep ppl to treat stuff like memory reclaim and
> the iprune_mutex specially because of this recursive calling nature
> of memory reclaim, but so far nothing has happened....
---
	So it's really a kernel bug, not an XFS bug...(?)


> FWIW, I think that recent changes have resulted in the xfs_fsr case
> (swap_extents) being annotated properly so that one should go
> away.
---
	If it was limited to xfs_fsr, that'd be tolerable -- but its
cropping up in random user-level-apps (imaps, sort, et al).



> Well, any debugging code is really designed for test and dev systems,
> not for production systems.....
---
	The lock-correctness code is described as a feature to provide
"provability".  It's not called "debugging" and I don't regard that as
"debugging" -- but something that any production system that wants
operational integrity over a minor 'speed hit', would "theoretically"
want.

	If it is "debug" code, it should be labeled as such -- but
code that can mathematically guarantee that parts of the kernel operate
correctly seems like a _reliability_ feature, not a debugging feature.

	Thanks for the insight -- very appreciated.

linda


--
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/