Incorrect backport to 2.6.32-stable - NFSD regression.

Bug #1365914 reported by Luis Henriques
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Invalid
Medium
Luis Henriques
Lucid
Fix Released
Medium
Luis Henriques

Bug Description

SRU Justification:

Impact:
The original bug report[1] refers to the failure in running pulseaudio
when $HOME is NFS4 mounted.

[1] https://bugzilla.novell.com/show_bug.cgi?id=893787

Fix:
Reverting Lucid 0a69d50207d9e098eeb98b516b1b08b4d05dbc6f commit
(47c85291d3dd1a51501555000b90f8e281a0458e commit upstream) will fix
this issue.

Testcase:
Although I haven't tested this myself, the original bug reporter
provides a test case:

1. Mount ~ from NFS4

2. start pulseaudio:
   ~$ pulseaudio
   E: [pulseaudio] core-util.c: Failed to create secure directory
   (/home/foo/bar/.pulse): Remote I/O error

3. Actual Results:
   pulseaudio does not work
   Expected Results:
   pulseaudio should work

--

Neil Brown reported[1] in the stable mailing list that

commit 63d059e73ff4574b79bd8aa252b5fc00b6326ddf
Author: NeilBrown <email address hidden>
Date: Wed Feb 16 13:08:35 2011 +1100

    nfsd: correctly handle return value from nfsd_map_name_to_*

    commit 47c85291d3dd1a51501555000b90f8e281a0458e upstream.

in kernel 2.6.32.30 fixes a regression introduced by commit 3c726023402a2f3b28f49b9d90ebf9e71151157d. However, this commit hasn't been backported to the 2.6.32 kernel.

So, rather an fixing a regression, it introduces one and this patch should be reverted.

For more details, see https://bugzilla.novell.com/show_bug.cgi?id=893787

[1] http://www.spinics.net/lists/linux-nfs/msg46403.html

CVE References

Luis Henriques (henrix)
Changed in linux (Ubuntu):
importance: Undecided → Medium
Changed in linux (Ubuntu Lucid):
status: New → Triaged
assignee: nobody → Luis Henriques (henrix)
importance: Undecided → Medium
Luis Henriques (henrix)
description: updated
Tim Gardner (timg-tpi)
Changed in linux (Ubuntu Lucid):
status: Triaged → Fix Committed
Changed in linux (Ubuntu):
status: Triaged → Invalid
Revision history for this message
Brad Figg (brad-figg) wrote :

This bug is awaiting verification that the kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification-needed-lucid' to 'verification-done-lucid'.

If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.

See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Thank you!

tags: added: verification-needed-lucid
Revision history for this message
Luis Henriques (henrix) wrote :

This fix is available in upstream 2.6.32, so it can be considered as a regular stable update -- we just SRU'ed it without waiting for the upstream release. As such, I'm tagging it as verified.

tags: added: verification-done-lucid
removed: verification-needed-lucid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package linux - 2.6.32-67.134

---------------
linux (2.6.32-67.134) lucid; urgency=low

  [ Kamal Mostafa ]

  * Release Tracking Bug
    - re-used previous tracking bug

  [ Upstream Kernel Changes ]

  * udf: Avoid infinite loop when processing indirect ICBs
    - LP: #1370042
    - CVE-2014-6410

linux (2.6.32-67.133) lucid; urgency=low

  [ Joseph Salisbury ]

  * Release Tracking Bug
    - LP: #1372657

  [ Upstream Kernel Changes ]

  * Revert "nfsd: correctly handle return value from nfsd_map_name_to_*"
    - LP: #1365914
  * HID: fix a couple of off-by-ones
    - LP: #1370035
    - CVE-2014-3184
  * USB: whiteheat: Added bounds checking for bulk command response
    - LP: #1370036
    - CVE-2014-3185
 -- Kamal Mostafa <email address hidden> Wed, 24 Sep 2014 11:04:09 -0700

Changed in linux (Ubuntu Lucid):
status: Fix Committed → Fix Released
status: Fix Committed → 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.