From: Greg KH <gregkh@linuxfoundation.org>
To: Alakesh Haloi <alakeshh@amazon.com>
Cc: stable@vger.kernel.org, len.brown@intel.com
Subject: Re: Requests for inclusion on linux-4.14.y
Date: Thu, 4 Oct 2018 12:27:00 -0700 [thread overview]
Message-ID: <20181004192700.GA9909@kroah.com> (raw)
In-Reply-To: <20181004183835.GA15503@dev-dsk-alakeshh-2b-5cdffd54.us-west-2.amazon.com>
On Thu, Oct 04, 2018 at 06:38:35PM +0000, Alakesh Haloi wrote:
> Hello Greg,
>
> Can you please consider including the following patch in the stable
> linux-4.14.y branch?
> This is to fix a possible sprintf buffer overflow
>
> 46c2797826cc ("tools/power turbostat: fix possible sprintf buffer overflow")
I'll queue it up, but really, can't you just use the latest userspace
tool on older kernels here?
thanks,
greg k-h
next prev parent reply other threads:[~2018-10-05 2:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-04 18:38 Requests for inclusion on linux-4.14.y Alakesh Haloi
2018-10-04 19:27 ` Greg KH [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-06 18:49 Eduardo Valentin
2018-09-17 11:52 ` 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=20181004192700.GA9909@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=alakeshh@amazon.com \
--cc=len.brown@intel.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).