i2o_block struct gendisk misinitialization (2.4.3)

to fix it. Álvaro Lopes --- linux-2.4.3/drivers/i2o/i2o_block.c Sat Apr 7 16:42:21 2001 +++ linux/drivers/i2o/i2o_block.c Fri Apr 27 19:58:41 2001 @@ -15,6 +15,8 @@ * from loop.c. Isn't free software great for reusability 8) * * Fixes/additions: + * Alvaro Lopes

i2o_block struct gendisk misinitialization (2.4.3)

to fix it. Álvaro Lopes --- linux-2.4.3/drivers/i2o/i2o_block.c Sat Apr 7 16:42:21 2001 +++ linux/drivers/i2o/i2o_block.c Fri Apr 27 19:58:41 2001 @@ -15,6 +15,8 @@ * from loop.c. Isn't free software great for reusability 8) * * Fixes/additions: + * Alvaro Lopes

Kernel (2.4.0) lock-up using ppp_async - SEVERE - EXPLOIT RUNS AS ANY USER.

Hi all, hi Paulus. Is somewhat odd how I got it, but here it goes. I found a bug in 2.4.0 async PPP driver. I tested the same program in 2.2.17 and it run perfectly (and without hanging). So, here goes the description: 2.4.0 Kernel hangs up when I do the following stuff: * Create a

Kernel (2.4.0) lock-up in "write" (using PTS).

Hi all This is somewhat odd, but I seemed to have found some kind of bug in 2.4.0. I tested the same program in 2.2.17 and it run perfectly. So, here goes the description: 2.4.0 Kernel hangs up when I do the following stuff: * Create a new PTY using openpty(); * Fork using

Kernel (2.4.0) lock-up in write (using PTS).

Hi all This is somewhat odd, but I seemed to have found some kind of bug in 2.4.0. I tested the same program in 2.2.17 and it run perfectly. So, here goes the description: 2.4.0 Kernel hangs up when I do the following stuff: * Create a new PTY using openpty(); * Fork using

Kernel (2.4.0) lock-up using ppp_async - SEVERE - EXPLOIT RUNS AS ANY USER.

Hi all, hi Paulus. Is somewhat odd how I got it, but here it goes. I found a bug in 2.4.0 async PPP driver. I tested the same program in 2.2.17 and it run perfectly (and without hanging). So, here goes the description: 2.4.0 Kernel hangs up when I do the following stuff: * Create a

kernel BUG at ll_rw_blk.c:711!

Just got this one: Sep 25 18:02:01 thecrypt kernel: kernel BUG at ll_rw_blk.c:711! Sep 25 18:02:01 thecrypt kernel: invalid operand: Sep 25 18:02:01 thecrypt kernel: CPU:0 Sep 25 18:02:01 thecrypt kernel: EIP:0010:[__make_request+161/1444] Sep 25 18:02:01 thecrypt kernel: EFLAGS:

kernel BUG at ll_rw_blk.c:711!

Just got this one: Sep 25 18:02:01 thecrypt kernel: kernel BUG at ll_rw_blk.c:711! Sep 25 18:02:01 thecrypt kernel: invalid operand: Sep 25 18:02:01 thecrypt kernel: CPU:0 Sep 25 18:02:01 thecrypt kernel: EIP:0010:[__make_request+161/1444] Sep 25 18:02:01 thecrypt kernel: EFLAGS:

Is now possible to mount the same filesystem at multiple mountpoints?

Hi I already tried to find anything related to this in the kernel archives, but found nothing. As I do not know if this is a "bug" or "feature", here it goes. It does the same on 2.3.99pre9. I'm running 2.4.0-test8. mount is mount-2.10o. thecrypt:/# mount /dev/hda1 on / type ext2