Uhhuh.. 2.4.12

Uhhuh.. 2.4.12

[Linus Torvalds]

2.4.11 had a fix for a symlink DoS attack, but sadly that fix broke the
creation of files through a dangling symlink rather badly (it caused the
inode to be created in the very same inode as the symlink, with unhappy
end results).

Happily nobody uses that particular horror - or _almost_ nobody does. It
looks like at least the SuSE installer (yast2) does, which causes a nasty
unkillable inode as /dev/mouse if you use yast2 on 2.4.11.

("debugfs -w rootdev" + "rm /dev/mouse" will remove it, although I suspect
there are other less drastic methods too if your fsck doesn't seem to
notice anything wrong with it. Only one report of this actually happening
so far).

So I made a 2.4.12, and renamed away the sorry excuse for a kernel that
2.4.11 was.

		Linus

-----
final:
 - Greg KH: USB update (fix UHCI timeouts, serial unplug)
 - Christoph Rohland: shmem locking fixes
 - Al Viro: more mount cleanup
 - me: fix bad interaction with link_count handling
 - David Miller: Sparc updates, net cleanup
 - Tim Waugh: parport update
 - Jeff Garzik: net driver updates

Re: Uhhuh.. 2.4.12

[Linus Torvalds]

In article <Pine.LNX.4.33.0110110058550.1198-100000@penguin.transmeta.com>,
Linus Torvalds  <torvalds@transmeta.com> wrote:
>
>So I made a 2.4.12, and renamed away the sorry excuse for a kernel that
>2.4.11 was.
>
> - Tim Waugh: parport update

.. which is broken.

Not a good week. 

On the other hand, the good news is that I'll open 2.5.x RSN, just
because Alan is so much better at maintaining things ;)

		Linus

Re: Uhhuh.. 2.4.12

[Tim Waugh]

On Thu, Oct 11, 2001 at 08:30:52AM +0000, Linus Torvalds wrote:

> In article <Pine.LNX.4.33.0110110058550.1198-100000@penguin.transmeta.com>,
> Linus Torvalds  <torvalds@transmeta.com> wrote:
> >
> >So I made a 2.4.12, and renamed away the sorry excuse for a kernel that
> >2.4.11 was.
> >
> > - Tim Waugh: parport update
> 
> .. which is broken.
> 
> Not a good week. 

Here is the fix:

--- linux/drivers/parport/ieee1284_ops.c.orig	Thu Oct 11 09:40:39 2001
+++ linux/drivers/parport/ieee1284_ops.c	Thu Oct 11 09:40:42 2001
@@ -362,7 +362,7 @@
 	} else {
 		DPRINTK (KERN_DEBUG "%s: ECP direction: failed to reverse\n",
 			 port->name);
-		port->ieee1284.phase = IEEE1284_PH_DIR_UNKNOWN;
+		port->ieee1284.phase = IEEE1284_PH_ECP_DIR_UNKNOWN;
 	}
 
 	return retval;
@@ -394,7 +394,7 @@
 		DPRINTK (KERN_DEBUG
 			 "%s: ECP direction: failed to switch forward\n",
 			 port->name);
-		port->ieee1284.phase = IEEE1284_PH_DIR_UNKNOWN;
+		port->ieee1284.phase = IEEE1284_PH_ECP_DIR_UNKNOWN;
 	}
 
 
Sorry guys. *blush*

Tim.
*/

Re: Uhhuh.. 2.4.12

[J . A . Magallon]

On 20011011 Tim Waugh wrote:
>On Thu, Oct 11, 2001 at 08:30:52AM +0000, Linus Torvalds wrote:
>
>> In article <Pine.LNX.4.33.0110110058550.1198-100000@penguin.transmeta.com>,
>> Linus Torvalds  <torvalds@transmeta.com> wrote:
>> >
>> >So I made a 2.4.12, and renamed away the sorry excuse for a kernel that
>> >2.4.11 was.
>> >
>> > - Tim Waugh: parport update
>> 
>> .. which is broken.
>> 
>> Not a good week. 
>
>Here is the fix:
>
>--- linux/drivers/parport/ieee1284_ops.c.orig	Thu Oct 11 09:40:39 2001
>+++ linux/drivers/parport/ieee1284_ops.c	Thu Oct 11 09:40:42 2001
>@@ -362,7 +362,7 @@
> 	} else {
> 		DPRINTK (KERN_DEBUG "%s: ECP direction: failed to reverse\n",
> 			 port->name);
>-		port->ieee1284.phase = IEEE1284_PH_DIR_UNKNOWN;
>+		port->ieee1284.phase = IEEE1284_PH_ECP_DIR_UNKNOWN;
> 	}
> 
> 	return retval;
>@@ -394,7 +394,7 @@
> 		DPRINTK (KERN_DEBUG
> 			 "%s: ECP direction: failed to switch forward\n",
> 			 port->name);
>-		port->ieee1284.phase = IEEE1284_PH_DIR_UNKNOWN;
>+		port->ieee1284.phase = IEEE1284_PH_ECP_DIR_UNKNOWN;
> 	}
> 

So you are on the work, why don't put out .13 ? And we have a correct tree...

