Historical speck list archives
 help / color / mirror / Atom feed
From: "Stewart, David C" <david.c.stewart@intel.com>
To: speck@linutronix.de
Subject: [MODERATED] Re: Debian problem with Slow Randomizing Boosts DoS
Date: Mon, 8 Jun 2020 20:08:12 +0000	[thread overview]
Message-ID: <5813C7A9-BD34-40C5-B4AB-558EDC88E73C@intel.com> (raw)
In-Reply-To: <20200608190621.GA2189328@eldamar.local>

Salvatore - thank you for the heads up. We made folks here at Intel aware. Thanks also for the process improvement.

Dave

On 6/8/20, 12:07 PM, "speck for Salvatore Bonaccorso" <speck@linutronix.de> wrote:

> A human error caused today that the changelog entry for the planned
> 4.9.210-1+deb9u1 upload in Debian covering the SRBDS mitigation
> changes were for a short time leaked on
> https://tracker.debian.org/linux (the message was sent as well to 56
> subscribers for the tracker entry).

      reply	other threads:[~2020-06-08 20:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-08 19:06 [MODERATED] Debian problem with Slow Randomizing Boosts DoS Salvatore Bonaccorso
2020-06-08 20:08 ` Stewart, David C [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=5813C7A9-BD34-40C5-B4AB-558EDC88E73C@intel.com \
    --to=david.c.stewart@intel.com \
    --cc=speck@linutronix.de \
    /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 read-only IMAP folder(s) and NNTP newsgroup(s).