From: Jarkko Sakkinen <jarkko.sakkinen-VuQAYsv1563Yd54FQh9/CA@public.gmane.org>
To: James Morris <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
Cc: keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
Wilck-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org
Subject: Re: [GIT PULL] remaining tpmdd fixes for Linux 4.5
Date: Fri, 26 Feb 2016 11:48:29 +0200 [thread overview]
Message-ID: <20160226094829.GA16207@intel.com> (raw)
In-Reply-To: <alpine.LRH.2.20.1602261438340.17858-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
On Fri, Feb 26, 2016 at 02:38:52PM +1100, James Morris wrote:
> On Thu, 25 Feb 2016, Jerry Snitselaar wrote:
>
> > On Mon Feb 22 16, Jarkko Sakkinen wrote:
> > >On Mon, Feb 22, 2016 at 12:56:53PM +1100, James Morris wrote:
> > > > On Sat, 20 Feb 2016, Jarkko Sakkinen wrote:
> > > >
> > > > > Hi James,
> > > > >
> > > > > I'm sorry for the late pull request for 4.5. The reason for this was
> > > > > the latency in my previous one. I picked with care the absolutely
> > > > > critical fixes so that we can make a sound tpmdd release.
> > > > >
> > > > > I really hope you can still pick these as one of them is absolutely
> > > > > critical to get authorization policy sealing API right (kernel keeps
> > > > > it finger out of user space created objects).
> > > >
> > > > Pushed to next for more testing and review.
> > > >
> > > > This really is getting too late in the development cycle for so many
> > > > fixes. It means the code was not ready to be merged in the first place.
> > >
> > >I fully agree what you're saying. I'll learn the lesson here and take
> > >factors more conservative attitude from now on. No excuses. I'm sorry
> > >about this.
> > >
> > >Partly the reason for recent increase in regressions has been
> > >increased real-world use of TPM2 and thus issues have started to pop
> > >up that's a lame excuse anyway.
> > >
> >
> > Would it be worthwhile to have a tpm branch that gets pulled by -next
> > directly so changes will have already been going through the paces in
> > -next prior to the pull reuqest to James?
>
> That would be useful, some other subsystems do that.
I'll start using it.
> --
> James Morris
> <jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
/Jarkko
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
next prev parent reply other threads:[~2016-02-26 9:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 8:17 [GIT PULL] remaining tpmdd fixes for Linux 4.5 Jarkko Sakkinen
[not found] ` <20160220081705.GA12981-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-02-22 1:56 ` James Morris
[not found] ` <alpine.LRH.2.20.1602221255210.4918-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
2016-02-22 14:50 ` Jarkko Sakkinen
[not found] ` <20160222145023.GA28365-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org>
2016-02-22 17:52 ` Jason Gunthorpe
2016-02-22 19:08 ` Jarkko Sakkinen
2016-02-22 19:11 ` Jason Gunthorpe
2016-02-22 21:23 ` Jarkko Sakkinen
2016-02-25 17:30 ` Jerry Snitselaar
[not found] ` <20160225173044.gcr2j65ihv6cevzm-8w2GRY7Bv7UXGNroddHbYwC/G2K4zDHf@public.gmane.org>
2016-02-26 3:38 ` James Morris
[not found] ` <alpine.LRH.2.20.1602261438340.17858-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
2016-02-26 9:48 ` Jarkko Sakkinen [this message]
2016-02-26 7:57 ` James Morris
[not found] ` <alpine.LRH.2.20.1602261857040.28734-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org>
2016-02-26 9:00 ` Jarkko Sakkinen
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=20160226094829.GA16207@intel.com \
--to=jarkko.sakkinen-vuqaysv1563yd54fqh9/ca@public.gmane.org \
--cc=Wilck-ral2JQCrhuEAvxtiuMwx3w@public.gmane.org \
--cc=jmorris-gx6/JNMH7DfYtjvyW6yDsg@public.gmane.org \
--cc=keyrings-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-kernel-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-security-module-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=tpmdd-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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).