From: Greg KH <gregkh@linuxfoundation.org>
To: Amir Goldstein <amir73il@gmail.com>
Cc: overlayfs <linux-unionfs@vger.kernel.org>,
Miklos Szeredi <miklos@szeredi.hu>,
stable <stable@vger.kernel.org>
Subject: Re: [PATCH] ovl: fix overlay: warning prefix
Date: Mon, 18 Dec 2017 13:35:30 +0100 [thread overview]
Message-ID: <20171218123530.GA7128@kroah.com> (raw)
In-Reply-To: <CAOQ4uxi9SMM6YY1SYKOns3S4jEa0cuHDt+DiHo8ThSSMWCTgFw@mail.gmail.com>
On Mon, Dec 18, 2017 at 02:19:52PM +0200, Amir Goldstein wrote:
> On Wed, Nov 22, 2017 at 8:27 PM, Amir Goldstein <amir73il@gmail.com> wrote:
> > Conform two stray warning messages to the standard overlayfs: prefix.
> >
> > Signed-off-by: Amir Goldstein <amir73il@gmail.com>
> > ---
>
> Greg,
>
> Upstream commit ("da2e6b7eeda8 ovl: fix overlay: warning prefix")
> was not marked for stable, because it is not a bug fix per-se.
> Nevertheless, it may be useful to apply it to stable kernels to keep
> overlayfs bug reports/analysis consistent.
>
> The first hunk fixes (#v4.10):
> a6c606551141 ovl: redirect on rename-dir
>
> The second hunk fixes (#v4.14):
> b5efccbe0a12 ovl: constant d_ino across copy up
>
> For your consideration.
> If you wish, I can send a patch for v4.10 with just the first hunk.
4.10 is long end-of-life, so I don't think that matters :)
As for 4.14, this is just an error message, I don't think it's that
serious of a fix for a stable kernel, do you? It's _this_ close to just
being a spelling fix.
thanks,
greg k-h
next prev parent reply other threads:[~2017-12-18 12:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-22 18:27 [PATCH] ovl: fix overlay: warning prefix Amir Goldstein
2017-12-11 17:52 ` Amir Goldstein
2017-12-14 10:19 ` Miklos Szeredi
2017-12-18 12:19 ` Amir Goldstein
2017-12-18 12:35 ` Greg KH [this message]
2017-12-18 12:43 ` Amir Goldstein
-- strict thread matches above, loose matches on Subject: below --
2018-01-10 9:17 Chengguang Xu
2018-01-10 11:45 ` Amir Goldstein
2018-01-10 11:59 ` Chengguang Xu
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=20171218123530.GA7128@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amir73il@gmail.com \
--cc=linux-unionfs@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=stable@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox