Re: [PATCH] tpm: Revert "tpm: fix invalid locking in NONBLOCKING mode"

From: Alex Guzman <alex@guzman.io>
To: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>,
	Mario.Limonciello@dell.com,
	James.Bottomley@HansenPartnership.com, peterhuewe@gmx.de,
	jgg@ziepe.ca
Cc: arnd@arndb.de, gregkh@linuxfoundation.org,
	linux-integrity@vger.kernel.org, jeffrin@rajagiritech.edu.in
Subject: Re: [PATCH] tpm: Revert "tpm: fix invalid locking in NONBLOCKING mode"
Date: Wed, 27 May 2020 18:10:02 -0700	[thread overview]
Message-ID: <a5e2a176faa272a0edc8737c1ef1bf5b3c278f63.camel@guzman.io> (raw)
In-Reply-To: <d6b4591c49f01f24b0dbfd25c8792a3f506d6cae.camel@linux.intel.com>

On Wed, 2020-05-27 at 23:15 +0300, Jarkko Sakkinen wrote:
> On Tue, 2020-05-26 at 19:23 +0000, Mario.Limonciello@dell.com wrote:
> > Thanks, I don't pretend to understand the nuances of this
> > particular code,
> > but I was hoping that the request to revert got some attention
> > since Alex's
> > kernel Bugzilla and message a few months ago to linux integrity
> > weren't.
> 
> Removing linux-kernel from CC since this subsystem internal
> discussion.
> 
> Seeing the whole thing first time today.
> 
> Bugzilla is the first thing to ignore when busy. It is good as place
> holder for bugs, but all discussions should happen only in LKML.
> There's
> no official requirement to proactively use Bugzilla for anything.
> 
> That said I'm happy that people put stuff there so that it gets
> logged.
> 
> For follow-up's use only LKML if it is important to you. Those will
> get
> processed.
> 
> As far as this goes, if nothing is heard from me, check that you put
> me
> as CC to the original email. Otherwise, I might have missed it (by
> mistake,
> not by purpose).
> 
> Honestly, I'm not sure what point was this patch when there was time
> to
> wait for months without response. Why the passivity for all this
> time?
> 
> /Jarkko
> 

It largely went quiet because I didn't raise the issue in the mailing
list again. I pinged back in February (
https://lore.kernel.org/linux-integrity/CAJ7-PMbujee92N1f9xVF8vtXgS49qpe7qHkeWh1Z0R-Rk-Jkaw@mail.gmail.com/
) but the conversation died out and I was content to simply use the
last working kernel version and see if the bug was resolved on its own.
I raised the issue again on the bugtracker a few days ago, leading to
this follow up here. :)

- Alex