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
next prev parent reply other threads:[~2020-05-28 1:10 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-26 18:32 [PATCH] tpm: Revert "tpm: fix invalid locking in NONBLOCKING mode" Mario Limonciello
2020-05-26 19:14 ` James Bottomley
2020-05-26 19:23 ` Mario.Limonciello
2020-05-26 19:38 ` James Bottomley
2020-05-26 22:19 ` Alex Guzman
2020-05-26 23:06 ` James Bottomley
2020-05-26 23:31 ` Alex Guzman
2020-05-27 0:18 ` James Bottomley
2020-05-27 20:09 ` Jarkko Sakkinen
2020-05-27 20:18 ` Mario.Limonciello
2020-05-28 0:43 ` Jarkko Sakkinen
2020-05-28 0:59 ` Mario.Limonciello
2020-05-28 6:53 ` Jarkko Sakkinen
2020-05-27 20:15 ` Jarkko Sakkinen
2020-05-28 1:10 ` Alex Guzman [this message]
2020-05-28 6:54 ` Jarkko Sakkinen
2020-05-28 22:33 ` James Bottomley
2020-05-26 19:39 ` Tadeusz Struk
2020-05-26 20:00 ` James Bottomley
2020-05-26 21:33 ` Tadeusz Struk
2020-05-26 22:34 ` Alex Guzman
2020-05-28 0:30 ` Jarkko Sakkinen
2020-05-28 4:40 ` Tadeusz Struk
2020-05-28 6:55 ` 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=a5e2a176faa272a0edc8737c1ef1bf5b3c278f63.camel@guzman.io \
--to=alex@guzman.io \
--cc=James.Bottomley@HansenPartnership.com \
--cc=Mario.Limonciello@dell.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=jarkko.sakkinen@linux.intel.com \
--cc=jeffrin@rajagiritech.edu.in \
--cc=jgg@ziepe.ca \
--cc=linux-integrity@vger.kernel.org \
--cc=peterhuewe@gmx.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 NNTP newsgroup(s).