From: Prarit Bhargava <prarit@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: Eric Sandeen <esandeen@redhat.com>, xfs@oss.sgi.com
Subject: Re: lockdep warning when logging in with ssh
Date: Wed, 10 Sep 2014 18:40:15 -0400 [thread overview]
Message-ID: <5410D34F.1030404@redhat.com> (raw)
In-Reply-To: <20140910202348.GC27048@dastard>
On 09/10/2014 04:23 PM, Dave Chinner wrote:
> On Wed, Sep 10, 2014 at 02:59:31PM -0400, Prarit Bhargava wrote:
>> I see this when I attempt to login via ssh. I do not see it if I login on
>> the serial console. I recall seeing it earlier when chasing another patch but
>> cannot recall the kernel version.
>
> It's the shmem code that is broken - instantiating an inode while
> holding the mmap_sem inverts lock orders all over the place,
> especially in the security subsystem....
>
I'll send this off to Hugh Dickens then.
P.
> Cheers,
>
> Dave.
>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2014-09-10 22:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-10 18:59 lockdep warning when logging in with ssh Prarit Bhargava
2014-09-10 20:23 ` Dave Chinner
2014-09-10 22:40 ` Prarit Bhargava [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=5410D34F.1030404@redhat.com \
--to=prarit@redhat.com \
--cc=david@fromorbit.com \
--cc=esandeen@redhat.com \
--cc=xfs@oss.sgi.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