From: Greg KH <gregkh@linuxfoundation.org>
To: Hugh Dickins <hughd@google.com>
Cc: kirill.shutemov@linux.intel.com, akpm@linux-foundation.org,
tonyb@cybernetics.com, torvalds@linux-foundation.org,
stable@vger.kernel.org, stable-commits@vger.kernel.org
Subject: Re: Patch "ipc/shm: fix crash if CONFIG_SHMEM is not set" has been added to the 4.7-stable tree
Date: Wed, 28 Sep 2016 08:06:52 +0200 [thread overview]
Message-ID: <20160928060652.GB26329@kroah.com> (raw)
In-Reply-To: <alpine.LSU.2.11.1609271444540.3314@eggly.anvils>
On Tue, Sep 27, 2016 at 02:53:52PM -0700, Hugh Dickins wrote:
> On Tue, 27 Sep 2016, gregkh@linuxfoundation.org wrote:
> >
> > This is a note to let you know that I've just added the patch titled
> >
> > ipc/shm: fix crash if CONFIG_SHMEM is not set
> >
> > to the 4.7-stable tree which can be found at:
> > http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary
> >
> > The filename of the patch is:
> > ipc-shm-fix-crash-if-config_shmem-is-not-set.patch
> > and it can be found in the queue-4.7 subdirectory.
> >
> > If you, or anyone else, feels it should not be added to the stable tree,
> > please let <stable@vger.kernel.org> know about it.
>
> The <stable@vger.kernel.org> [4.7.x] tag was mistakenly added to this
> commit: the commit to be fixed went into v4.8-rc1, and there is no
> reason to expect that it will ever be backported to 4.7.x. I don't
> think this change to ramfs will do any actual harm in 4.7.x, but it
> is rather odd to include it.
Ok, now dropped, thanks for letting me know.
greg k-h
prev parent reply other threads:[~2016-09-28 6:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-27 15:04 Patch "ipc/shm: fix crash if CONFIG_SHMEM is not set" has been added to the 4.7-stable tree gregkh
2016-09-27 21:53 ` Hugh Dickins
2016-09-28 6:06 ` 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=20160928060652.GB26329@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=akpm@linux-foundation.org \
--cc=hughd@google.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=stable-commits@vger.kernel.org \
--cc=stable@vger.kernel.org \
--cc=tonyb@cybernetics.com \
--cc=torvalds@linux-foundation.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