From: Theodore Ts'o <tytso@mit.edu>
To: Stephen Rothwell <sfr@canb.auug.org.au>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org
Subject: Re: [GIT PULL] /dev/random driver changes for 4.8
Date: Mon, 25 Jul 2016 10:24:07 -0400 [thread overview]
Message-ID: <20160725142407.GG10966@thunk.org> (raw)
In-Reply-To: <20160725171515.737d61ae@canb.auug.org.au>
On Mon, Jul 25, 2016 at 05:15:15PM +1000, Stephen Rothwell wrote:
> Hi Ted,
>
> On Mon, 25 Jul 2016 02:44:24 -0400 Theodore Ts'o <tytso@mit.edu> wrote:
> >
> > The following changes since commit 1a695a905c18548062509178b98bc91e67510864:
> >
> > Linux 4.7-rc1 (2016-05-29 09:29:24 -0700)
> >
> > are available in the git repository at:
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tytso/random.git tags/random_for_linus
> >
> > for you to fetch changes up to 86a574de4590ffe6fd3f3ca34cdcf655a78e36ec:
> >
> > random: strengthen input validation for RNDADDTOENTCNT (2016-07-03 17:09:33 -0400)
>
> Of course none of this has been in linux-next since the random tree was
> dropped in March because it had not been updated for more than a year at
> that point.
>
> However, at least half of these look like bug fixes (cced to stable).
>
> Should I reinstate the random tree to linux-next?
Yes, please do. It was getting zero-day checks, and I assumed it was
in linux-next; I should have checked, though.
- Ted
next prev parent reply other threads:[~2016-07-25 14:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 6:44 [GIT PULL] /dev/random driver changes for 4.8 Theodore Ts'o
2016-07-25 7:15 ` Stephen Rothwell
2016-07-25 14:24 ` Theodore Ts'o [this message]
2016-07-25 21:51 ` Stephen Rothwell
2016-07-27 13:12 ` Theodore Ts'o
2016-07-27 22:05 ` Linus Torvalds
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=20160725142407.GG10966@thunk.org \
--to=tytso@mit.edu \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=torvalds@linux-foundation.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.