From: Mimi Zohar <zohar@linux.ibm.com>
To: Eric Biggers <ebiggers@kernel.org>
Cc: linux-integrity@vger.kernel.org, Al Viro <viro@zeniv.linux.org.uk>
Subject: Re: [RFC PATCH] ima: fix ima_file_mmap circular locking dependency
Date: Sun, 14 Jul 2019 12:48:08 -0400 [thread overview]
Message-ID: <1563122888.4539.119.camel@linux.ibm.com> (raw)
In-Reply-To: <20190712231339.GC701@sol.localdomain>
Hi Eric,
On Fri, 2019-07-12 at 16:13 -0700, Eric Biggers wrote:
> So I suggest just invalidating the report "possible deadlock in
> process_measurement" too, unless you think you think the older overlayfs-related
> deadlock report is still valid and actionable. It doesn't have a reproducer
> and was last seen 5 months ago, so it *might* be stale:
> https://syzkaller.appspot.com/text?tag=CrashReport&x=1767eeef400000
Yes, please invalidate that one as well.
Mimi
prev parent reply other threads:[~2019-07-14 16:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-12 20:41 [RFC PATCH] ima: fix ima_file_mmap circular locking dependency Mimi Zohar
2019-07-12 23:13 ` Eric Biggers
2019-07-14 16:48 ` Mimi Zohar [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=1563122888.4539.119.camel@linux.ibm.com \
--to=zohar@linux.ibm.com \
--cc=ebiggers@kernel.org \
--cc=linux-integrity@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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).