Hi, On Wed Oct 01, 2008 at 15:12:38 +0200, Peter Palfrader wrote: > On Wed, 01 Oct 2008, Philipp Kern wrote: > > > am Wed, Oct 01, 2008 at 12:41:00PM +0200 hast du folgendes geschrieben: > > > irqbalance in etch segfaults when /proc/interrupts contains an interrupt > > > with a number higher than or equal to MAX_INTERRUPTS (256) due to a > > > missing array boundary check. At least it segfaults reliably on all my > > > hosts (say powell.d.o) that have a line starting in the 500s range. > > > > > > The version from lenny/backports does not have this issue. Should we > > > try to fix this in the etch package also? > > > > looks RC to me. If it's just a missing boundary check, please add it > > and post the debdiff. (: > > source interdiff looks like this: > > diff -u irqbalance-0.12/debian/changelog irqbalance-0.12/debian/changelog > --- irqbalance-0.12/debian/changelog > +++ irqbalance-0.12/debian/changelog > @@ -1,3 +1,15 @@ > +irqbalance (0.12-7etch1) stable; urgency=low > + > + * Non maintainer upload. > + * irqbalance would segfault on startup when /proc/interrupts contains > + an interrupt with a number of 256 or larger, since internally it > + stored data in a fixed-length array. Newer versions (say 0.55) have > + replaced the data structure with a list so this is fixed there. For > + now we just skip interrupts with such high numbers, since it's the > + least invasive approach during the stable cycle. > + > + -- Peter Palfrader <[EMAIL PROTECTED]> Wed, 1 Oct 2008 15:06:07 +0200 > +
Please mention the Bug# in the changelog. if there isn't any, please go ahead and open an RC bug. Greetings Martin -- Martin Zobel-Helas <[EMAIL PROTECTED]> | Debian System Administrator Debian & GNU/Linux Developer | Debian Listmaster Public key http://zobel.ftbfs.de/5d64f870.asc - KeyID: 5D64 F870 GPG Fingerprint: 5DB3 1301 375A A50F 07E7 302F 493E FB8E 5D64 F870 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
