linux-kernel - Re: [PATCH 000 of 14] knfsd: Assorted nfsd patches for 2.6.20

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: <17791.57459.23780.747689@cse.unsw.edu.au>
Date:	Wed, 13 Dec 2006 22:13:55 +1100
From:	Neil Brown <neilb@...e.de>
To:	Jeff Garzik <jeff@...zik.org>
Cc:	Andrew Morton <akpm@...l.org>, nfs@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 000 of 14] knfsd: Assorted nfsd patches for 2.6.20 - prepare
 for IPv6 and more

On Wednesday December 13, jeff@...zik.org wrote:
> NeilBrown wrote:
> > Following are 14 patches for knfsd that are suitable for inclusion in 2.6.20.
> > First 13 are from Chuck Lever and make preparations for IPv6 support (I think we've
> > get them right this time).
> > 
> > Last is from Peter Staubach and fixes and issue with exclusive create
> > interacting badly with some ACLs.
> 
> 
> Any word on this 2.6.19 oops?
> 
> http://lkml.org/lkml/2006/12/8/110

Not yet... I've been spending my spare time looking for an md oops :-)

A quick look suggests that it cannot possibly happen ...

cancel_rearming_delayed_workqueue appears to be being called with a
bad "struct workqueue_struct *".  But that really must have been
initialised when the first nfsd thread started...

It looks like cwq in flush_cpu_workqueue is 0x0000040000000100.  Is
that the sort of address you would expect?  Where do alloc_percpu 
data structures live?  The '4' wouldn't be a single-bit memory error,
would it? (that would be too easy).

So: no, no real progress.   Is it repeatable?

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