Bug 81544 - Mounting smbfs with 32bit UID causes UID wraparound
Mounting smbfs with 32bit UID causes UID wraparound
Product: Red Hat Linux
Classification: Retired
Component: samba (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Jay Fenlason
David Lawrence
Depends On: 73066
  Show dependency treegraph
Reported: 2003-01-10 04:00 EST by Panu Matilainen
Modified: 2014-08-31 19:24 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-08-02 06:23:42 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Panu Matilainen 2003-01-10 04:00:27 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 Galeon/1.2.7 (X11; Linux i686; U;) Gecko/20021216

Description of problem:

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.smbmount //some/share /mnt/ -o uid=100000
2. ls -ld /mnt

Actual Results:  Actual Results:  The UID wraps around at 65535(and so does GID)
so the mount point gets owned by wrong UID.

Expected Results:  UID shouldn't wrap around of course..

Additional info:

The fix requires a patch to the kernel and also smbmnt:
Oh and this is present in all RH versions up to date, not just phoebe.
Comment 1 Jay Fenlason 2003-01-10 18:17:32 EST
I'm reassigning this to the kernel maintainer.  Once the kernel uses a proper 
__kernel_uid_t, we'll see if samba 2.2.7a needs patching.
Comment 2 Panu Matilainen 2003-01-12 05:48:00 EST
Oh by the point here was that you can't really change the __kernel_uid_t in 
middle of stable kernel series - see 
http://www.uwsg.iu.edu/hypermail/linux/kernel/0209.0/0678.html. With this patch 
in samba you don't need to break kernel binary compatibility.
Comment 3 Panu Matilainen 2006-08-02 06:23:42 EDT
This ancient bug got eventually fixed in RHEL, closing...

Note You need to log in before you can comment on or make changes to this bug.