From: Marc Kleine-Budde <mkl@pengutronix.de>
To: dedekind1@gmail.com
Cc: linux-mtd <linux-mtd@lists.infradead.org>
Subject: Re: SELinux + ubifs: possible circular locking dependency
Date: Wed, 20 Feb 2013 12:19:53 +0100 [thread overview]
Message-ID: <5124B159.1040305@pengutronix.de> (raw)
In-Reply-To: <1360843685.12703.165.camel@sauron.fi.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1731 bytes --]
On 02/14/2013 01:08 PM, Artem Bityutskiy wrote:
> On Thu, 2013-02-14 at 12:56 +0100, Marc Kleine-Budde wrote:
>> On 02/14/2013 08:15 AM, Artem Bityutskiy wrote:
>>> Mark, how about this one? I compiled it and ran on my fedora 16 with
>>> SElinux enabled, no obvious issues.
>>>
>>> From a19350097200570571aa522afebb96b34db534f4 Mon Sep 17 00:00:00 2001
>>> From: Artem Bityutskiy <artem.bityutskiy@linux.intel.com>
>>> Date: Thu, 14 Feb 2013 09:07:36 +0200
>>> Subject: [PATCH] selinux: do not confuse lockdep
>>>
>>> Selinux has per-inode mutexes called 'isec->lock', and they are initialized in
>>> the same place, which makes lockdep treat all of the them as if they were
>>> identical. However, locking rules may be a little bit different depending on
>>> the file-system, so we should put these locks to separate classes, just like we
>>> do for 'i_mutex'. Namely, we should put them to per-FS type classes, which is
>>> exactly what this patch does.
>>>
>>> The problem this patch intends to fix is a strange lockdep warning, which I,
>>> frankly speaking, do not really understand, but I believe the root-cause should
>>> be fixed by this patch.
>>
>> Thanks, this works with mainline, but not with my xattr patch series
>> applied.
>
> Hmm, probably I have to annotate the ui mutex. Let's drop security
> mailing lists from the loop so far, I'll come up with a patch tomorrow.
Do you have a patch I can test?
Marc
--
Pengutronix e.K. | Marc Kleine-Budde |
Industrial Linux Solutions | Phone: +49-231-2826-924 |
Vertretung West/Dortmund | Fax: +49-5121-206917-5555 |
Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
next prev parent reply other threads:[~2013-02-20 11:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-06 11:20 ubifs: possible circular locking dependency Marc Kleine-Budde
[not found] ` <5115076E.3070703@pengutronix.de>
2013-02-13 12:47 ` SELinux + " Artem Bityutskiy
2013-02-13 14:37 ` Marc Kleine-Budde
2013-02-14 6:36 ` Artem Bityutskiy
2013-02-14 7:15 ` Artem Bityutskiy
2013-02-14 11:56 ` Marc Kleine-Budde
2013-02-14 12:08 ` Artem Bityutskiy
2013-02-20 11:19 ` Marc Kleine-Budde [this message]
2013-02-20 11:24 ` Artem Bityutskiy
2013-02-20 11:39 ` 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=5124B159.1040305@pengutronix.de \
--to=mkl@pengutronix.de \
--cc=dedekind1@gmail.com \
--cc=linux-mtd@lists.infradead.org \
/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