PROBLEM: Kernel 2.5.19 oops when copying files from SMBFS fs to VFAT fs

PROBLEM: Kernel 2.5.19 oops when copying files from SMBFS fs to VFAT fs

Post by Urban Widmar » Sat, 01 Jun 2002 07:10:08




> Starting with linux kernel 2.5.19, when I try to cp/mv files from one of my
> Windows 2000, Service Pack 2 machines (mounted as SMBFS on
> /net/gateway-data) to a local VFAT partition (mounted as VFAT on /mnt/data),
> causes the kernel to oops.

> Please, see attached "dmesg" file for information on the kernel oops
> message. Also, the "ksymoops" file contains the information dumped by
> ksymooops on the faulting kernel.

It appears to crash in smbfs smb_readpage because struct file is NULL.
Don't know if that is a caller error or a smbfs bug.

Quote:> Steps to reproduce the problem:
> ===============================
> mount -t vfat /dev/hda3 /mnt/data -o gid=100,umask=007
> mount -t smbfs //gateway/data /net/ -o username=Administrator
> /mnt/data/Jpgs/
> cp /net/* .

Approximately how much data is this?
Does this also happen with a kernel in the stable series? (2.4.19-pre9 ?)

/Urban

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in

More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

 
 
 

1. 2.5.19:fs/locks.c

The following patch addresses problem associated with
process locks when called from the cloned process created
with CLONE_THREAD flag. The fcntl locks are per-process and
creates a dead-lock for cloned (w/CLONE_THREAD) processes.
It should use tgid instead pid (same way as getpid()).

Thanks,

=======================================

[ fcntl_locks-2.5.19.diff 1K ]
diff -Naur linux-2.5.19/fs/locks.c linux-2.5.19-patch/fs/locks.c
--- linux-2.5.19/fs/locks.c     Wed May 29 13:42:53 2002

        fl->fl_owner = NULL;
        fl->fl_file = filp;
-       fl->fl_pid = current->pid;
+       fl->fl_pid = current->tgid;
        fl->fl_flags = FL_FLOCK;
        fl->fl_type = type;

                fl->fl_end = OFFSET_MAX;

        fl->fl_owner = current->files;
-       fl->fl_pid = current->pid;
+       fl->fl_pid = current->tgid;
        fl->fl_file = filp;
        fl->fl_flags = FL_POSIX;

                fl->fl_end = OFFSET_MAX;

        fl->fl_owner = current->files;
-       fl->fl_pid = current->pid;
+       fl->fl_pid = current->tgid;
        fl->fl_file = filp;
        fl->fl_flags = FL_POSIX;

                return -ENOMEM;

        fl->fl_owner = current->files;
-       fl->fl_pid = current->pid;
+       fl->fl_pid = current->tgid;

        fl->fl_file = filp;

                return -ENOMEM;

        new_fl->fl_owner = current->files;
-       new_fl->fl_pid = current->pid;
+       new_fl->fl_pid = current->tgid;
        new_fl->fl_file = filp;
        new_fl->fl_flags = FL_POSIX | FL_ACCESS;
        new_fl->fl_type = (read_write == FLOCK_VERIFY_WRITE) ? F_WRLCK : F_RDLCK;

2. hd7 not mounting after dump crash

3. oops: 2.5.19, unloading sound modules (snd-ens1371)

4. quota

5. 2.5.19 OOPS in pcmcia setup code

6. Opinions/Suggestions for Linux Pentium...

7. 2.5.19 - What's up with the kernel build?

8. which pci video card

9. 3dfx framebuffer driver borked in 2.5.19 kernel

10. Kyocera FS 1600 or FS 1600+ Printer drivers ( FS-1600 FS-1600+)

11. USB host drivers test results (2.5.19) and problem.

12. 2.5.19: vesafb problems

13. AUDIT 2.5.19: Continuing copy_to/from_user & clear_user