From: Greg KH <greg@kroah.com>
To: Jeff Layton <jlayton@kernel.org>
Cc: "stable@vger.kernel.org" <stable@vger.kernel.org>,
Vitaly Lipatov <lav@etersoft.ru>
Subject: Re: please pick 4d2dc2cc766c for v4.14 stable series
Date: Thu, 14 Dec 2017 18:48:10 +0100 [thread overview]
Message-ID: <20171214174810.GH10610@kroah.com> (raw)
In-Reply-To: <1513106225.3372.7.camel@kernel.org>
On Tue, Dec 12, 2017 at 02:17:05PM -0500, Jeff Layton wrote:
> Hi! I neglected to mark this patch for stable when I merged it, and it
> probably should have been, as Vitaly points out that locking for 32-bit
> apps running on a 64-bit kernel is broken. Can you pick this for v4.14
> stable?
>
> commit: 4d2dc2cc766c3b51929658cacbc6e34fc8e242fb
> subject: fcntl: don't cap l_start and l_end values for F_GETLK64 in compat syscall
Now applied, thanks.
greg k-h
prev parent reply other threads:[~2017-12-14 17:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 19:17 please pick 4d2dc2cc766c for v4.14 stable series Jeff Layton
2017-12-14 17:48 ` 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=20171214174810.GH10610@kroah.com \
--to=greg@kroah.com \
--cc=jlayton@kernel.org \
--cc=lav@etersoft.ru \
--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).