All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Rasmus Bøg Hansen" <rasmus-tUP8e6pgWdNlY7y4Fx5NiA@public.gmane.org>
To: David Howells <dhowells@redhat.com>
Cc: bfields@fieldses.org, linux-nfs@vger.kernel.org
Subject: Re: PROBLEM: nfsd crashes in 2.6.29
Date: Tue, 28 Apr 2009 22:07:06 +0200	[thread overview]
Message-ID: <49F761EA.1080303@msconsult.dk> (raw)
In-Reply-To: <25153.1240939886@redhat.com>

David Howells skrev:
> J. Bruce Fields <bfields@fieldses.org> wrote:
>=20
>>>> Without trying to figure out where that is, just looking at the
>>>> offset...  That would be consistent with current_cred()->security =
being
>>>> NULL, since the cred_sid(cred) in inode_has_perm does tsec->sid, w=
here
>>>> tsec is
>=20
> It oughtn't to be possible...  Unless, perhaps, the credentials have =
been
> freed.  During the process of freeing the creds, the security pointer=
 is
> cleared.
>=20
> Are you running with CONFIG_DEBUG_SLAB=3Dn?  If so, would it be possi=
ble to flip
> it to =3Dy?

I have it turned off and now I am running 2.6.29.2 fine without selinux=
=20
(which I didn't use).

I can try to turn it on but I won't be near the server for about two=20
weeks as I am going on a training course and noone else uses the NFS se=
rver.

Regards
/Rasmus

--=20
Rasmus B=F8g Hansen
MSC Aps
B=F8gesvinget 8
2740 Skovlunde
44 53 93 66

      reply	other threads:[~2009-04-28 20:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-31 13:21 PROBLEM: nfsd crashes in 2.6.29 Rasmus Bøg Hansen
     [not found] ` <49D218C8.2040503-tUP8e6pgWdNlY7y4Fx5NiA@public.gmane.org>
2009-04-01 18:57   ` J. Bruce Fields
     [not found]     ` <20090402105943.14031ff3mhfka6bk@ssl.msconsult.dk>
     [not found]       ` <20090428164133.GP17891@fieldses.org>
2009-04-28 17:31         ` David Howells
2009-04-28 20:07           ` Rasmus Bøg Hansen [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=49F761EA.1080303@msconsult.dk \
    --to=rasmus-tup8e6pgwdnly7y4fx5nia@public.gmane.org \
    --cc=bfields@fieldses.org \
    --cc=dhowells@redhat.com \
    --cc=linux-nfs@vger.kernel.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 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.