> -----Original Message----- > From: linux-nfs-owner@xxxxxxxxxxxxxxx [mailto:linux-nfs-owner@xxxxxxxxxxxxxxx] > On Behalf Of Benny Halevy > Sent: Wednesday, September 14, 2011 2:29 PM > To: Peng, Tao > Cc: rees@xxxxxxxxx; linux-nfs@xxxxxxxxxxxxxxx > Subject: Re: NULL pointer dereference during mount > > I couldn't reproduce this with selinux neither disabled nor enforcing. > What's your selinux configuration? I didn't changed selinux config so it is the default on Fedora15 /etc/selinux/config: SELINUX=enforcing SELINUXTYPE=targeted /etc/selinux/semanage.conf: module-store = direct expand-check=0 usepasswd=False Cheers, Tao > > Benny > > On 2011-09-13 18:43, tao.peng@xxxxxxx wrote: > > > > ________________________________________ > > From: Jim Rees [rees@xxxxxxxxx] > > Sent: Tuesday, September 13, 2011 8:42 PM > > To: Peng, Tao > > Cc: bhalevy@xxxxxxxxxx; linux-nfs@xxxxxxxxxxxxxxx > > Subject: Re: NULL pointer dereference during mount > > > > tao.peng@xxxxxxx 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@xxxxxxxxxxxxxxx > > More majordomo info at http://vger.kernel.org/majordomo-info.html > -- > To unsubscribe from this list: send the line "unsubscribe linux-nfs" in > the body of a message to majordomo@xxxxxxxxxxxxxxx > More majordomo info at http://vger.kernel.org/majordomo-info.html -- To unsubscribe from this list: send the line "unsubscribe linux-nfs" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
