From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Mimi Zohar <zohar@linux.ibm.com>
Cc: paulmck@kernel.org, jmorris@namei.org,
linux-kernel@vger.kernel.org, madhuparnabhowmik10@gmail.com,
linux-security-module@vger.kernel.org, joel@joelfernandes.org,
linux-integrity@vger.kernel.org,
linux-kernel-mentees@lists.linuxfoundation.org, serge@hallyn.com
Subject: Re: [Linux-kernel-mentees] [PATCH] integrity: evm: Fix RCU list related warnings.
Date: Fri, 8 May 2020 11:21:21 +1000 [thread overview]
Message-ID: <20200508112121.6f665d74@canb.auug.org.au> (raw)
In-Reply-To: <1588897421.5685.152.camel@linux.ibm.com>
[-- Attachment #1.1: Type: text/plain, Size: 429 bytes --]
Hi Mimi,
On Thu, 07 May 2020 20:23:41 -0400 Mimi Zohar <zohar@linux.ibm.com> wrote:
>
> Sorry for the delay in pushing this and other fixes to the next-
> integrity branch. It's in my next-integrity-testing branch.
OK, thanks.
> This isn't a bug per-se, just annotating the reason for the lack of
> locking.
Yes, but these warnings stop the syzbot's testing in its tracks :-(
--
Cheers,
Stephen Rothwell
[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 201 bytes --]
_______________________________________________
Linux-kernel-mentees mailing list
Linux-kernel-mentees@lists.linuxfoundation.org
https://lists.linuxfoundation.org/mailman/listinfo/linux-kernel-mentees
prev parent reply other threads:[~2020-05-08 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-30 16:02 [Linux-kernel-mentees] [PATCH] integrity: evm: Fix RCU list related warnings madhuparnabhowmik10
2020-04-30 16:25 ` Paul E. McKenney
2020-05-08 0:14 ` Stephen Rothwell
2020-05-08 0:23 ` Mimi Zohar
2020-05-08 1:21 ` Stephen Rothwell [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=20200508112121.6f665d74@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=jmorris@namei.org \
--cc=joel@joelfernandes.org \
--cc=linux-integrity@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=madhuparnabhowmik10@gmail.com \
--cc=paulmck@kernel.org \
--cc=serge@hallyn.com \
--cc=zohar@linux.ibm.com \
/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).