All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: ltp@lists.linux.it
Subject: [LTP] FAILED: patch "[PATCH] ovl: hash non-dir by lower inode for fsnotify" failed to apply to 4.14-stable tree
Date: Thu, 5 Jul 2018 17:57:10 +0200	[thread overview]
Message-ID: <20180705155710.GA20455@kroah.com> (raw)
In-Reply-To: <CABdQkv9mUMF_ewvE2_7AUXpxoS2ZUcbnxo+iL3yF3FU-aVLkBQ@mail.gmail.com>

On Thu, Jul 05, 2018 at 12:53:24PM -0300, Rafael David Tinoco wrote:
> > What bug?  Please never top-post, you loose all context :(
> 
> Won't happen again.
> 
> Summary is this:
> 
> commit 764baba80168ad3adafb521d2ab483ccbc49e344
> Author: Amir Goldstein <amir73il@gmail.com>
> Date:   Sun Feb 4 15:35:09 2018 +0200
> 
>     ovl: hash non-dir by lower inode for fsnotify
> 
> INFO: inotify issue with non-dir non-upper files in overlayfs exists
> in LTS <= v4.14.
> INFO: LTP inotify08 test fails on * v4.14 and bellow * and should be skipped.
> 
> And message was informative only (clearly didn't work). Either way, do
> you think it's worth informing existing LTS bugs, found by test
> tooling, here ?

Why can't we fix those bugs in the stable kernel releases?  Is it too
difficult to do so?

thanks,

greg k-h

WARNING: multiple messages have this Message-ID (diff)
From: Greg KH <gregkh@linuxfoundation.org>
To: Rafael David Tinoco <rafael.tinoco@linaro.org>
Cc: stable@vger.kernel.org, amir73il@gmail.com, mszeredi@redhat.com,
	ltp@lists.linux.it
Subject: Re: FAILED: patch "[PATCH] ovl: hash non-dir by lower inode for fsnotify" failed to apply to 4.14-stable tree
Date: Thu, 5 Jul 2018 17:57:10 +0200	[thread overview]
Message-ID: <20180705155710.GA20455@kroah.com> (raw)
In-Reply-To: <CABdQkv9mUMF_ewvE2_7AUXpxoS2ZUcbnxo+iL3yF3FU-aVLkBQ@mail.gmail.com>

On Thu, Jul 05, 2018 at 12:53:24PM -0300, Rafael David Tinoco wrote:
> > What bug?  Please never top-post, you loose all context :(
> 
> Won't happen again.
> 
> Summary is this:
> 
> commit 764baba80168ad3adafb521d2ab483ccbc49e344
> Author: Amir Goldstein <amir73il@gmail.com>
> Date:   Sun Feb 4 15:35:09 2018 +0200
> 
>     ovl: hash non-dir by lower inode for fsnotify
> 
> INFO: inotify issue with non-dir non-upper files in overlayfs exists
> in LTS <= v4.14.
> INFO: LTP inotify08 test fails on * v4.14 and bellow * and should be skipped.
> 
> And message was informative only (clearly didn't work). Either way, do
> you think it's worth informing existing LTS bugs, found by test
> tooling, here ?

Why can't we fix those bugs in the stable kernel releases?  Is it too
difficult to do so?

thanks,

greg k-h

  reply	other threads:[~2018-07-05 15:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-12 15:02 FAILED: patch "[PATCH] ovl: hash non-dir by lower inode for fsnotify" failed to apply to 4.14-stable tree gregkh
2018-07-05 15:11 ` [LTP] " Rafael David Tinoco
2018-07-05 15:11   ` Rafael David Tinoco
2018-07-05 15:18   ` [LTP] " Greg KH
2018-07-05 15:18     ` Greg KH
2018-07-05 15:27     ` [LTP] " Rafael David Tinoco
2018-07-05 15:27       ` Rafael David Tinoco
2018-07-05 15:30       ` [LTP] " Greg KH
2018-07-05 15:30         ` Greg KH
2018-07-05 15:53         ` [LTP] " Rafael David Tinoco
2018-07-05 15:53           ` Rafael David Tinoco
2018-07-05 15:57           ` Greg KH [this message]
2018-07-05 15:57             ` Greg KH
2018-07-05 16:15             ` [LTP] " Rafael David Tinoco
2018-07-05 16:15               ` Rafael David Tinoco
2018-07-05 16:32               ` [LTP] " Greg KH
2018-07-05 16:32                 ` Greg KH
2018-07-05 16:41                 ` [LTP] " Rafael David Tinoco
2018-07-05 16:41                   ` Rafael David Tinoco
2018-07-05 18:28                 ` Amir Goldstein
2018-07-10 13:55                   ` Greg KH
2018-07-10 14:16                     ` Rafael David Tinoco
2018-07-10 14:39                       ` Amir Goldstein
2018-07-10 15:00                         ` Rafael David Tinoco
2018-07-11  8:07                         ` Jan Kara
2018-07-11 11:37                           ` Rafael David Tinoco

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=20180705155710.GA20455@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=ltp@lists.linux.it \
    /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.