All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vince Busam <vbusam@google.com>
To: nfs@lists.sourceforge.net
Subject: segfault in mount with CITI patch
Date: Wed, 21 Dec 2005 17:30:18 -0800	[thread overview]
Message-ID: <43AA01AA.3060705@google.com> (raw)

I've found that mount (from util-linux 2.12 + CITI_NFS4_ALL-3 patch) will segfault with 
this (probably rare) command:

mount -o tcp,nosuid,rw,rsize=8192,wsize=8192,nfsvers=3,mountvers=2,intr,sec=krb5 
server:/volume /mntpoint

This is because nfs_call_mount() will run nfs2_mount() when mountvers=2, but since 
nfsvers=3, nfsmount() will expect certain fields to be filled out, which are not.  Causing 
a segfault here, where flavor points to an invalid address.
1061                            if (flavor[i] == data.pseudoflavor)


Is nfsvers=3,mountvers=2 even OK to do?  If not, mount should print an error instead of 
segfault.

Thanks,
Vince


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2005-12-22  1:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-22  1:30 Vince Busam [this message]
2005-12-22 23:08 ` segfault in mount with CITI patch Trond Myklebust
2005-12-22 23:43   ` Vince Busam

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=43AA01AA.3060705@google.com \
    --to=vbusam@google.com \
    --cc=nfs@lists.sourceforge.net \
    /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.