-- 
J.A. Magallon                           #  Let the source be with you...        
mailto:jamagallon@able.es
Mandrake Linux release 8.2 (Cooker) for i586
Linux werewolf 2.4.10-ac11-beo #2 SMP Thu Oct 11 02:41:04 CEST 2001 i686

Re: Uhhuh.. 2.4.12

[T. A.]

Perhaps a quick update to the posted 2.4.12 kernel source tarball before
everyone downloads the bad one?

Or if its too late for that, 2.4.12a or 2.4.13?  :-)  (A new kernel version
out in only about an hour or so might beat the previous record.)

----- Original Message -----
From: "Tim Waugh" <twaugh@redhat.com>
To: "Linus Torvalds" <torvalds@transmeta.com>
Cc: <linux-kernel@vger.kernel.org>
Sent: Thursday, October 11, 2001 4:41 AM
Subject: Re: Uhhuh.. 2.4.12


> On Thu, Oct 11, 2001 at 08:30:52AM +0000, Linus Torvalds wrote:
>
> > In article
<Pine.LNX.4.33.0110110058550.1198-100000@penguin.transmeta.com>,
> > Linus Torvalds  <torvalds@transmeta.com> wrote:
> > >
> > >So I made a 2.4.12, and renamed away the sorry excuse for a kernel that
> > >2.4.11 was.
> > >
> > > - Tim Waugh: parport update
> >
> > .. which is broken.
> >
> > Not a good week.
>
> Here is the fix:
>
> --- linux/drivers/parport/ieee1284_ops.c.orig Thu Oct 11 09:40:39 2001
> +++ linux/drivers/parport/ieee1284_ops.c Thu Oct 11 09:40:42 2001
> @@ -362,7 +362,7 @@
>   } else {
>   DPRINTK (KERN_DEBUG "%s: ECP direction: failed to reverse\n",
>   port->name);
> - port->ieee1284.phase = IEEE1284_PH_DIR_UNKNOWN;
> + port->ieee1284.phase = IEEE1284_PH_ECP_DIR_UNKNOWN;
>   }
>
>   return retval;
> @@ -394,7 +394,7 @@
>   DPRINTK (KERN_DEBUG
>   "%s: ECP direction: failed to switch forward\n",
>   port->name);
> - port->ieee1284.phase = IEEE1284_PH_DIR_UNKNOWN;
> + port->ieee1284.phase = IEEE1284_PH_ECP_DIR_UNKNOWN;
>   }
>
>
> Sorry guys. *blush*
>
> Tim.
> */
> -
> 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/
>

Re: Uhhuh.. 2.4.12

[Stefan Smietanowski]

Hi.

>>So I made a 2.4.12, and renamed away the sorry excuse for a kernel that
>>2.4.11 was.
>>
>> - Tim Waugh: parport update
>
> .. which is broken.
>
> Not a good week.
>
> On the other hand, the good news is that I'll open 2.5.x RSN, just
> because Alan is so much better at maintaining things ;)

Hmm. Does that mean that 2.4.x-ac will become the standard tree or ?
// Stefan

Re: Uhhuh.. 2.4.12

[Tim Waugh]

[-- Attachment #1: Type: text/plain, Size: 294 bytes --]

On Thu, Oct 11, 2001 at 10:42:09AM +0200, Stefan Smietanowski wrote:

> Hmm. Does that mean that 2.4.x-ac will become the standard tree or ?

No, it means that I have to write out 'I will not edit patches by hand
without testing them' a thousand times, _without_ using cut and
paste..

Tim.
*/

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

Re: Uhhuh.. 2.4.12

[Stefan Smietanowski]

Hi.

>> Hmm. Does that mean that 2.4.x-ac will become the standard tree or ?
>
> No, it means that I have to write out 'I will not edit patches by hand
> without testing them' a thousand times, _without_ using cut and
> paste..

Wow. What a job. Why don't you code instead ? :)

// Stefan

Re: Uhhuh.. 2.4.12

[Marco Colombo]

On Thu, 11 Oct 2001, Linus Torvalds wrote:

> In article <Pine.LNX.4.33.0110110058550.1198-100000@penguin.transmeta.com>,
> Linus Torvalds  <torvalds@transmeta.com> wrote:
> >
> >So I made a 2.4.12, and renamed away the sorry excuse for a kernel that
> >2.4.11 was.
> >
> > - Tim Waugh: parport update
>
> .. which is broken.
>
> Not a good week.
>
> On the other hand, the good news is that I'll open 2.5.x RSN, just
> because Alan is so much better at maintaining things ;)

And will Alan release 2.4.13 asap with Rik's VM? - (sorry, couldn't resist)

.TM.
-- 
      ____/  ____/   /
     /      /       /			Marco Colombo
    ___/  ___  /   /		      Technical Manager
   /          /   /			 ESI s.r.l.
 _____/ _____/  _/		       Colombo@ESI.it

Re: Uhhuh.. 2.4.12

[Alan Cox]

> > On the other hand, the good news is that I'll open 2.5.x RSN, just
> > because Alan is so much better at maintaining things ;)
> 
> And will Alan release 2.4.13 asap with Rik's VM? - (sorry, couldn't resist)

I think 2.4.13 will be a Linus release