Re: BUG: loop device not work in 2.6.1-mm2 an 2.6.1-mm3

Re: BUG: loop device not work in 2.6.1-mm2 an 2.6.1-mm3

[Andy Lutomirski]

Murilo Pontes wrote:

 > 21:44:56 [root@murilo:~]#mount -V
 > mount: mount-2.12
 >
 > umount: /tmp/ramdisk_mountdir: não montado
 > ioctl: LOOP_CLR_FD: No such device or address
 > mount: será usado o dispositivo de laço /dev/loop/0
 > ioctl: LOOP_SET_FD: Argumento inválido
 >
 >
 > -
 > To unsubscribe from this list: send the line "unsubscribe linux-kernel"=
 >  in
 > the body of a message to majordomo@vger.kernel.org
 > More majordomo info at  http://vger.kernel.org/majordomo-info.html
 > Please read the FAQ at  http://www.tux.org/lkml/

Are you running reiserfs?  If so, this patch (from Ben Slusky) fixed it:

--- drivers/block/loop.c.old	2004-01-11 13:05:05.000000000 -0500
+++ drivers/block/loop.c	2004-01-14 07:49:24.795161024 -0500
@@ -853,9 +853,7 @@
  		blk_queue_merge_bvec(lo->lo_queue, q->merge_bvec_fn);
  	}

-	error = set_blocksize(bdev, lo_blocksize);
-	if (error)
-		goto out_putf;
+	set_blocksize(bdev, lo_blocksize);

  	kernel_thread(loop_thread, lo, CLONE_KERNEL);
  	down(&lo->lo_sem);

Re: BUG: loop device not work in 2.6.1-mm2 an 2.6.1-mm3

[Murilo Pontes]

Loop work with 2.6.1, but not work with 2.6.1-mm{1,2,3}
I try apply your patch in 2.6.1-mm3

11:41:50 [root@murilo:/MRX/drivers/linux-2.6.1]#patch -p0 -i /root/download/loop-mm3.diff
patching file drivers/block/loop.c
patch: **** malformed patch at line 4:                 blk_queue_merge_bvec(lo->lo_queue, q->merge_bvec_fn);


Em Qui 15 Jan 2004 06:58, Andy Lutomirski escreveu:
> Murilo Pontes wrote:
>  > 21:44:56 [root@murilo:~]#mount -V
>  > mount: mount-2.12
>  >
>  > umount: /tmp/ramdisk_mountdir: não montado
>  > ioctl: LOOP_CLR_FD: No such device or address
>  > mount: será usado o dispositivo de laço /dev/loop/0
>  > ioctl: LOOP_SET_FD: Argumento inválido
>  >
>  >
>  > -
>  > To unsubscribe from this list: send the line "unsubscribe linux-kernel"=
>  >  in
>  > the body of a message to majordomo@vger.kernel.org
>  > More majordomo info at  http://vger.kernel.org/majordomo-info.html
>  > Please read the FAQ at  http://www.tux.org/lkml/
>
> Are you running reiserfs?  If so, this patch (from Ben Slusky) fixed it:
>
> --- drivers/block/loop.c.old	2004-01-11 13:05:05.000000000 -0500
> +++ drivers/block/loop.c	2004-01-14 07:49:24.795161024 -0500
> @@ -853,9 +853,7 @@
>   		blk_queue_merge_bvec(lo->lo_queue, q->merge_bvec_fn);
>   	}
>
> -	error = set_blocksize(bdev, lo_blocksize);
> -	if (error)
> -		goto out_putf;
> +	set_blocksize(bdev, lo_blocksize);
>
>   	kernel_thread(loop_thread, lo, CLONE_KERNEL);
>   	down(&lo->lo_sem);
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/

BUG: loop device not work in 2.6.1-mm2 an 2.6.1-mm3

[Murilo Pontes]

21:44:56 [root@murilo:~]#mount -V
mount: mount-2.12

umount: /tmp/ramdisk_mountdir: não montado
ioctl: LOOP_CLR_FD: No such device or address
mount: será usado o dispositivo de laço /dev/loop/0
ioctl: LOOP_SET_FD: Argumento inválido