search for: __kernel_uid_t

...r desired) to include <linux/fs.h>. Also, the Linux kernel uses 16 bit numbers for uid_t, gid_t, and mode_t, whilst glibc2 uses 32 bits. This causes problems obviously when trying to mount the share. Basically the permissions and ownership as all screwed up. The fix is to replace uid_t with __kernel_uid_t and the others the same way. With these small changes all the mount utilities compile correctly, with the exception of smbumount, which required $(LIBS) be added to the object dependancies in the Makefile. So now I have a copy of Samba and the smb mount utils that works properly with glibc2. I cle...

On S?nnavend 05 November 2005 00:51, Christoph Hellwig wrote: > On Sat, Nov 05, 2005 at 12:10:46AM +0100, Arnd Bergmann wrote: > > > > BTW, I now have a set of 25 patches that moves all handlers from > > fs/compat_ioctl.c over to the respective drivers and subsystems, > > but I'm not sure how to best test that. > > I intend to at least give it a test run on my

On S?nnavend 05 November 2005 00:51, Christoph Hellwig wrote: > On Sat, Nov 05, 2005 at 12:10:46AM +0100, Arnd Bergmann wrote: > > > > BTW, I now have a set of 25 patches that moves all handlers from > > fs/compat_ioctl.c over to the respective drivers and subsystems, > > but I'm not sure how to best test that. > > I intend to at least give it a test run on my

...which seems to have been pushed off to the side as not important, even though it's a serious flaw. Just where, I don't know (i.e., kernel smbfs or samba/smbmount). I know there must be *someone* who has a clue. Various proposed causes include password caching, the use of uid_t instead of __kernel_uid_t in the smbumount code (what that has to do with keeping a share mounted, I'm not sure), and blistering silence from those that write the code and know it best. Pasted below is the body of a previous unanswered post. If any of the experts could help, I and others would really appreciate it....

How do i unsubscribe??