linux-kernel - Re: hanging aio process

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]

Date:	Wed, 21 May 2014 09:20:38 -0400
From:	Benjamin LaHaise <bcrl@...ck.org>
To:	Sebastian Ott <sebott@...ux.vnet.ibm.com>
Cc:	Anatol Pomozov <anatol.pomozov@...il.com>, linux-aio@...ck.org,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: hanging aio process

On Wed, May 21, 2014 at 10:48:55AM +0200, Sebastian Ott wrote:
> > 
> > I already did that and it didn't change, always 1 + (1UL << 31) in all
> > cases, before and after percpu_ref_kill(&ctx->reqs). I'm not really
> > familiar with this percpu_ref stuff but it looks like the initial
> > reference is dropped asynchronous.
> 
> 
> cat /sys/kernel/debug/tracing/trace

Your trace still isn't monitoring aio_complete().  You need to check if 
aio_complete() is getting called in order to determine if the bug is in 
the core aio code or not.

		-ben
-- 
"Thought is the essence of where you are now."
--
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/