From: Greg KH <greg@kroah.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Henry Jensen <hjensen@gmx.de>,
Tyler Hicks <tyhicks@canonical.com>,
ecryptfs@vger.kernel.org, Jann Horn <jann@thejh.net>,
stable@vger.kernel.org
Subject: Re: [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it
Date: Wed, 3 Aug 2016 05:49:27 +0200 [thread overview]
Message-ID: <20160803034927.GA31125@kroah.com> (raw)
In-Reply-To: <2d10394e-b255-92b0-f378-a164cd731b9e@suse.com>
On Tue, Aug 02, 2016 at 09:05:04AM -0400, Jeff Mahoney wrote:
> On 8/2/16 8:50 AM, Henry Jensen wrote:
> > Hello,
> >
> > is there any new status? We are meanwhile at kernel 4.4.16 LTS and
> > ecryptfs is still broken there.
>
> The revert and the fix below, plus Tyler's cleanup, landed in 4.7. Both
> were tagged for inclusion in -stable but haven't landed there yet. I'm
> afraid that's the limit of my tracking of it.
Yes, that's all you need to do. I'll be queueing these up soon, I have
200+ stable patches to process at this point in time.
Henry, there's nothing preventing you from adding these to your local
trees if you need them.
thanks,
greg k-h
prev parent reply other threads:[~2016-08-03 3:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-05 21:32 [PATCH 1/2] Revert "ecryptfs: forbid opening files without mmap handler" jeffm
2016-07-05 21:32 ` [PATCH 2/2] ecryptfs: don't allow mmap when the lower fs doesn't support it jeffm
2016-07-05 21:57 ` Jann Horn
2016-07-07 23:22 ` Tyler Hicks
2016-07-07 23:20 ` Tyler Hicks
2016-07-08 0:46 ` Jeff Mahoney
2016-08-02 12:50 ` Henry Jensen
2016-08-02 13:05 ` Jeff Mahoney
2016-08-03 3:49 ` Greg KH [this message]
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=20160803034927.GA31125@kroah.com \
--to=greg@kroah.com \
--cc=ecryptfs@vger.kernel.org \
--cc=hjensen@gmx.de \
--cc=jann@thejh.net \
--cc=jeffm@suse.com \
--cc=stable@vger.kernel.org \
--cc=tyhicks@canonical.com \
/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.