Linux Security Modules development
 help / color / mirror / Atom feed
From: james.l.morris@oracle.com (James Morris)
To: linux-security-module@vger.kernel.org
Subject: [PATCH] KEYS: trusted: fix writing past end of buffer in trusted_read()
Date: Wed, 1 Nov 2017 17:55:15 +1100 (AEDT)	[thread overview]
Message-ID: <alpine.LFD.2.20.1711011754050.6046@localhost> (raw)
In-Reply-To: <20171026205744.105566-1-ebiggers3@gmail.com>

On Thu, 26 Oct 2017, Eric Biggers wrote:

> From: Eric Biggers <ebiggers@google.com>


David, this needs to go to Linus.

Are you planning on pushing out more fixes for this -rc or shuld I just 
send it up via my tree?


-- 
James Morris
<james.l.morris@oracle.com>

--
To unsubscribe from this list: send the line "unsubscribe linux-security-module" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2017-11-01  6:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 20:57 [PATCH] KEYS: trusted: fix writing past end of buffer in trusted_read() Eric Biggers
2017-10-26 23:57 ` Mimi Zohar
2017-10-27  7:55 ` James Morris
2017-11-01  6:55 ` James Morris [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=alpine.LFD.2.20.1711011754050.6046@localhost \
    --to=james.l.morris@oracle.com \
    --cc=linux-security-module@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