mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Andrew Morton <akpm@linux-foundation.org>
To: Huang Ying <ying.huang@intel.com>
Cc: Lino Sanfilippo <LinoSanfilippo@gmx.de>,
	Linus Torvalds <torvalds@linux-foundation.org>,
	LKML <linux-kernel@vger.kernel.org>, LKP ML <lkp@01.org>
Subject: Re: [LKP] [fanotify] 66ba93c0d7f: i6300esb: Unexpected close, not stopping watchdog!
Date: Fri, 24 Apr 2015 10:42:09 -0700	[thread overview]
Message-ID: <20150424104209.83834f6a22442b11086a501c@linux-foundation.org> (raw)
In-Reply-To: <1429770338.25120.2.camel@intel.com>

On Thu, 23 Apr 2015 14:25:38 +0800 Huang Ying <ying.huang@intel.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?


  reply	other threads:[~2015-04-24 17:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-23  6:25 Huang Ying
2015-04-24 17:42 ` Andrew Morton [this message]
2015-04-24 20:52   ` Lino Sanfilippo
2015-05-04  0:49   ` Huang Ying

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150424104209.83834f6a22442b11086a501c@linux-foundation.org \
    --to=akpm@linux-foundation.org \
    --cc=LinoSanfilippo@gmx.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkp@01.org \
    --cc=torvalds@linux-foundation.org \
    --cc=ying.huang@intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®