linux-kernel - Re: [LKP] [fanotify] 66ba93c0d7f: i6300esb: Unexpected close, not stopping watchdog!

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:	Fri, 24 Apr 2015 10:42:09 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Huang Ying <ying.huang@...el.com>
Cc:	Lino Sanfilippo <LinoSanfilippo@....de>,
	Linus Torvalds <torvalds@...ux-foundation.org>,
	LKML <linux-kernel@...r.kernel.org>, LKP ML <lkp@...org>
Subject: Re: [LKP] [fanotify] 66ba93c0d7f: i6300esb: Unexpected close, not
 stopping watchdog!

On Thu, 23 Apr 2015 14:25:38 +0800 Huang Ying <ying.huang@...el.com> wrote:

> FYI, we noticed the below changes on
> 
> git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master
> commit 66ba93c0d7fe63def447ad0afe380307ff9ebcad ("fanotify: don't set FAN_ONDIR implicitly on a marks ignored mask")
> 
> When doing LTP test.  Test system hang after doing some fanotify test cases, while system
> can run to reboot in the parent comments.

Thanks.  I've queued a reversion patch.  I'll hold off sending it to
Linus for a while, to see if we can get this fixed up.


What does "hang" mean?  Was the machine all locked up?  Or is it the
case that the particular LTP test failed to complete?  I suspect the
latter - that the new notify behaviour is differing from LTP's
expectation in some fashion?

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