readdir(3) fails for cifs mount in 32-bit process on amd64

Bug #676171 reported by Mark Sheppard
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Undecided
Unassigned

Bug Description

After upgrading a server from januty/amd64 to karmic/amd64 our custom written backup program started failing. A further upgrade to lucid/amd64 didn't help. And testing it on a desktop with maverick/amd64 (the one I just ran "ubuntu-bug" on) shows it doesn't work on that either. I've reduced the problem down to being readdir(3) failing in 32-bit processes on cifs mounts.

Hopefully the code in the attached list.c file demonstrates the problem. I compiled it with "gcc -m32 -o list32 list.c && gcc -m64 -o list64 list.c" then ran list32 and list64, each with an argument of a path to a directory on a cifs mount. The list32 executable failed with "Cannot allocate memory", but list64 works fine. The remote share I'm trying to access is on a machine running Windows Server 2003.

Cheers,
Mark.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: linux-image-2.6.35-22-generic 2.6.35-22.35
Regression: Yes
Reproducible: Yes
ProcVersionSignature: Ubuntu 2.6.35-22.35-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: nvidia
AlsaVersion: Advanced Linux Sound Architecture Driver Version 1.0.23.
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: mark 1317 F.... pulseaudio
CRDA: Error: [Errno 2] No such file or directory
Card0.Amixer.info:
 Card hw:0 'NVidia'/'HDA NVidia at 0xdfffc000 irq 22'
   Mixer name : 'SigmaTel STAC9227'
   Components : 'HDA:83847618,102801e0,00100201'
   Controls : 35
   Simple ctrls : 23
Date: Tue Nov 16 17:38:15 2010
HibernationDevice: RESUME=UUID=d0a315bf-c24d-4552-a1fb-3716ce2e8782
IwConfig: Error: [Errno 2] No such file or directory
Lsusb:
 Bus 002 Device 002: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
 Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Dell DXG061
ProcCmdLine: BOOT_IMAGE=/boot/vmlinuz-2.6.35-22-generic root=UUID=4e4060e3-11f1-4a8f-9daa-a44118149e7f ro quiet splash
ProcEnviron:
 PATH=(custom, user)
 LANG=en_GB.UTF-8
 SHELL=/usr/bin/tcsh
RelatedPackageVersions: linux-firmware 1.38
RfKill: Error: [Errno 2] No such file or directory
SourcePackage: linux
UdevDb: Error: [Errno 2] No such file or directory
WpaSupplicantLog:

dmi.bios.date: 07/31/2006
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.1.3
dmi.board.name: 0YF432
dmi.board.vendor: Dell Inc.
dmi.board.version: A02
dmi.chassis.type: 7
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.1.3:bd07/31/2006:svnDellInc.:pnDellDXG061:pvr:rvnDellInc.:rn0YF432:rvrA02:cvnDellInc.:ct7:cvr:
dmi.product.name: Dell DXG061
dmi.sys.vendor: Dell Inc.

Revision history for this message
Mark Sheppard (mark-sheppard) wrote :
Brad Figg (brad-figg)
Changed in linux (Ubuntu):
status: New → Confirmed
Revision history for this message
penalvch (penalvch) wrote :

Mark Sheppard, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.11-rc5

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

If you are unable to test the mainline kernel, please comment as to why specifically you were unable to test it and add the following tags:
kernel-unable-to-test-upstream
kernel-unable-to-test-upstream-VERSION-NUMBER

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

tags: added: bios-outdated-1.4.1 karmic lucid
Changed in linux (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for linux (Ubuntu) because there has been no activity for 60 days.]

Changed in linux (Ubuntu):
status: Incomplete → Expired
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.