From: Greg KH <gregkh@linuxfoundation.org>
To: Amit Pundir <amit.pundir@linaro.org>
Cc: stable@vger.kernel.org
Subject: Re: [PATCH for-3.18 0/7] Security fixes picked from android security bulletins
Date: Thu, 4 May 2017 12:42:59 -0700 [thread overview]
Message-ID: <20170504194259.GC10166@kroah.com> (raw)
In-Reply-To: <1493832958-12489-1-git-send-email-amit.pundir@linaro.org>
On Wed, May 03, 2017 at 11:05:51PM +0530, Amit Pundir wrote:
> Hi Greg,
>
> Please consider following security fixes for linux-3.18.y.
> I have picked up these fixes from the list of security
> vulnerabilities published in Android Security Bulletins,
> https://source.android.com/security/bulletin/, this year
> so far.
>
> Cherry-picked and build tested on v3.18.51 for
> ARCH=arm/arm64/x86/x86_64/mips + allmodconfig.
Many thanks for these, all now queued up.
greg k-h
prev parent reply other threads:[~2017-05-04 19:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-03 17:35 [PATCH for-3.18 0/7] Security fixes picked from android security bulletins Amit Pundir
2017-05-03 17:35 ` [PATCH for-3.18 1/7] ALSA: pcm : Call kill_fasync() in stream lock Amit Pundir
2017-05-03 17:35 ` [PATCH for-3.18 2/7] regulator: core: Fix regualtor_ena_gpio_free not to access pin after freeing Amit Pundir
2017-05-03 17:35 ` [PATCH for-3.18 3/7] perf: Tighten (and fix) the grouping condition Amit Pundir
2017-05-03 17:42 ` Linus Torvalds
2017-05-03 17:58 ` Amit Pundir
2017-05-03 17:35 ` [PATCH for-3.18 4/7] posix_acl: Clear SGID bit when setting file permissions Amit Pundir
2017-05-03 17:35 ` [PATCH for-3.18 5/7] l2tp: fix racy SOCK_ZAPPED flag check in l2tp_ip{,6}_bind() Amit Pundir
2017-05-03 17:35 ` [PATCH for-3.18 6/7] net: avoid signed overflows for SO_{SND|RCV}BUFFORCE Amit Pundir
2017-05-03 17:35 ` [PATCH for-3.18 7/7] mm: avoid setting up anonymous pages into file mapping Amit Pundir
2017-05-04 19:42 ` 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=20170504194259.GC10166@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=amit.pundir@linaro.org \
--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 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.