From: Artem Bityutskiy <dedekind1@gmail.com>
To: Marc Kleine-Budde <mkl@pengutronix.de>
Cc: linux-mtd@lists.infradead.org,
linux-security-module@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: SELinux + ubifs: possible circular locking dependency
Date: Thu, 14 Feb 2013 08:36:05 +0200 [thread overview]
Message-ID: <1360823765.12703.153.camel@sauron.fi.intel.com> (raw)
In-Reply-To: <511BA51E.9000606@pengutronix.de>
On Wed, 2013-02-13 at 15:37 +0100, Marc Kleine-Budde wrote:
> > + lockdep_set_class(&isec->lock, inode->i_sb->s_type->i_mutex_key);
>
> So I added an "&", so that the line looks like that:
Yeah, I did not compile it, and for the deadlock of course I have to add
own class for isec->lock in the fstype structure. I'll try to come up
with another patch. Thanks!
--
Best Regards,
Artem Bityutskiy
next prev parent reply other threads:[~2013-02-14 6:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <51123C80.2050400@pengutronix.de>
2013-02-08 14:10 ` SELinux + ubifs: possible circular locking dependency Marc Kleine-Budde
2013-02-13 12:47 ` Artem Bityutskiy
2013-02-13 14:37 ` Marc Kleine-Budde
2013-02-14 6:36 ` Artem Bityutskiy [this message]
2013-02-14 7:15 ` Artem Bityutskiy
2013-02-14 11:56 ` Marc Kleine-Budde
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=1360823765.12703.153.camel@sauron.fi.intel.com \
--to=dedekind1@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.org \
--cc=linux-security-module@vger.kernel.org \
--cc=mkl@pengutronix.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