From: Huang Ying <ying.huang@intel.com>
To: lkp@lists.01.org
Subject: Re: [fanotify] 66ba93c0d7f: i6300esb: Unexpected close, not stopping watchdog!
Date: Mon, 04 May 2015 08:49:07 +0800 [thread overview]
Message-ID: <1430700547.25120.132.camel@intel.com> (raw)
In-Reply-To: <20150424104209.83834f6a22442b11086a501c@linux-foundation.org>
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
Hi, Andrew,
Sorry for late. I am in vacation in last week.
On Fri, 2015-04-24 at 10:42 -0700, Andrew Morton wrote:
> 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?
Sorry for confusion. The machine was not locked up, just the LTP test
failed to complete.
Best Regards,
Huang, Ying
WARNING: multiple messages have this Message-ID (diff)
From: Huang Ying <ying.huang@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
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: Mon, 04 May 2015 08:49:07 +0800 [thread overview]
Message-ID: <1430700547.25120.132.camel@intel.com> (raw)
In-Reply-To: <20150424104209.83834f6a22442b11086a501c@linux-foundation.org>
Hi, Andrew,
Sorry for late. I am in vacation in last week.
On Fri, 2015-04-24 at 10:42 -0700, Andrew Morton wrote:
> 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?
Sorry for confusion. The machine was not locked up, just the LTP test
failed to complete.
Best Regards,
Huang, Ying
next prev parent reply other threads:[~2015-05-04 0:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-23 6:25 [fanotify] 66ba93c0d7f: i6300esb: Unexpected close, not stopping watchdog! Huang Ying
2015-04-23 6:25 ` [LKP] " Huang Ying
2015-04-24 17:42 ` Andrew Morton
2015-04-24 17:42 ` [LKP] " Andrew Morton
2015-04-24 20:52 ` Lino Sanfilippo
2015-05-04 0:49 ` Huang Ying [this message]
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=1430700547.25120.132.camel@intel.com \
--to=ying.huang@intel.com \
--cc=lkp@lists.01.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.