nfs-common: gssd -R crashes with a segmentation fault

Bug #1179992 reported by Christopher Odenbach
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
nfs-utils (Ubuntu)
Fix Released
Undecided
Unassigned

Bug Description

Hi,

when starting gssd with the -R option to specify a non-standard REALM it segfaults because of a missing colon in the getopt() call.

See http://git.linux-nfs.org/?p=steved/nfs-utils.git;a=commitdiff;h=0ce973a59ab3393481ba7c434a7353b5007cba71 for the fix.

Debian bug: #707720

The problem has been fixed in nfs-utils/1:1.2.8-1. Will this fix come back to at least quantal?

Thanks,

Christopher

Revision history for this message
Launchpad Janitor (janitor) wrote :
Download full text (3.6 KiB)

This bug was fixed in the package nfs-utils - 1:1.2.8-2ubuntu1

---------------
nfs-utils (1:1.2.8-2ubuntu1) saucy; urgency=low

  [ Stéphane Graber ]
  * Merge from Debian unstable.
    - includes upstream fix for gssd -R. LP: #1179992.
    - includes upstream fix for an exportfs crash when using long paths.
      LP: #1062022.
  * Remaining changes:
    - debian/nfs-common.{statd,statd-mounting,gssd,idmapd}.upstart,
      debian/control, debian/nfs-common.{preinst,postinst,prerm,postrm},
      debian/rules: drop nfs-common init script in favor of upstart jobs,
      and build-depend on debhelper (>= 7.3.15ubuntu3) for correct upstart
      init handling.
    - Depend on rpcbind (>= 0.2.0-6ubuntu1) for upstart support.
    - debian/nfs-kernel-server.postinst: don't call "invoke-rc.d nfs-common"
      in the postinst, this is redundant anyway and the nfs-common init script
      is gone now.
    - nfs-kernel-server.init: Unmount nfsd fs when init script stops
    - Allow issuing options to rpc.nfsd
    - debian/nfs-common.defaults: always start idmapd automatically; drop
      the configuration option.
    - Move /var/lib/nfs/rpc_pipefs to /run/rpc_pipefs. This does not belong
      in /var/lib.
    - Add "-e" (ticket expiry is error) option to rpc.gssd to prevent hangs due
      to EKEYEXPIRED error from kernel on ticket expiry. LP: #794112
    - Adjust upstart jobs to treat TYPE=nfs and TYPE=nfs4 mounts identically,
      since TYPE=nfs4 is considered deprecated.
    - Fix various boot-time race conditions between mountall and nfs-utils by
      moving handling of the 'mounting' events to separate gssd-mounting and
      idmapd-mounting jobs. Requires mountall 2.41 or better to avoid deadlock
      on boot. LP: #643289, LP: #611397.
    - Fix the stop conditions: never stop on 'runlevel [06]' since that gives
      the system no time to cleanly unmount nfs mounts; instead, stop only on
      the unmounted-remote-filesystems event. LP: #569094.
    - Newer versions of gssd don't talk to portmap, so don't make the upstart
      job depend on it.
    - Add an instance to statd-mounting, and change it to just wait for statd
      instead of trying to trigger it potentially out of order. This also
      means we don't need to try to force portmap to start from statd.

  [ Steve Langasek ]
  * Build --with-gssglue; linking directly against libgssapi-krb5 results in
    rpc.gssd trying to incorrectly pass opaque pointers between two different
    gss implementations (via libtirpc).

nfs-utils (1:1.2.8-2) unstable; urgency=medium

  * Fix reportbug scripts to use rpcinfo in /usr/sbin.
  * Add id_resolver.conf to fix nfsidmap invocation
    (Closes: #708156, #638157, #707960).
  * Remove autogenerated roff as nfsdcltrack.man is meant to be used
    as the actual source according to author (Closes: #707908).

nfs-utils (1:1.2.8-1) unstable; urgency=low

  * New upstream version (Closes: #707258).
    - Only amend extra-options on a successful vers=4 mount
      (Closes: #690181).
    - Use default domain (Closes: #657188).
    - Fix is-subdirectory to understand '/' (Closes: #685306).
    - Drop 18-osd_login-sbindir: incorporated upstream.
    ...

Read more...

Changed in nfs-utils (Ubuntu):
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.