From: Dave Jones <davej@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: vfs: INFO: possible circular locking dependency detected
Date: Wed, 9 May 2012 14:49:09 -0400 [thread overview]
Message-ID: <20120509184909.GA27705@redhat.com> (raw)
In-Reply-To: <CA+1xoqf=fDqJq1ks=fo9B27nGrAEVGArYSddmX49Otxw+jpKJw@mail.gmail.com>
On Wed, May 09, 2012 at 07:13:29PM +0200, Sasha Levin wrote:
> On Wed, May 9, 2012 at 6:37 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > If that's _all_ that happened, I'm not particulary
> > concerned; it's not pretty, but saying "thou shalt not grab ->cred_guard_mutex
> > anywhere in ->read() on anything that has exec bits or might get one" is
> > not too terrible. If that's something else, though, we might have a real
> > problem...
>
> That's probably the case. The proc file got chmodded and exec'ed.
>
> Can we do something to eliminate this false positive though? I can't
> think of anything nice...
>
> btw,
> I've never seen this issue before, even though I run same tests for a
> while now. What could have triggered it now?
Assuming you're running trinity du-jour, I only added fuzzing of execve yesterday.
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Dave Jones <davej@redhat.com>
To: Sasha Levin <levinsasha928@gmail.com>
Cc: Al Viro <viro@zeniv.linux.org.uk>,
linux-fsdevel@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: vfs: INFO: possible circular locking dependency detected
Date: Wed, 9 May 2012 14:49:09 -0400 [thread overview]
Message-ID: <20120509184909.GA27705@redhat.com> (raw)
In-Reply-To: <CA+1xoqf=fDqJq1ks=fo9B27nGrAEVGArYSddmX49Otxw+jpKJw@mail.gmail.com>
On Wed, May 09, 2012 at 07:13:29PM +0200, Sasha Levin wrote:
> On Wed, May 9, 2012 at 6:37 PM, Al Viro <viro@zeniv.linux.org.uk> wrote:
> > If that's _all_ that happened, I'm not particulary
> > concerned; it's not pretty, but saying "thou shalt not grab ->cred_guard_mutex
> > anywhere in ->read() on anything that has exec bits or might get one" is
> > not too terrible. If that's something else, though, we might have a real
> > problem...
>
> That's probably the case. The proc file got chmodded and exec'ed.
>
> Can we do something to eliminate this false positive though? I can't
> think of anything nice...
>
> btw,
> I've never seen this issue before, even though I run same tests for a
> while now. What could have triggered it now?
Assuming you're running trinity du-jour, I only added fuzzing of execve yesterday.
Dave
next prev parent reply other threads:[~2012-05-09 18:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-09 15:25 vfs: INFO: possible circular locking dependency detected Sasha Levin
2012-05-09 16:12 ` Al Viro
2012-05-09 16:23 ` Sasha Levin
2012-05-09 16:28 ` Al Viro
2012-05-09 16:36 ` Sasha Levin
2012-05-09 16:37 ` Al Viro
2012-05-09 17:13 ` Sasha Levin
2012-05-09 18:49 ` Dave Jones [this message]
2012-05-09 18:49 ` Dave Jones
2012-05-09 16:25 ` Al Viro
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=20120509184909.GA27705@redhat.com \
--to=davej@redhat.com \
--cc=levinsasha928@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.