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]
Date:	Thu, 3 Jan 2013 17:26:39 -0500
From:	Tejun Heo <>
To:	"Myklebust, Trond" <>
Cc:	"J. Bruce Fields" <>,
	"Adamson, Dros" <>,
	Dave Jones <>,
	Linux Kernel <>,
	"" <>
Subject: Re: nfsd oops on Linus' current tree.

Hello, Trond.

On Thu, Jan 03, 2013 at 10:12:32PM +0000, Myklebust, Trond wrote:
> > The analysis is likely completely wrong, so please don't go off doing
> > something unnecessary.  Please take look at what's causing the
> > deadlocks again.
> The analysis is a no-brainer:
> We see a deadlock due to one work item waiting for completion of another
> work item that is queued on the same CPU. There is no other dependency
> between the two work items.

What do you mean "waiting for completion of"?  Is one flushing the
other?  Or is one waiting for the other to take certain action?  How
are the two work items related?  Are they queued on the same
workqueue?  Can you create a minimal repro case of the observed


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists