On Mon, Dec 18, 2017 at 2:35 PM, Greg KH <gregkh@xxxxxxxxxxxxxxxxxxx> wrote:
> 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@xxxxxxxxx> wrote:
>> > Conform two stray warning messages to the standard overlayfs: prefix.
>> >
>> > Signed-off-by: Amir Goldstein <amir73il@xxxxxxxxx>
>> > ---
>>
>> 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 :)
Yeh, I thought 4.13 was still around, but it's not...
>
> 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.
>
Not serious at all.
It's just that collecting overlayfs output from kmsg on bug reports
is one notch easier to request.
I can certainly live without it being in a stable.
Thanks,
Amir.