From: Greg KH <gregkh@linuxfoundation.org>
To: Eric Schultz <eric@startuperic.com>
Cc: stable@vger.kernel.org
Subject: Re: 4.4.16: ovl: BUG() in notify_change()
Date: Wed, 3 Aug 2016 07:45:36 +0200 [thread overview]
Message-ID: <20160803054536.GC6711@kroah.com> (raw)
In-Reply-To: <5896D6A2-5595-4938-A189-F58BA6FA6E75@startuperic.com>
On Sat, Jul 30, 2016 at 10:28:16AM -0500, Eric Schultz wrote:
> Hey Greg,
>
> Apologies in advance if this isn’t the correct method or channel to report bugs
> with kernel 4.4.16.
>
> Commit c12dada5f28a4894b81df2666c060f5cecc02cf9 was included in kernel 4.4.16
> but relies on its parent upstream commit
> b99c2d913810e56682a538c9f2394d76fca808f8, currently missing from
> 4.4.16, otherwise BUG() is thrown for certain operations in overlayfs (I’m able
> to reproduce the issue). I can confirm porting upstream commit
> b99c2d913810e56682a538c9f2394d76fca808f8 in to kernel 4.4.16 solves the issues.
> Please let me know if I could help out in any other way.
This patch does not apply to the 4.4.y stable tree, can you provide a
backport?
thanks,
greg k-h
next parent reply other threads:[~2016-08-03 5:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5896D6A2-5595-4938-A189-F58BA6FA6E75@startuperic.com>
2016-08-03 5:45 ` Greg KH [this message]
2016-08-03 10:02 ` 4.4.16: ovl: BUG() in notify_change() Eric Schultz
2016-08-03 13:28 ` Greg KH
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=20160803054536.GC6711@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=eric@startuperic.com \
--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;
as well as URLs for NNTP newsgroup(s).