public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Benny Halevy <bhalevy@tonian.com>
To: tao.peng@emc.com
Cc: rees@umich.edu, linux-nfs@vger.kernel.org
Subject: Re: NULL pointer dereference during mount
Date: Wed, 14 Sep 2011 08:31:23 +0200	[thread overview]
Message-ID: <4E704A3B.7080504@tonian.com> (raw)
In-Reply-To: <F19688880B763E40B28B2B462677FBF805C3F37B8D-AYrsSIZi/B2B3McK65YKY9BPR1lH4CV8@public.gmane.org>

I couldn't reproduce this with selinux neither disabled nor enforcing.
What's your selinux configuration?

Benny

On 2011-09-13 18:43, tao.peng@emc.com wrote:
> 
> ________________________________________
> From: Jim Rees [rees@umich.edu]
> Sent: Tuesday, September 13, 2011 8:42 PM
> To: Peng, Tao
> Cc: bhalevy@tonian.com; linux-nfs@vger.kernel.org
> Subject: Re: NULL pointer dereference during mount
> 
> tao.peng@emc.com wrote:
> 
>   After rebasing to your pnfs-all-latest branch, I always got bellow NULL
>   pointer dereference for both nfsv4 and pnfs. Do you know of any recent
>   change that can cause this?
> 
> "git diff" shows no change in the nfs client between my for-benny branch and
> benny's pnfs-all-latest branch.  And the mount works for me.  But the first
> thing I always do on a fresh Fedora install is disable selinux.  Maybe
> something changed in selinux?
> [PT] Just tested 3.1-rc6 and it is working properly. So I think it should be caused by nfs changes.--
> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      parent reply	other threads:[~2011-09-14  6:31 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-09-13 11:55 NULL pointer dereference during mount tao.peng
2011-09-13 12:02 ` tao.peng
     [not found]   ` <F19688880B763E40B28B2B462677FBF805C329A001-AYrsSIZi/B2B3McK65YKY9BPR1lH4CV8@public.gmane.org>
2011-09-13 12:17     ` Benny Halevy
2011-09-13 12:42 ` Jim Rees
     [not found]   ` <20110913124202.GA9498-8f4Pc2RrbJmHXe+LvDLADg@public.gmane.org>
2011-09-13 16:43     ` tao.peng
2011-09-14  6:28       ` Benny Halevy
2011-09-14  7:53         ` tao.peng
2011-09-14 15:56           ` tao.peng
     [not found]             ` <F19688880B763E40B28B2B462677FBF805C3F37B8F-AYrsSIZi/B2B3McK65YKY9BPR1lH4CV8@public.gmane.org>
2011-09-14 16:47               ` Benny Halevy
     [not found]       ` <F19688880B763E40B28B2B462677FBF805C3F37B8D-AYrsSIZi/B2B3McK65YKY9BPR1lH4CV8@public.gmane.org>
2011-09-14  6:31         ` Benny Halevy [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=4E704A3B.7080504@tonian.com \
    --to=bhalevy@tonian.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=rees@umich.edu \
    --cc=tao.peng@emc.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