2003-07-24 20:32:10

by Marcelo Tosatti

[permalink] [raw]
Subject: Linux 2.4.22-pre8


Hello,

Here goes -pre8. It contains network driver updates, IEEE1394 update, a
POSIX compliance fix introduced by the execve() security fixes during
early -pre, amongst others.

Detailed changelog below

Summary of changes from v2.4.22-pre7 to v2.4.22-pre8
============================================

<gorgo:thunderchild.debian.net>:
o [netdrvr wan] note comx maintainer change, by request

<lethal:unusual.internal.linux-sh.org>:
o sh64: sh-sci support for SH-5 101/103

<mark.fasheh:oracle.com>:
o Fix deadlock in journal_create

<taowenhwa:intel.com>:
o [e100] read skb->len after freeing skb
o [e100] cu_start: timeout waiting for cu
o [e100] misc

Andreas Gruenbacher:
o unshare-files fix breaks file locks

Ben Collins:
o [SPARC64]: Clear all IRQs at probe time in PCI sabre driver
o Update IEEE1394 (r1010)

Bhavesh P. Davda:
o Fix aha152x hangs on pcmcia card eject

Chas Williams:
o [ATM]: Get config/build dependencies correct

Daniel Ritz:
o fix ne2k-pci memleak

Marcelo Tosatti:
o Changed EXTRAVERSION to -pre8

Neil Brown:
o knfsd: Only set ->reuse for tcp sockets, not udp

Roger Luethi:
o via-rhine 1.19: One more Rhine-I fix

Scott Feldman:
o [netdrvr ethtool] add ethtool TSO get/set
o [e1000] request_irq() failure resulted in freeing twice
o [e1000] fix VLAN support on PPC64
o [e1000] missing Tx cleanup opportunities during intr handling
o [e1000] alloc_etherdev failure didn't cleanup regions
o [e1000] ethtool diag cleanup
o [e1000] h/w workaround for mis-fused parts
o [e1000] s/int/unsigned int/ for descriptor ring indexes
o [e1000] misc cleanup


2003-07-25 00:50:47

by Geert Uytterhoeven

[permalink] [raw]
Subject: Re: Linux 2.4.22-pre8

On Thu, 24 Jul 2003, Marcelo Tosatti wrote:
> Andreas Gruenbacher:
> o unshare-files fix breaks file locks

Which adds one more warning (the third one below) to my build log:

| ide.c:175: warning: `ide_scan_direction' defined but not used
| ide-lib.c:174: warning: comparison of distinct pointer types lacks a cast
| binfmt_elf.c:446: warning: `files' might be used uninitialized in this function

Seems to be harmless, though.

Gr{oetje,eeting}s,

Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- [email protected]

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
-- Linus Torvalds


2003-07-25 02:58:53

by Nuno Silva

[permalink] [raw]
Subject: Re: Linux 2.4.22-pre8

Hi Marcelo!

Marcelo Tosatti wrote:
> Hello,
>
> Here goes -pre8. It contains network driver updates, IEEE1394 update, a
> POSIX compliance fix introduced by the execve() security fixes during
> early -pre, amongst others.
>

[..snip..]

Can you, please(!!), tell me if this release fixes all the known
security problems that compromise root? :)

There's a lot of information available and some people says that
everything is "good" in recent vanilla-preX. Others says it isn't.

Anyone brave enough to answer? :-)

Regards,
Nuno Silva


2003-07-25 06:57:01

by Andreas Gruenbacher

[permalink] [raw]
Subject: Re: Linux 2.4.22-pre8

Hello Geert and Marcelo,

it turns oout that the warning is bogus, and trivially fixed. Marcelo, you may
want to apply the attached patch.

Cheers,
Andreas.

On Friday 25 July 2003 03:05, Geert Uytterhoeven wrote:
> On Thu, 24 Jul 2003, Marcelo Tosatti wrote:
> > Andreas Gruenbacher:
> > o unshare-files fix breaks file locks
>
> Which adds one more warning (the third one below) to my build log:
> | ide.c:175: warning: `ide_scan_direction' defined but not used
> | ide-lib.c:174: warning: comparison of distinct pointer types lacks a cast
> | binfmt_elf.c:446: warning: `files' might be used uninitialized in this
> | function
>
> Seems to be harmless, though.


Attachments:
(No filename) (667.00 B)
binfmt_elf-warning.diff (399.00 B)
Download all attachments

2003-07-25 11:21:06

by Alessandro Suardi

[permalink] [raw]
Subject: Re: radeon still broken (was: Linux 2.4.22-pre8)

Marcelo Tosatti wrote:
> Hello,
>
> Here goes -pre8. It contains network driver updates, IEEE1394 update, a
> POSIX compliance fix introduced by the execve() security fixes during
> early -pre, amongst others.
>
> Detailed changelog below

radeon is still broken. Looks obvious since it was broken for me
since -pre6, and -pre8 didn't change anything apparently... but
I decided to give -pre8 a spin anyway.

To my surprise, the framebuffer didn't go wild as it happened in
earlier occasions - as in here:

http://www.ussg.iu.edu/hypermail/linux/kernel/0307.2/0732.html

However, firing startx resulted in a black screen and a hard hang
(had to keep the poweroff button for 10" to actually power off).

So I tried booting -pre8 again, and this time the framebuffer went
wild again. It looks like there is a timing issue perhaps ?

I'm available for testing and debugging this - so far I'm stuck
with -pre4 which is the latest working.


Thanks in advance for any help/insight.

--alessandro

"Prima di non essere sincera / Pensa che ti tradisci solo tu"
(Vasco Rossi, 'Prima di partire per un lungo viaggio')

2003-07-25 12:30:00

by Marcelo Tosatti

[permalink] [raw]
Subject: Re: Linux 2.4.22-pre8



On Fri, 25 Jul 2003, Nuno Silva wrote:

> Hi Marcelo!
>
> Marcelo Tosatti wrote:
> > Hello,
> >
> > Here goes -pre8. It contains network driver updates, IEEE1394 update, a
> > POSIX compliance fix introduced by the execve() security fixes during
> > early -pre, amongst others.
> >
>
> [..snip..]
>
> Can you, please(!!), tell me if this release fixes all the known
> security problems that compromise root? :)
>
> There's a lot of information available and some people says that
> everything is "good" in recent vanilla-preX. Others says it isn't.

As far as I know, all known security problems are fixed. All security
fixes from -ac are in mainline.

So if anyone knows any security problem which is not fixed yet, please
inform me.

2003-07-27 16:17:26

by Roy Sigurd Karlsbakk

[permalink] [raw]
Subject: Re: Linux 2.4.22-pre8

> As far as I know, all known security problems are fixed. All security
> fixes from -ac are in mainline.
>
> So if anyone knows any security problem which is not fixed yet, please
> inform me.

Are these fixes available as separate patches to 2.4.21? If so, where
can I find them?

roy