All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Snild Dolkow <snild@sony.com>
Cc: kregkh@linuxfoundation.org, stable@vger.kernel.org,
	Oleksiy Avramchenko <oleksiy.avramchenko@sony.com>,
	Peter Enderborg <peter.enderborg@sony.com>
Subject: Re: [PATCH RESEND] kthread, tracing: Don't expose half-written comm when creating kthreads
Date: Fri, 7 Sep 2018 11:44:23 +0200	[thread overview]
Message-ID: <20180907094423.GB13327@kroah.com> (raw)
In-Reply-To: <20180904065203.47304-1-snild@sony.com>

On Tue, Sep 04, 2018 at 08:52:03AM +0200, Snild Dolkow wrote:
> I didn't receive any replies on this, and it doesn't seem to have made
> it into the latest 3.18 or 4.4 releases. Previously sent on Aug 23rd:
> https://lists.linaro.org/pipermail/linux-stable-mirror/2018-August/056347.html
> 
> I assume I sent it wrong; maybe missing keywords or recipients? If
> anyone can tell me what I missed, I'd appreciate it.

You didn't miss anything (well, getting my email address wrong wasn't
the best...)  I was just busy with the merge window and all of the other
assorted security mess we have been cleaning up after, combined with
conference travel.

thanks,

greg k-h

  parent reply	other threads:[~2018-09-07 14:24 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-04  6:52 [PATCH RESEND] kthread, tracing: Don't expose half-written comm when creating kthreads Snild Dolkow
2018-09-04  7:00 ` Snild Dolkow
2018-09-07  9:44 ` Greg KH [this message]
2018-09-07  9:51   ` Snild Dolkow
  -- strict thread matches above, loose matches on Subject: below --
2018-07-23 13:42 Snild Dolkow
2018-07-23 13:55 ` Steven Rostedt
2018-07-23 14:23   ` Snild Dolkow
2018-07-23 15:37     ` Steven Rostedt
2018-07-23 15:49       ` Snild Dolkow
2018-07-23 16:41         ` Steven Rostedt
2018-07-24  8:17           ` Snild Dolkow
2018-07-24 14:48             ` Steven Rostedt
2018-07-24 15:02               ` Snild Dolkow

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=20180907094423.GB13327@kroah.com \
    --to=greg@kroah.com \
    --cc=kregkh@linuxfoundation.org \
    --cc=oleksiy.avramchenko@sony.com \
    --cc=peter.enderborg@sony.com \
    --cc=snild@sony.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 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.