Processing of kernel-source-2.6.10_2.6.10-2_i386.changes
kernel-source-2.6.10_2.6.10-2_i386.changes uploaded successfully to localhost along with the files: kernel-source-2.6.10_2.6.10-2.dsc kernel-source-2.6.10_2.6.10.orig.tar.gz kernel-source-2.6.10_2.6.10-2.diff.gz kernel-patch-debian-2.6.10_2.6.10-2_all.deb kernel-source-2.6.10_2.6.10-2_all.deb kernel-tree-2.6.10_2.6.10-2_all.deb kernel-doc-2.6.10_2.6.10-2_all.deb Greetings, Your Debian queue daemon
kernel-source-2.6.10_2.6.10-2_i386.changes is NEW
(new) kernel-doc-2.6.10_2.6.10-2_all.deb optional doc Linux kernel specific documentation for version 2.6.10 This package provides the various readme's in the 2.6.10 kernel Documentation/ subdirectory: these typically contain kernel-specific installation notes for some drivers for example. See /usr/share/doc/kernel-doc-X.X.XX/Documentation/00-INDEX for a list of what is contained in each file. Please read the Changes file, as it contains information about the problems, which may result by upgrading your kernel. (new) kernel-patch-debian-2.6.10_2.6.10-2_all.deb optional devel Debian patches to Linux 2.6.10 This package includes the patches used to produce the prepackaged kernel-source-2.6.10 package. Note that these patches do NOT apply against a pristine Linux 2.6.10 kernel but only against kernel-source-2.6.10_2.6.10.orig.tar.gz from the Debian archive. (new) kernel-source-2.6.10_2.6.10-2.diff.gz optional devel (new) kernel-source-2.6.10_2.6.10-2.dsc optional devel (new) kernel-source-2.6.10_2.6.10-2_all.deb optional devel Linux kernel source for version 2.6.10 with Debian patches This package provides the source code for the Linux kernel version 2.6.10. . You may configure the kernel to your setup by typing make config and following instructions, but you could get ncursesX.X-dev and try make menuconfig for a jazzier, and easier to use interface. There are options to use QT or GNOME based configuration interfaces, but they need additional packages to be installed. Also, please read the detailed documentation in the file /usr/share/doc/kernel-source-2.6.10/README.headers.gz. . If you wish to use this package to create a custom Linux kernel, then it is suggested that you investigate the package kernel-package, which has been designed to ease the task of creating kernel image packages. (new) kernel-source-2.6.10_2.6.10.orig.tar.gz optional devel (new) kernel-tree-2.6.10_2.6.10-2_all.deb optional devel Linux kernel tree for building prepackaged Debian kernel images This meta package is used as a build-time dependency of prepackaged Debian kernel-image packages. Its dependencies are structured so that a complete kernel tree with Debian patches applied will be available after this package is installed. It also contains the upstream changelog file. . For those intending to use this package as a build-time dependency, this package provides a list of virtual packages that guarantees the availability of a particular Debian revision of the kernel tree. The kernel-image-2.6.10-i386 package is an example of this. Changes: kernel-source-2.6.10 (2.6.10-2) unstable; urgency=low . * [SECURITY] 028-do_brk_security_fixes.dpatch Fix local root vulnerability for various do_brk() calls; ensure an exclusive lock on memory while modifying it; CAN-2004-1235 (Andres Salomon) (closes: #289155). . * [SECURITY] 029-random_poolsize_overflow.dpatch drivers/char/random allows you to set the poolsize; its sanity checking on that input isn's very good. We fix that here. See http://seclists.org/lists/fulldisclosure/2005/Jan/0270.html for more details. This fixes #3 on that list (Andres Salomon). . * [SECURITY] 030-moxa_user_copy_checking.dpatch The moxa driver does some ugly things w/ signed integers. This fixes #4 on Brad Spengler's advisory (Andres Salomon). . * [SECURITY] 031-sg_scsi_ioctl_int_overflows.dpatch SG ioctl stuff doesn't actually check whether the scsi command length is positive. #5 on the above advisory (Andres Salomon). Announcing to debian-devel-changes@lists.debian.org Closing bugs: 289155 Your package contains new components which requires manual editing of the override file. It is ok otherwise, so please be patient. New packages are usually added to the override file about once a week. You may have gotten the distribution wrong. You'll get warnings above if files already exist in other distributions.
Bug#80878: New message from Mertens
Check here if your message below does not load. Lots of times you have to pretend to join a parade in which you're not really interested in order to get where you're going. -Christopher Darlington Morley (1890-1957) bantamweight Doesn't Ms. Brown hate playing at the company? Britishhood Why does the Air Force need expensive new bombers? Have the people we've been bombing over the years been complaining? George Wallace camphine I get from most parents is ?Can you teach my child to talk?? This question has haunted me for years. adenosarcoma Minds are like parachutes. They only function when they are open. -Sir James Dewar, Scientist (1877-1925) adoperation Many bartenders like driving every other day. bah Lots of times you have to pretend to join a parade in which you're not really interested in order to get where you're going. -Christopher Darlington Morley (1890-1957) atmological Toren came to me at age 32 months. He had 2 words: Ma Ma and Bye Bye. He could not focus, but ran around the room. His mother was convinced I was going to have him cured by his third birthday. I told her I was no miracle worker, but we'd do what we could during the next 4 months. Immediately we started structuring Toren's day. I went home and worked up a program called 'Toren's Nouns'. The first day I showed Toren the program, he looked at it for 10-15 seconds and then left the computer. The next day he stayed about 30 seconds. Each day he built up more time at the computer. By the second week, he would sit on my lap for 10 minutes pressing whichever word he wanted to hear. But he spoke no sounds, no words. Three weeks passed I began berating myself. 'See, Jo, you thought this noun program was so great. Look at Toren, he's not learning anything.' The fourth week Toren walked over to the computer, picked up the overlay from the IntelliKeys keyboard, pointed to 10 different words and approximated each word. That day, I cried. Avis
Processing of kernel-source-2.6.9_2.6.9-5_i386.changes
kernel-source-2.6.9_2.6.9-5_i386.changes uploaded successfully to localhost along with the files: kernel-source-2.6.9_2.6.9-5.dsc kernel-source-2.6.9_2.6.9-5.diff.gz kernel-patch-debian-2.6.9_2.6.9-5_all.deb kernel-source-2.6.9_2.6.9-5_all.deb kernel-tree-2.6.9_2.6.9-5_all.deb kernel-doc-2.6.9_2.6.9-5_all.deb Greetings, Your Debian queue daemon
Processing of kernel-source-2.6.8_2.6.8-12_i386.changes
kernel-source-2.6.8_2.6.8-12_i386.changes uploaded successfully to localhost along with the files: kernel-source-2.6.8_2.6.8-12.dsc kernel-source-2.6.8_2.6.8-12.diff.gz kernel-patch-debian-2.6.8_2.6.8-12_all.deb kernel-source-2.6.8_2.6.8-12_all.deb kernel-tree-2.6.8_2.6.8-12_all.deb kernel-doc-2.6.8_2.6.8-12_all.deb Greetings, Your Debian queue daemon
Bug#289155: marked as done (CAN-2004-1235: uselib() privilege escalation)
Your message dated Sat, 08 Jan 2005 06:48:41 -0500 with message-id [EMAIL PROTECTED] and subject line Bug#289155: fixed in kernel-source-2.6.9 2.6.9-5 has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 7 Jan 2005 14:41:07 + From [EMAIL PROTECTED] Fri Jan 07 06:41:07 2005 Return-path: [EMAIL PROTECTED] Received: from inutil.org (vserver151.vserver151.serverflex.de) [193.22.164.111] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CmvIZ-0007RW-00; Fri, 07 Jan 2005 06:41:07 -0800 Received: from wlan-client-025.informatik.uni-bremen.de ([134.102.116.26] helo=localhost.localdomain) by vserver151.vserver151.serverflex.de with asmtp (TLS-1.0:RSA_ARCFOUR_SHA:16) (Exim 4.34) id 1CmvIX-0007Sb-Lt for [EMAIL PROTECTED]; Fri, 07 Jan 2005 15:41:05 +0100 Received: from jmm by localhost.localdomain with local (Exim 4.34) id 1CmvIU-0001lw-3s; Fri, 07 Jan 2005 15:41:02 +0100 Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Moritz Muehlenhoff [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: CAN-2004-1235: uselib() privilege escalation X-Mailer: reportbug 3.5 Date: Fri, 07 Jan 2005 15:41:01 +0100 Message-Id: [EMAIL PROTECTED] X-SA-Exim-Connect-IP: 134.102.116.26 X-SA-Exim-Mail-From: [EMAIL PROTECTED] X-SA-Exim-Scanned: No (on vserver151.vserver151.serverflex.de); SAEximRunCond expanded to false Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_PACKAGE, RCVD_IN_DSBL autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Package: kernel-source-2.6.8 Version: 2.6.8 Severity: grave Tags: security Justification: user security hole Paul Starzetz from iSec Security Research has discovered a local root exploit in the Linux kernel: Locally exploitable flaws have been found in the Linux binary format loaders' uselib() functions that allow local users to gain root privileges. The full advisory text: http://isec.pl/vulnerabilities/isec-0021-uselib.txt I haven't found a patch for 2.6 yet, a patch for 2.4 is available in the 2.4 Bitkeeper branch. Cheers, Moritz -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable') Architecture: i386 (i686) Kernel: Linux 2.6.9-1-386 Locale: LANG=C, [EMAIL PROTECTED] (charmap=ISO-8859-15) Versions of packages kernel-source-2.6.8 depends on: ii binutils 2.15-5 The GNU assembler, linker and bina ii bzip2 1.0.2-2high-quality block-sorting file co ii coreutils [fileutils] 5.2.1-2The GNU core utilities --- Received: (at 289155-close) by bugs.debian.org; 8 Jan 2005 11:52:00 + From [EMAIL PROTECTED] Sat Jan 08 03:52:00 2005 Return-path: [EMAIL PROTECTED] Received: from newraff.debian.org [208.185.25.31] (mail) by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CnF8R-0007j9-00; Sat, 08 Jan 2005 03:51:59 -0800 Received: from katie by newraff.debian.org with local (Exim 3.35 1 (Debian)) id 1CnF5F-0007km-00; Sat, 08 Jan 2005 06:48:41 -0500 From: Andres Salomon [EMAIL PROTECTED] To: [EMAIL PROTECTED] X-Katie: $Revision: 1.54 $ Subject: Bug#289155: fixed in kernel-source-2.6.9 2.6.9-5 Message-Id: [EMAIL PROTECTED] Sender: Archive Administrator [EMAIL PROTECTED] Date: Sat, 08 Jan 2005 06:48:41 -0500 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-6.0 required=4.0 tests=BAYES_00,HAS_BUG_NUMBER autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: Source: kernel-source-2.6.9 Source-Version: 2.6.9-5 We believe that the bug you reported is fixed in the latest version of kernel-source-2.6.9, which is due to be installed in the Debian FTP archive: kernel-doc-2.6.9_2.6.9-5_all.deb to pool/main/k/kernel-source-2.6.9/kernel-doc-2.6.9_2.6.9-5_all.deb kernel-patch-debian-2.6.9_2.6.9-5_all.deb to pool/main/k/kernel-source-2.6.9/kernel-patch-debian-2.6.9_2.6.9-5_all.deb kernel-source-2.6.9_2.6.9-5.diff.gz to pool/main/k/kernel-source-2.6.9/kernel-source-2.6.9_2.6.9-5.diff.gz kernel-source-2.6.9_2.6.9-5.dsc to
kernel-source-2.6.8_2.6.8-12_i386.changes ACCEPTED
Accepted: kernel-doc-2.6.8_2.6.8-12_all.deb to pool/main/k/kernel-source-2.6.8/kernel-doc-2.6.8_2.6.8-12_all.deb kernel-patch-debian-2.6.8_2.6.8-12_all.deb to pool/main/k/kernel-source-2.6.8/kernel-patch-debian-2.6.8_2.6.8-12_all.deb kernel-source-2.6.8_2.6.8-12.diff.gz to pool/main/k/kernel-source-2.6.8/kernel-source-2.6.8_2.6.8-12.diff.gz kernel-source-2.6.8_2.6.8-12.dsc to pool/main/k/kernel-source-2.6.8/kernel-source-2.6.8_2.6.8-12.dsc kernel-source-2.6.8_2.6.8-12_all.deb to pool/main/k/kernel-source-2.6.8/kernel-source-2.6.8_2.6.8-12_all.deb kernel-tree-2.6.8_2.6.8-12_all.deb to pool/main/k/kernel-source-2.6.8/kernel-tree-2.6.8_2.6.8-12_all.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 289155 Thank you for your contribution to Debian.
kernel-source-2.6.9_2.6.9-5_i386.changes ACCEPTED
Accepted: kernel-doc-2.6.9_2.6.9-5_all.deb to pool/main/k/kernel-source-2.6.9/kernel-doc-2.6.9_2.6.9-5_all.deb kernel-patch-debian-2.6.9_2.6.9-5_all.deb to pool/main/k/kernel-source-2.6.9/kernel-patch-debian-2.6.9_2.6.9-5_all.deb kernel-source-2.6.9_2.6.9-5.diff.gz to pool/main/k/kernel-source-2.6.9/kernel-source-2.6.9_2.6.9-5.diff.gz kernel-source-2.6.9_2.6.9-5.dsc to pool/main/k/kernel-source-2.6.9/kernel-source-2.6.9_2.6.9-5.dsc kernel-source-2.6.9_2.6.9-5_all.deb to pool/main/k/kernel-source-2.6.9/kernel-source-2.6.9_2.6.9-5_all.deb kernel-tree-2.6.9_2.6.9-5_all.deb to pool/main/k/kernel-source-2.6.9/kernel-tree-2.6.9_2.6.9-5_all.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 289155 Thank you for your contribution to Debian.
Bug#277343: marked as done (mondo: Deadlock on swapfile even with -E /swapfile)
Your message dated Sat, 8 Jan 2005 13:47:07 +0100 with message-id [EMAIL PROTECTED] and subject line #277343: not a bug has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 19 Oct 2004 16:25:37 + From [EMAIL PROTECTED] Tue Oct 19 09:25:37 2004 Return-path: [EMAIL PROTECTED] Received: from smtpin.eastlink.ca [24.222.0.18] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CJwno-0001Id-00; Tue, 19 Oct 2004 09:25:37 -0700 Received: from webshielde250.Dymaxion.ca ([24.222.19.7]) by mx3.eastlink.ca (iPlanet Messaging Server 5.2 HotFix 1.25 (built Mar 3 2004)) with ESMTP id [EMAIL PROTECTED] for [EMAIL PROTECTED]; Tue, 19 Oct 2004 13:25:05 -0300 (ADT) Received: from nt1-exchange.dymaxion.ca(24.222.19.7) by webshielde250.Dymaxion.ca via csmap id 70e1b41a_21ec_11d9_95e7_0002b3bc8fcd_1625; Tue, 19 Oct 2004 13:32:18 -0300 (ADT) Received: from bgpc.dymaxion.ca ([24.222.19.4]) by nt1-exchange.dymaxion.ca with Microsoft SMTPSVC(6.0.3790.211); Tue, 19 Oct 2004 13:24:53 -0300 Received: from ben by bgpc.dymaxion.ca with local (Exim 3.36 #1 (Debian)) id 1CJwn5-0008Is-00; Tue, 19 Oct 2004 13:24:51 -0300 Date: Tue, 19 Oct 2004 13:24:50 -0300 From: Ben Armstrong [EMAIL PROTECTED] Subject: mondo: Deadlock on swapfile even with -E /swapfile To: Debian Bug Tracking System [EMAIL PROTECTED] Message-id: [EMAIL PROTECTED] MIME-version: 1.0 X-Mailer: reportbug 2.99.6 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT X-OriginalArrivalTime: 19 Oct 2004 16:24:53.0430 (UTC) FILETIME=[29FED560:01C4B5F8] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: mondo Version: 2.03.1-2 Severity: important I recently added a 128M swapfile to my system located in /swapfile. Now, when I run mondoarchive, even when I specify -E /swapfile, it deadlocks when it reads /swapfile (which ends up in biggielist.txt). If it matters, I was doing a differential backup. I haven't yet tried a full. The only way to break the deadlock is with the command 'swapoff -a'. Then when mondarchive has gotten past that point, I run 'swapon -a' to reenable swap. Ben -- System Information: Debian Release: 3.1 APT prefers unstable APT policy: (500, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Kernel: Linux 2.6.7-1-686 Locale: LANG=en_US, LC_CTYPE=en_US Versions of packages mondo depends on: ii afio2.5-2Archive file manipulation program ii binutils2.15-4 The GNU assembler, linker and bina ii buffer 1.19-5 Buffering/reblocking program for t ii cdrecord4:2.0+a38-1 command line CD writing tool ii dosfstools 2.10-1 Utilities to create and check MS-D ii gawk1:3.1.4-1GNU awk, a pattern scanning and pr ii libc6 2.3.2.ds1-18 GNU C Library: Shared libraries an ii libnewt0.51 0.51.6-17Not Erik's Windowing Toolkit - tex ii lzop1.01-3 fast compression program ii mindi 1.03.1-3 Creates boot/root disks based on y -- no debconf information --- Received: (at 277343-done) by bugs.debian.org; 8 Jan 2005 12:47:10 + From [EMAIL PROTECTED] Sat Jan 08 04:47:10 2005 Return-path: [EMAIL PROTECTED] Received: from verein.lst.de (mail.lst.de) [213.95.11.210] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CnFzp-SY-00; Sat, 08 Jan 2005 04:47:10 -0800 Received: from verein.lst.de (localhost [127.0.0.1]) by mail.lst.de (8.12.3/8.12.3/Debian-7.1) with ESMTP id j08Cl76t001920 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for [EMAIL PROTECTED]; Sat, 8 Jan 2005 13:47:07 +0100 Received: (from [EMAIL PROTECTED]) by verein.lst.de (8.12.3/8.12.3/Debian-6.6) id j08Cl7Gb001918 for [EMAIL PROTECTED]; Sat, 8 Jan 2005 13:47:07 +0100 Date: Sat, 8 Jan 2005 13:47:07 +0100 From: Christoph Hellwig [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: #277343: not a bug Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii
Processed: #281905 please enable CONFIG_EFI_PARTITION; it's needed for 2TiB
Processing commands for [EMAIL PROTECTED]: severity 281905 wishlist Bug#281905: please enable CONFIG_EFI_PARTITION; it's needed for 2TiB Severity set to `wishlist'. thanks Stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#281905: #281905 please enable CONFIG_EFI_PARTITION; it's needed for 2TiB
severity 281905 wishlist thanks The EFI format is unfortunately rather misdesigned and has a backup data area at the end of the devices - which won't be acciable by lots of usb devices because they have broken size reporting. This alone wouldn't be a problem if we could simply probe EFI last, but that doesn't work either as EFI partition tables also contain a fake dos partition table to trick around older windows versions. Best thing for 2TB disks is to use LVM anyway
Bug#286028: #286028 installation-reports: loading tg3 module for Broadcom NIC causes total freeze of system
please try installing with a 2.6 kernel, it has a much more uptodate tg3 driver (and various other advantages)
Bug#288197: marked as done (2.6.10: ip_conntrack ignores RST making the tracking hash blow up in your face)
Your message dated Sat, 8 Jan 2005 14:12:32 +0100 with message-id [EMAIL PROTECTED] and subject line #288197 fixed in the WIP packages has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 2 Jan 2005 12:37:03 + From [EMAIL PROTECTED] Sun Jan 02 04:37:03 2005 Return-path: [EMAIL PROTECTED] Received: from pasop.tomt.net (pelle.pasop.tomt.net) [217.8.136.222] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1Cl4yk-0003Ne-00; Sun, 02 Jan 2005 04:37:03 -0800 Received: by pelle.pasop.tomt.net (Postfix, from userid 1000) id 4AC6564098; Sun, 2 Jan 2005 13:36:57 +0100 (CET) Content-Type: text/plain; charset=us-ascii MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Andre Tomt [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: 2.6.10: ip_conntrack ignores RST making the tracking hash blow up in your face X-Mailer: reportbug 3.2 Date: Sun, 02 Jan 2005 13:36:57 +0100 Message-Id: [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: kernel Severity: important Tags: patch This is a bug introduced by netfilter ip_conntrack window tracking fixes introduced in a late 2.6.10-rc, wich should be fixed in the pending 2.6.10 upload to the debian archive (discussed on #debian-kernel). The window tracking fixed broke RST handling, making the tracking hash blow up really badly. In my setup it blew up with net.ipv4.ip_conntrack_max=65536 after a little over 24 hours in use. With a 5 day established timeout (the default) the hash would probably grow to somewhere around 30 entries - each taking rougly 300 bytes, and this is on a relatively low trafficed firewall (10-20Mbps). Normal non-buggy operation here is about 1-2000 entries. The fix attached is currently not been checked over by the guy who broke it all; but it has been known to work just fine in my setups and others. More history - and patch: http://lists.netfilter.org/pipermail/netfilter-devel/2004-December/017908.html -- System Information: Debian Release: 3.1 APT prefers testing APT policy: (1000, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.10-s1-up Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) --- Received: (at 288197-done) by bugs.debian.org; 8 Jan 2005 13:12:34 + From [EMAIL PROTECTED] Sat Jan 08 05:12:34 2005 Return-path: [EMAIL PROTECTED] Received: from verein.lst.de (mail.lst.de) [213.95.11.210] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CnGOQ-0005UV-00; Sat, 08 Jan 2005 05:12:34 -0800 Received: from verein.lst.de (localhost [127.0.0.1]) by mail.lst.de (8.12.3/8.12.3/Debian-7.1) with ESMTP id j08DCW6t002313 (version=TLSv1/SSLv3 cipher=EDH-RSA-DES-CBC3-SHA bits=168 verify=NO) for [EMAIL PROTECTED]; Sat, 8 Jan 2005 14:12:32 +0100 Received: (from [EMAIL PROTECTED]) by verein.lst.de (8.12.3/8.12.3/Debian-6.6) id j08DCWf5002311 for [EMAIL PROTECTED]; Sat, 8 Jan 2005 14:12:32 +0100 Date: Sat, 8 Jan 2005 14:12:32 +0100 From: Christoph Hellwig [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: #288197 fixed in the WIP packages Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.3.28i X-Spam-Score: -4.901 () BAYES_00 X-Scanned-By: MIMEDefang 2.39 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no version=2.60-bugs.debian.org_2005_01_02 X-Spam-Level: this bug is 2.6.10-only and the WIP packages for 2.6.10 have it fixed already
Processed: tagging 289247
Processing commands for [EMAIL PROTECTED]: # Automatically generated email from bts, devscripts version 2.8.6 tags 289247 + pending Bug#289247: SCSI Device List update (FIX problems with some pendrivers) Tags were: patch Tags added: pending End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Processed: your mail
Processing commands for [EMAIL PROTECTED]: severity 216237 wishlist Bug#216237: ataraid/pdcraid drivers needed for 2.6 Bug#227692: kernel-image-2.6.0-1-k7: HPTRAID and PDCRAID modules not present. Severity set to `wishlist'. End of message, stopping processing here. Please contact me if you need assistance. Debian bug tracking system administrator (administrator, Debian Bugs database)
Bug#193625: marked as done (ISDN divert support broken)
Your message dated Sat, 8 Jan 2005 14:19:44 +0100 with message-id [EMAIL PROTECTED] and subject line divert support compiles cleanly in current kernels has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 17 May 2003 09:40:19 + From [EMAIL PROTECTED] Sat May 17 04:40:16 2003 Return-path: [EMAIL PROTECTED] Received: from marco.bezeqint.net [192.115.106.37] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 19GyAo-gE-00; Sat, 17 May 2003 04:40:14 -0500 Received: from localhost (bzq-179-7-156.cust.bezeqint.net [212.179.7.156]) by marco.bezeqint.net (Bezeq International SMTP out Mail Server) with ESMTP id 90D158673 for [EMAIL PROTECTED]; Sat, 17 May 2003 15:35:29 +0300 (IDT) Received: from shaul by localhost with local (Exim 3.36 #1 (Debian)) id 19GyAh-0001zY-00 for [EMAIL PROTECTED]; Sat, 17 May 2003 12:40:07 +0300 Date: Sat, 17 May 2003 12:40:07 +0300 To: [EMAIL PROTECTED] Subject: Doesn't compile? Message-ID: [EMAIL PROTECTED] Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.4i From: Shaul Karl [EMAIL PROTECTED] Delivered-To: [EMAIL PROTECTED] X-Spam-Status: No, hits=-10.8 required=4.0 tests=BAYES_30,HAS_PACKAGE,UPPERCASE_50_75,USER_AGENT_MUTT autolearn=ham version=2.53-bugs.debian.org_2003_05_09 X-Spam-Level: X-Spam-Checker-Version: SpamAssassin 2.53-bugs.debian.org_2003_05_09 (1.174.2.15-2003-03-30-exp) Package: kernel-source-2.5.69 Version: 2.5.69-1 Severity: normal *** Please type your report below this line *** I get [ ... ] gcc -Wp,-MD,net/xfrm/.xfrm_algo.o.d -D__KERNEL__ -Iinclude -Wall -Wstrict-prototypes -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common -pipe -mpreferred-stack-boundary=2 -march=i486 -Iinclude/asm-i386/mach-default -fomit-frame-pointer -nostdinc -iwithprefix include-DKBUILD_BASENAME=xfrm_algo -DKBUILD_MODNAME=xfrm_algo -c -o net/xfrm/.tmp_xfrm_algo.o net/xfrm/xfrm_algo.c^M In file included from net/xfrm/xfrm_algo.c:16:^M include/net/ah.h: In function `ah_hmac_digest':^M include/net/ah.h:26: warning: implicit declaration of function `crypto_hmac_init'^M include/net/ah.h:27: `crypto_hmac_update' undeclared (first use in this function)^M include/net/ah.h:27: (Each undeclared identifier is reported only once^M include/net/ah.h:27: for each function it appears in.)^M include/net/ah.h:28: warning: implicit declaration of function `crypto_hmac_final'^M In file included from net/xfrm/xfrm_algo.c:19:^M include/net/esp.h: In function `esp_hmac_digest':^M include/net/esp.h:49: `crypto_hmac_update' undeclared (first use in this function)^M make[3]: *** [net/xfrm/xfrm_algo.o] Error 1^M make[2]: *** [net/xfrm] Error 2^M make[1]: *** [net] Error 2^M make[1]: Leaving directory `/tmp/kernel-source-2.5.69'^M make: *** [stamp-build] Error 2^M Here is .config: # # Automatically generated make config: don't edit # CONFIG_X86=y CONFIG_MMU=y CONFIG_UID16=y CONFIG_GENERIC_ISA_DMA=y # # Code maturity level options # CONFIG_EXPERIMENTAL=y # # General setup # CONFIG_SWAP=y CONFIG_SYSVIPC=y CONFIG_BSD_PROCESS_ACCT=y CONFIG_SYSCTL=y CONFIG_LOG_BUF_SHIFT=14 # # Loadable module support # CONFIG_MODULES=y CONFIG_MODULE_UNLOAD=y # CONFIG_MODULE_FORCE_UNLOAD is not set CONFIG_OBSOLETE_MODPARM=y CONFIG_MODVERSIONS=y CONFIG_KMOD=y # # Processor type and features # CONFIG_X86_PC=y # CONFIG_X86_VOYAGER is not set # CONFIG_X86_NUMAQ is not set # CONFIG_X86_SUMMIT is not set # CONFIG_X86_BIGSMP is not set # CONFIG_X86_VISWS is not set # CONFIG_M386 is not set CONFIG_M486=y # CONFIG_M586 is not set # CONFIG_M586TSC is not set # CONFIG_M586MMX is not set # CONFIG_M686 is not set # CONFIG_MPENTIUMII is not set # CONFIG_MPENTIUMIII is not set # CONFIG_MPENTIUM4 is not set # CONFIG_MK6 is not set # CONFIG_MK7 is not set # CONFIG_MK8 is not set # CONFIG_MELAN is not set # CONFIG_MCRUSOE is not set # CONFIG_MWINCHIPC6 is not set # CONFIG_MWINCHIP2 is not set # CONFIG_MWINCHIP3D is not set # CONFIG_MCYRIXIII is not set # CONFIG_MVIAC3_2 is not set # CONFIG_X86_GENERIC is not set CONFIG_X86_CMPXCHG=y CONFIG_X86_XADD=y CONFIG_X86_L1_CACHE_SHIFT=4 CONFIG_RWSEM_XCHGADD_ALGORITHM=y CONFIG_X86_PPRO_FENCE=y CONFIG_X86_F00F_BUG=y CONFIG_X86_WP_WORKS_OK=y CONFIG_X86_INVLPG=y CONFIG_X86_BSWAP=y CONFIG_X86_POPAD_OK=y CONFIG_X86_ALIGNMENT_16=y # CONFIG_HUGETLB_PAGE is not set # CONFIG_SMP is not set CONFIG_PREEMPT=y CONFIG_X86_UP_APIC=y
Bug#288812: kernel-image-2.4.27-1-686: upgrade from v2 to v6 breaks nvidia-kernel-2.4.27-1-686
The unresolved sumbols log would be useful, I am sad to say that an attempt to collect more info resulted in me wasting about 3 hours without a decent result. For some reason, when I rebooted into 2.6 (an attempt to avoid the you need to reboot soon), and did dpkg -i kernel-image-2.4.27-1-686_2.4.27-6_i386.deb the resulting kernel didn't want to boot. During the boot log it complained about being unable to load sg.o; I looked at the initrd image and found that sg.o wasn't there indeed. So I added a script /usr/share/initrd-tools/scripts/sg-module, containing the following: #!/bin/sh case $VERSION in 2.4.*) cp /lib/modules/$VERSION/kernel/drivers/scsi/sg.o \ $INITRDDIR/lib/modules/$VERSION/kernel/drivers/scsi/ ;; esac and manually re-created the 2.4 initrd. The kernel still refuses to boot, while no longer complaining about the absent sg.o; the last messages it spits out are pivot_root: No such file or directory /sbin/init: 425: could not open dev/console: No such file Kernel panic: Attempted to kill init! An attempt to downgrade back to -2 did not help this time, the results didn't change. Is something broken with my initrd-tools? Was it a stupid idea to do it under 2.6 rather than under 2.4 (the previous upgrades of 2.4 were done while running 2.4)? If you have any ideas what to do, I'll be happy to try them out to collect further info for you. plus something like lspci that shows what nvida board you have. So I installed module-assistant, and (under 2.6) did the following: module-assistant prepare module-assistant auto-install nvidia-kernel-source and now I have nvidia acceleration working under my 2.6. Here's the lspci output (collected under 2.6): :00:00.0 Host bridge: Intel Corp. 82865G/PE/P DRAM Controller/Host-Hub Interface (rev 02) :00:01.0 PCI bridge: Intel Corp. 82865G/PE/P PCI to AGP Controller (rev 02) :00:1d.0 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #1 (rev 02) :00:1d.1 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #2 (rev 02) :00:1d.2 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #3 (rev 02) :00:1d.3 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB UHCI #4 (rev 02) :00:1d.7 USB Controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) USB2 EHCI Controller (rev 02) :00:1e.0 PCI bridge: Intel Corp. 82801 PCI Bridge (rev c2) :00:1f.0 ISA bridge: Intel Corp. 82801EB/ER (ICH5/ICH5R) LPC Bridge (rev 02) :00:1f.2 IDE interface: Intel Corp. 82801EB (ICH5) Serial ATA 150 Storage Controller (rev 02) :00:1f.3 SMBus: Intel Corp. 82801EB/ER (ICH5/ICH5R) SMBus Controller (rev 02) :00:1f.5 Multimedia audio controller: Intel Corp. 82801EB/ER (ICH5/ICH5R) AC'97 Audio Controller (rev 02) :01:00.0 VGA compatible controller: nVidia Corporation NV18 [GeForce4 MX 440 AGP 8x] (rev c1) :03:08.0 Ethernet controller: Intel Corp. 82562EZ 10/100 Ethernet Controller (rev 02) :03:09.0 Communication controller: PCTel Inc HSP MicroModem 56 (rev 01) :03:0c.0 SCSI storage controller: Advanced System Products, Inc ABP940-U / ABP960-U (rev 03) Kind regards, Vassilii
Bug#281372: marked as done (kernel-source-2.4.27: Crash on Dell PE 8450)
Your message dated Sat, 08 Jan 2005 17:14:22 + with message-id [EMAIL PROTECTED] and subject line This bug can be closed has caused the attached Bug report to be marked as done. This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database) -- Received: (at submit) by bugs.debian.org; 15 Nov 2004 13:07:54 + From [EMAIL PROTECTED] Mon Nov 15 05:07:54 2004 Return-path: [EMAIL PROTECTED] Received: from lorn.amazing-internet.net (allanon.amazing-internet.net) [213.210.55.94] by spohr.debian.org with esmtp (Exim 3.35 1 (Debian)) id 1CTgaH-0004DV-00; Mon, 15 Nov 2004 05:07:53 -0800 Received: from [172.16.1.17] (helo=tardis.amazing-internet.net) by allanon.amazing-internet.net with esmtp (Exim 3.35 #1 (Debian)) id 1CTgZS-0002tQ-00; Mon, 15 Nov 2004 13:07:02 + Received: from ronny by tardis.amazing-internet.net with local (Exim 3.35 #1 (Debian)) id 1CTgZS-0001VS-00; Mon, 15 Nov 2004 13:07:02 + From: Ronny Adsetts [EMAIL PROTECTED] To: Debian Bug Tracking System [EMAIL PROTECTED] Subject: kernel-source-2.4.27: Crash on Dell PE 8450 X-Mailer: reportbug 1.50 Date: Mon, 15 Nov 2004 13:07:02 + Message-Id: [EMAIL PROTECTED] Sender: Ronny Adsetts [EMAIL PROTECTED] X-MailScanner: Found to be clean X-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (score=-4.163, required 5.8, AWL -0.25, BAYES_00 -4.90, J_CHICKENPOX_41 0.60, TW_EV 0.08, TW_LV 0.08, TW_VG 0.08, TW_VP 0.08, TW_WP 0.08) Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE autolearn=no version=2.60-bugs.debian.org_2004_03_25 X-Spam-Level: Package: kernel-source-2.4.27 Version: 2.4.27-5 Severity: important This is using a kernel compiled using the config from kernel-image-2.4.27-1-686-smp for woody with the required tools backported. I'm fairly confident that this is a kernel issue rather than an issue with the backported tools otherwise I wouldn't be reporting it via the debian BTS. I'm currently running 2.4.26 compiled in the same way which crashes roughly about every 40 days or so. Built this latest 2.4 kernel to see if it helps any. The kernel lasted about 6 hours before bailing. I have an oops but can only run ksymoops while booted in 2.4.26 at the moment. I can do limited testing provided I have time to schedule it as the machine is in production. The important bits about this system as far as I can make out are that it's made to work quite hard doing backups. XFS on LVM on hardware RAID (Mylex extremeraid 3000 - DAC960 driver). We snapshot the LVM partitions before dumping to backup using xfsdump. xfs_freeze is used to quiesce the partitions before snapshotting. A couple of the partitions are exported using NFS. Thanks for any help you can give. Some info about the system, let me know what else you need: Other relevant dependancies: ii lvm-common 1.5.12aiwoody1 The Logical Volume Manager for Linux (common ii lvm10 1.0.8-2aiwoody The Logical Volume Manager for Linux ii xfsdump2.2.18-1aiwood Administrative utilities for the XFS filesys ii xfslibs-dev2.6.5-1aiwoody XFS filesystem-specific static libraries and ii xfsprogs 2.6.5-1aiwoody Utilities for managing the XFS filesystem $ df -h /dev/sda2 184M 122M 62M 67% / /dev/sda3 1.8G 14M 1.8G 1% /tmp /dev/sda5 2.8G 1.5G 1.4G 53% /usr /dev/sda6 1.9G 1.2G 699M 64% /var /dev/vg0/home_lv 30G 26G 5.0G 84% /home /dev/vg0/shared_lv 40G 28G 13G 69% /usr/local/shared /dev/vg0/archive_lv 150G 128G 23G 86% /usr/local/archive /dev/vg0/dbbackups_lv 20G 15G 5.5G 73% /usr/local/dbbackups /dev/vg0/software_lv 12G 9.7G 2.4G 81% /usr/local/software /dev/vg0/mirrors_lv12G 8.9G 3.2G 74% /usr/local/mirrors /dev/vg0/cvsroot_lv 8.0G 5.9G 2.2G 74% /usr/local/cvsroot /dev/vg0/music_lv 20G 8.1G 12G 41% /usr/local/music /dev/vg0/mail_lv 20G 2.3G 18G 12% /var/local/mail /usr/local/shared/_ftp-outgoing 40G 28G 13G 69% /home/ftp/outgoing /usr/local/shared/_ftp-incoming 40G 28G 13G 69% /home/ftp/incoming $ mount /dev/sda2 on / type xfs (rw) proc on /proc type proc (rw) devpts on /dev/pts type devpts (rw,gid=5,mode=620) /dev/sda3 on /tmp type xfs (rw) /dev/sda5 on /usr type xfs (rw) /dev/sda6 on /var type xfs (rw) /dev/vg0/home_lv on /home type xfs (rw,usrquota) /dev/vg0/shared_lv
Bug#283241: kernel-image-2.6.8-1-k7: 2.6.8 and 2.6.9: utime(2) hangs on smbfs
This bug does not exist in the vanilla version of 2.6.8. A patch added somewhere in the Debian kernel-source-2.6.8 packages breaks it. I, however, cannot seem to find any patches that should touch smbfs, so I can't point it out. I just just rebuilt that particular module with the sources from kernel.org and everything works just as well as before. I believe this bug is severe enough to force a fix in Sarge! It renders smbfs TOTALLY useless. -- Sren Hansen [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature
Bug#283241: kernel-image-2.6.8-1-k7: 2.6.8 and 2.6.9: utime(2) hangs on smbfs
Found the offending patch! It's called smbfs-overflow-fixes.dpatch. I've attached a patch that should fix the same overflow issues, but without breaking utime functionality. It's stolen from 2.6.10-ac7. :-) -- Sren Hansen [EMAIL PROTECTED] diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.10/fs/smbfs/proc.c linux-2.6.10/fs/smbfs/proc.c --- linux.vanilla-2.6.10/fs/smbfs/proc.c 2004-12-25 21:15:41.0 + +++ linux-2.6.10/fs/smbfs/proc.c 2004-12-26 23:03:13.0 + @@ -1427,9 +1427,9 @@ * So we must first calculate the amount of padding used by the server. */ data_off -= hdrlen; - if (data_off SMB_READX_MAX_PAD) { - PARANOIA(offset is larger than max pad!\n); - PARANOIA(%d %d\n, data_off, SMB_READX_MAX_PAD); + if (data_off SMB_READX_MAX_PAD || data_off 0) { + PARANOIA(offset is larger than SMB_READX_MAX_PAD or negative!\n); + PARANOIA(%d %d || %d 0\n, data_off, SMB_READX_MAX_PAD, data_off); req-rq_rlen = req-rq_bufsize + 1; return; } diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.10/fs/smbfs/request.c linux-2.6.10/fs/smbfs/request.c --- linux.vanilla-2.6.10/fs/smbfs/request.c 2004-12-25 21:15:41.0 + +++ linux-2.6.10/fs/smbfs/request.c 2004-12-26 23:06:24.0 + @@ -588,8 +588,18 @@ data_count = WVAL(inbuf, smb_drcnt); /* Modify offset for the split header/buffer we use */ - data_offset -= hdrlen; - parm_offset -= hdrlen; + if (data_count || data_offset) { + if (unlikely(data_offset hdrlen)) + goto out_bad_data; + else + data_offset -= hdrlen; + } + if (parm_count || parm_offset) { + if (unlikely(parm_offset hdrlen)) + goto out_bad_parm; + else + parm_offset -= hdrlen; + } if (parm_count == parm_tot data_count == data_tot) { /* @@ -600,18 +610,22 @@ * response that fits. */ VERBOSE(single trans2 response - dcnt=%d, pcnt=%d, doff=%d, poff=%d\n, + dcnt=%u, pcnt=%u, doff=%u, poff=%u\n, data_count, parm_count, data_offset, parm_offset); req-rq_ldata = data_count; req-rq_lparm = parm_count; req-rq_data = req-rq_buffer + data_offset; req-rq_parm = req-rq_buffer + parm_offset; + if (unlikely(parm_offset + parm_count req-rq_rlen)) + goto out_bad_parm; + if (unlikely(data_offset + data_count req-rq_rlen)) + goto out_bad_data; return 0; } VERBOSE(multi trans2 response - frag=%d, dcnt=%d, pcnt=%d, doff=%d, poff=%d\n, + frag=%d, dcnt=%u, pcnt=%u, doff=%u, poff=%u\n, req-rq_fragment, data_count, parm_count, data_offset, parm_offset); @@ -638,13 +652,15 @@ req-rq_parm = req-rq_trans2buffer; req-rq_data = req-rq_trans2buffer + parm_tot; - } else if (req-rq_total_data data_tot || - req-rq_total_parm parm_tot) + } else if (unlikely(req-rq_total_data data_tot || + req-rq_total_parm parm_tot)) goto out_data_grew; - if (parm_disp + parm_count req-rq_total_parm) + if (unlikely(parm_disp + parm_count req-rq_total_parm || + parm_offset + parm_count req-rq_rlen)) goto out_bad_parm; - if (data_disp + data_count req-rq_total_data) + if (unlikely(data_disp + data_count req-rq_total_data || + data_offset + data_count req-rq_rlen)) goto out_bad_data; inbuf = req-rq_buffer; @@ -666,10 +682,9 @@ return 1; out_too_long: - printk(KERN_ERR smb_trans2: data/param too long, data=%d, parm=%d\n, + printk(KERN_ERR smb_trans2: data/param too long, data=%u, parm=%u\n, data_tot, parm_tot); - req-rq_errno = -EIO; - goto out; + goto out_EIO; out_no_mem: printk(KERN_ERR smb_trans2: couldn't allocate data area of %d bytes\n, req-rq_trans2bufsize); @@ -677,16 +692,15 @@ goto out; out_data_grew: printk(KERN_ERR smb_trans2: data/params grew!\n); - req-rq_errno = -EIO; - goto out; + goto out_EIO; out_bad_parm: - printk(KERN_ERR smb_trans2: invalid parms, disp=%d, cnt=%d, tot=%d\n, - parm_disp, parm_count, parm_tot); - req-rq_errno = -EIO; - goto out; + printk(KERN_ERR smb_trans2: invalid parms, disp=%u, cnt=%u, tot=%u, ofs=%u\n, + parm_disp, parm_count, parm_tot, parm_offset); + goto out_EIO; out_bad_data: - printk(KERN_ERR smb_trans2: invalid data, disp=%d, cnt=%d, tot=%d\n, - data_disp, data_count, data_tot); + printk(KERN_ERR smb_trans2: invalid data, disp=%u, cnt=%u, tot=%u, ofs=%u\n, + data_disp, data_count, data_tot, data_offset); +out_EIO: req-rq_errno = -EIO; out: return req-rq_errno; smime.p7s Description: S/MIME cryptographic signature
Bug#283241: kernel-image-2.6.8-1-k7: 2.6.8 and 2.6.9: utime(2) hangs on smbfs
On Sat, Jan 08, 2005 at 06:36:27PM +0100, S?ren Hansen wrote: This bug does not exist in the vanilla version of 2.6.8. A patch added somewhere in the Debian kernel-source-2.6.8 packages breaks it. I, however, cannot seem to find any patches that should touch smbfs, so I can't point it out. I just just rebuilt that particular module with the sources from kernel.org and everything works just as well as before. I believe this bug is severe enough to force a fix in Sarge! It renders smbfs TOTALLY useless. -- S??ren Hansen [EMAIL PROTECTED] When merging to 2.6.10 I noticed we have a bunch of smbfs changes that were labelled security fixes. Can you try to rebuild the kernel (or just smbfs.ko) with the patch below reversed? #! /bin/sh -e ## PATCHNAME.dpatch by [EMAIL PROTECTED] ## ## All lines beginning with `## DP:' are a description of the patch. ## DP: Description: SMBfs overflow fixes ## DP: Patch author: unknown, stolen from -ac tree (probably Stefan Esser, Juan Quintela, and Urban Widmark) ## DP: Upstream status: unknown . $(dirname $0)/DPATCH @DPATCH@ diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.9/fs/smbfs/proc.c linux-2.6.9/fs/smbfs/proc.c --- linux.vanilla-2.6.9/fs/smbfs/proc.c 2004-10-20 23:17:20.0 +0100 +++ linux-2.6.9/fs/smbfs/proc.c 2004-11-17 19:41:41.0 + @@ -1427,9 +1427,9 @@ * So we must first calculate the amount of padding used by the server. */ data_off -= hdrlen; - if (data_off SMB_READX_MAX_PAD) { - PARANOIA(offset is larger than max pad!\n); - PARANOIA(%d %d\n, data_off, SMB_READX_MAX_PAD); + if (data_off SMB_READX_MAX_PAD || data_off 0) { + PARANOIA(offset is larger than SMB_READX_MAX_PAD or negative!\n); + PARANOIA(%d %d || %d 0\n, data_off, SMB_READX_MAX_PAD, data_off); req-rq_rlen = req-rq_bufsize + 1; return; } diff -u --new-file --recursive --exclude-from /usr/src/exclude linux.vanilla-2.6.9/fs/smbfs/request.c linux-2.6.9/fs/smbfs/request.c --- linux.vanilla-2.6.9/fs/smbfs/request.c 2004-10-20 22:33:50.0 +0100 +++ linux-2.6.9/fs/smbfs/request.c 2004-11-17 19:41:41.0 + @@ -588,6 +588,10 @@ data_count = WVAL(inbuf, smb_drcnt); /* Modify offset for the split header/buffer we use */ + if (data_offset hdrlen) + goto out_bad_data; + if (parm_offset hdrlen) + goto out_bad_parm; data_offset -= hdrlen; parm_offset -= hdrlen; @@ -607,6 +611,10 @@ req-rq_lparm = parm_count; req-rq_data = req-rq_buffer + data_offset; req-rq_parm = req-rq_buffer + parm_offset; + if (parm_offset + parm_count req-rq_rlen) + goto out_bad_parm; + if (data_offset + data_count req-rq_rlen) + goto out_bad_data; return 0; } @@ -643,8 +652,12 @@ if (parm_disp + parm_count req-rq_total_parm) goto out_bad_parm; + if (parm_offset + parm_count req-rq_rlen) + goto out_bad_parm; if (data_disp + data_count req-rq_total_data) goto out_bad_data; + if (data_offset + data_count req-rq_rlen) + goto out_bad_data; inbuf = req-rq_buffer; memcpy(req-rq_parm + parm_disp, inbuf + parm_offset, parm_count); @@ -676,13 +692,13 @@ req-rq_errno = -EIO; goto out; out_bad_parm: - printk(KERN_ERR smb_trans2: invalid parms, disp=%d, cnt=%d, tot=%d\n, - parm_disp, parm_count, parm_tot); + printk(KERN_ERR smb_trans2: invalid parms, disp=%d, cnt=%d, tot=%d, ofs=%d\n, + parm_disp, parm_count, parm_tot, parm_offset); req-rq_errno = -EIO; goto out; out_bad_data: - printk(KERN_ERR smb_trans2: invalid data, disp=%d, cnt=%d, tot=%d\n, - data_disp, data_count, data_tot); + printk(KERN_ERR smb_trans2: invalid data, disp=%d, cnt=%d, tot=%d, ofs=%d\n, + data_disp, data_count, data_tot, data_offset); req-rq_errno = -EIO; out: return req-rq_errno;
Bug#282751: This just bit me, hard.
Hi, My first Sarge install, from a brand new download of the Netinst image, went to hell because of this problem. To replicate: 1. download Netinst image, and burn cd. 2. run the netinst cd with linux26 3. do not run tasksel or otherwise add packages (this was difficult under the new install) 4. run apt-get update, then apt-get upgrade. (you will be told that LILO needs to be run) 5. lilo fails when run. Rebooting w/o running LILO leaves a hosed system, perhaps recoverable. So IMO this bug is leaving frass all over the place. Thanks, Jim
Re: make gconfig segfaults
On Sat, 2005-01-08 at 01:20 +0100, Stefan Soeffing wrote: After the last apt-get update apt-get upgrade I can't configure my kernel any more: [EMAIL PROTECTED]:/usr/src/kernel-source-2.6.8# make gconfig scripts/kconfig/gconf arch/i386/Kconfig (gconf:6136): Gtk-CRITICAL **: file gtklabel.c: line 2792 (gtk_label_set_use_underline): assertion `GTK_IS_LABEL (label)' failed [...] (gconf:6136): Gtk-CRITICAL **: file gtklabel.c: line 2792 (gtk_label_set_use_underline): assertion `GTK_IS_LABEL (label)' failed (gconf:6136): GLib-GObject-WARNING **: gsignal.c:1709: signal `pressed' is invalid for instance `0x80c8188' (gconf:6136): GLib-GObject-WARNING **: gsignal.c:1709: signal `pressed' is invalid for instance `0x80ca4c8' (gconf:6136): GLib-GObject-WARNING **: gsignal.c:1709: signal `pressed' is invalid for instance `0x80ca958' (gconf:6136): GLib-GObject-WARNING **: gsignal.c:1709: signal `pressed' is invalid for instance `0x80c8668' (gconf:6136): GLib-GObject-WARNING **: gsignal.c:1709: signal `pressed' is invalid for instance `0x80bda58' make[1]: *** [gconfig] Segmentation fault make: *** [gconfig] Error 2 --- Unfortunately I can't tell which packet/update caused the problem. It was caused by several things ... the update of libglade2-0, for instance, see #288445. However, there were several things in the gconf.c code that made it worse. Included are a rather messy patch to both gconf.c and gconf.glade. I ran glade-2 on the glade file, fixed two missing stock icons and cleaned up the C code that inserts the single/split/full modes. The rest of the patch is minor cleanups only. I refrained from using all the included xpm icons in images.c (like qconf.cc does) in favour of using the stock Gtk+ icons instead. Oh, yes there was a back bug in split mode that I also removed, oh well... Hope this helps somebody, event though I seriously doubt that this will ever make it into the kernel tree. Regards /Jocke --- gconf-old.c 2004-08-14 07:38:04.0 +0200 +++ gconf.c 2005-01-08 20:41:42.0 +0100 @@ -178,17 +178,31 @@ } -/* Main Window Initialization */ +void replace_button_icon(GladeXML * xml, GdkDrawable * window, + GtkStyle * style, gchar * btn_name, gchar ** xpm) +{ + GdkPixmap *pixmap; + GdkBitmap *mask; + GtkToolButton *button; + GtkWidget *image; + pixmap = gdk_pixmap_create_from_xpm_d(window, mask, + style-bg[GTK_STATE_NORMAL], + xpm); + + button = GTK_TOOL_BUTTON(glade_xml_get_widget(xml, btn_name)); + image = gtk_image_new_from_pixmap(pixmap, mask); + gtk_widget_show(image); + gtk_tool_button_set_icon_widget(button, image); +} +/* Main Window Initialization */ void init_main_window(const gchar * glade_file) { GladeXML *xml; GtkWidget *widget; GtkTextBuffer *txtbuf; char title[256]; - GdkPixmap *pixmap; - GdkBitmap *mask; GtkStyle *style; xml = glade_xml_new(glade_file, window1, NULL); @@ -221,36 +235,22 @@ style = gtk_widget_get_style(main_wnd); widget = glade_xml_get_widget(xml, toolbar1); - pixmap = gdk_pixmap_create_from_xpm_d(main_wnd-window, mask, - style-bg[GTK_STATE_NORMAL], - (gchar **) xpm_single_view); - gtk_image_set_from_pixmap(GTK_IMAGE - (((GtkToolbarChild - *) (g_list_nth(GTK_TOOLBAR(widget)- - children, - 5)-data))-icon), - pixmap, mask); - pixmap = - gdk_pixmap_create_from_xpm_d(main_wnd-window, mask, - style-bg[GTK_STATE_NORMAL], - (gchar **) xpm_split_view); - gtk_image_set_from_pixmap(GTK_IMAGE - (((GtkToolbarChild - *) (g_list_nth(GTK_TOOLBAR(widget)- - children, - 6)-data))-icon), - pixmap, mask); - pixmap = - gdk_pixmap_create_from_xpm_d(main_wnd-window, mask, - style-bg[GTK_STATE_NORMAL], - (gchar **) xpm_tree_view); - gtk_image_set_from_pixmap(GTK_IMAGE - (((GtkToolbarChild - *) (g_list_nth(GTK_TOOLBAR(widget)- - children, - 7)-data))-icon), - pixmap, mask); +#if 0 /* Use stock Gtk icons instead */ + replace_button_icon(xml, main_wnd-window, style, + button1, (gchar **) xpm_back); + replace_button_icon(xml, main_wnd-window, style, + button2, (gchar **) xpm_load); + replace_button_icon(xml, main_wnd-window, style, + button3, (gchar **) xpm_save); +#endif + replace_button_icon(xml, main_wnd-window, style, + button4, (gchar **) xpm_single_view); + replace_button_icon(xml, main_wnd-window, style, + button5, (gchar **) xpm_split_view); + replace_button_icon(xml, main_wnd-window, style, + button6, (gchar **) xpm_tree_view); +#if 0 switch (view_mode) { case SINGLE_VIEW: widget = glade_xml_get_widget(xml, button4); @@ -265,7 +265,7 @@ gtk_button_clicked(GTK_BUTTON(widget)); break; } - +#endif txtbuf = gtk_text_view_get_buffer(GTK_TEXT_VIEW(text_w)); tag1 = gtk_text_buffer_create_tag(txtbuf, mytag1, foreground, red, @@ -323,7 +323,7 @@ gtk_tree_view_set_model(view, model1);
kernel-patch-powerpc-2.6.9_2.6.9-2_powerpc.changes UNACCEPT
Rejected: Rejected: kernel-image-power3-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-patch-powerpc-2.6.9_2.6.9-2_all.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-patch-powerpc-2.6.9_2.6.9-2.dsc: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power3-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power3_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power3_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-powerpc_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power3-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-powerpc_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power3_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power4-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-powerpc_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power4_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-powerpc-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-power4_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power4_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-build-2.6.9-power4-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-2.6.9-power4-smp_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-image-powerpc-smp_2.6.9-2_powerpc.deb: old version (100) in unstable = new version (2.6.9-2) targeted at unstable. Rejected: Rejected: kernel-headers-2.6.9_2.6.9-2_powerpc.deb: old version (2.6.9-3) in unstable = new version (2.6.9-2) targeted at unstable. === Despite being ACCEPTed, this package failed the database sanity checks at the time of install. This should only happen rarely and in corner-cases (a binary upload of a package which has since been melanie'd for example), so no code to do the necessary unaccept actions has been written. These actions (e.g. bug reopening, announcement rescinding, etc.) will have to be done by hand. Also, the files have been left in the accepted directory; please deal with them as well.
Processing of kernel-image-2.6.9-i386_2.6.9-5_i386.changes
kernel-image-2.6.9-i386_2.6.9-5_i386.changes uploaded successfully to localhost along with the files: kernel-image-2.6.9-i386_2.6.9-5.dsc kernel-image-2.6.9-i386_2.6.9-5.tar.gz kernel-headers-2.6.9-2_2.6.9-5_i386.deb kernel-headers-2.6.9-2-686-smp_2.6.9-5_i386.deb kernel-image-2.6.9-2-686-smp_2.6.9-5_i386.deb kernel-headers-2.6.9-2-386_2.6.9-5_i386.deb kernel-image-2.6.9-2-386_2.6.9-5_i386.deb kernel-headers-2.6.9-2-k7_2.6.9-5_i386.deb kernel-image-2.6.9-2-k7_2.6.9-5_i386.deb kernel-headers-2.6.9-2-686_2.6.9-5_i386.deb kernel-image-2.6.9-2-686_2.6.9-5_i386.deb kernel-headers-2.6.9-2-k7-smp_2.6.9-5_i386.deb kernel-image-2.6.9-2-k7-smp_2.6.9-5_i386.deb Greetings, Your Debian queue daemon
Processing of kernel-image-2.6.8-i386_2.6.8-12_i386.changes
kernel-image-2.6.8-i386_2.6.8-12_i386.changes uploaded successfully to localhost along with the files: kernel-image-2.6.8-i386_2.6.8-12.dsc kernel-image-2.6.8-i386_2.6.8-12.tar.gz kernel-headers-2.6.8-2_2.6.8-12_i386.deb kernel-headers-2.6.8-2-686-smp_2.6.8-12_i386.deb kernel-image-2.6.8-2-686-smp_2.6.8-12_i386.deb kernel-headers-2.6.8-2-386_2.6.8-12_i386.deb kernel-image-2.6.8-2-386_2.6.8-12_i386.deb kernel-headers-2.6.8-2-k7_2.6.8-12_i386.deb kernel-image-2.6.8-2-k7_2.6.8-12_i386.deb kernel-headers-2.6.8-2-686_2.6.8-12_i386.deb kernel-image-2.6.8-2-686_2.6.8-12_i386.deb kernel-headers-2.6.8-2-k7-smp_2.6.8-12_i386.deb kernel-image-2.6.8-2-k7-smp_2.6.8-12_i386.deb Greetings, Your Debian queue daemon
kernel-image-2.6.8-i386_2.6.8-12_i386.changes ACCEPTED
Accepted: kernel-headers-2.6.8-2-386_2.6.8-12_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-386_2.6.8-12_i386.deb kernel-headers-2.6.8-2-686-smp_2.6.8-12_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-686-smp_2.6.8-12_i386.deb kernel-headers-2.6.8-2-686_2.6.8-12_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-686_2.6.8-12_i386.deb kernel-headers-2.6.8-2-k7-smp_2.6.8-12_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-k7-smp_2.6.8-12_i386.deb kernel-headers-2.6.8-2-k7_2.6.8-12_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2-k7_2.6.8-12_i386.deb kernel-headers-2.6.8-2_2.6.8-12_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-headers-2.6.8-2_2.6.8-12_i386.deb kernel-image-2.6.8-2-386_2.6.8-12_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-386_2.6.8-12_i386.deb kernel-image-2.6.8-2-686-smp_2.6.8-12_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-686-smp_2.6.8-12_i386.deb kernel-image-2.6.8-2-686_2.6.8-12_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-686_2.6.8-12_i386.deb kernel-image-2.6.8-2-k7-smp_2.6.8-12_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-k7-smp_2.6.8-12_i386.deb kernel-image-2.6.8-2-k7_2.6.8-12_i386.deb to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-2-k7_2.6.8-12_i386.deb kernel-image-2.6.8-i386_2.6.8-12.dsc to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-12.dsc kernel-image-2.6.8-i386_2.6.8-12.tar.gz to pool/main/k/kernel-image-2.6.8-i386/kernel-image-2.6.8-i386_2.6.8-12.tar.gz Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian.
kernel-image-2.6.9-i386_2.6.9-5_i386.changes ACCEPTED
Accepted: kernel-headers-2.6.9-2-386_2.6.9-5_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-headers-2.6.9-2-386_2.6.9-5_i386.deb kernel-headers-2.6.9-2-686-smp_2.6.9-5_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-headers-2.6.9-2-686-smp_2.6.9-5_i386.deb kernel-headers-2.6.9-2-686_2.6.9-5_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-headers-2.6.9-2-686_2.6.9-5_i386.deb kernel-headers-2.6.9-2-k7-smp_2.6.9-5_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-headers-2.6.9-2-k7-smp_2.6.9-5_i386.deb kernel-headers-2.6.9-2-k7_2.6.9-5_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-headers-2.6.9-2-k7_2.6.9-5_i386.deb kernel-headers-2.6.9-2_2.6.9-5_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-headers-2.6.9-2_2.6.9-5_i386.deb kernel-image-2.6.9-2-386_2.6.9-5_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-image-2.6.9-2-386_2.6.9-5_i386.deb kernel-image-2.6.9-2-686-smp_2.6.9-5_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-image-2.6.9-2-686-smp_2.6.9-5_i386.deb kernel-image-2.6.9-2-686_2.6.9-5_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-image-2.6.9-2-686_2.6.9-5_i386.deb kernel-image-2.6.9-2-k7-smp_2.6.9-5_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-image-2.6.9-2-k7-smp_2.6.9-5_i386.deb kernel-image-2.6.9-2-k7_2.6.9-5_i386.deb to pool/main/k/kernel-image-2.6.9-i386/kernel-image-2.6.9-2-k7_2.6.9-5_i386.deb kernel-image-2.6.9-i386_2.6.9-5.dsc to pool/main/k/kernel-image-2.6.9-i386/kernel-image-2.6.9-i386_2.6.9-5.dsc kernel-image-2.6.9-i386_2.6.9-5.tar.gz to pool/main/k/kernel-image-2.6.9-i386/kernel-image-2.6.9-i386_2.6.9-5.tar.gz Announcing to debian-devel-changes@lists.debian.org Thank you for your contribution to Debian.
Bug#283241: kernel-image-2.6.8-1-k7: 2.6.8 and 2.6.9: utime(2) hangs on smbfs
lr, 08 01 2005 kl. 19:35 +0100, skrev Christoph Hellwig: When merging to 2.6.10 I noticed we have a bunch of smbfs changes that were labelled security fixes. Can you try to rebuild the kernel (or just smbfs.ko) with the patch below reversed? Just as expected, that cleared it right up. The patch fixes some relevant issues, so I don't think it should just be rolled back. However, the patch, I attached to my previous mail should: * contain the overflow fixes, too * not break other stuff If you're not comfortable applying my patch, I could talk to Urban Widmark (the smbfs maintainer) and have him verify it ? -- Sren Hansen [EMAIL PROTECTED] smime.p7s Description: S/MIME cryptographic signature
Bug#289290: fixed
We believe that the bug you reported is now fixed; the following package(s) have been removed from unstable: kernel-patch-powerpc-2.6.8 |2.6.8-7 | all Note that the package(s) have simply been removed from the tag database and may (or may not) still be in the pool; this is not a bug. The package(s) will be physically removed automatically when no suite references them (and in the case of source, when no binary references it). Please also remember that the changes have been done on the master archive (ftp-master.debian.org) and will not propagate to any mirrors (ftp.debian.org included) until the next cron.daily run at the earliest. Packages are never removed from testing by hand. Testing tracks unstable and will automatically remove packages which were removed from unstable when removing them from testing causes no dependency problems. Bugs which have been reported against this package are not automatically removed from the Bug Tracking System. Please check all open bugs and close them or re-assign them to another package if the removed package was superseded by another one. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED] This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED] Debian distribution maintenance software pp. Anthony Towns (the ftpmaster behind the curtain)
Bug#67718: no fatty is pretty thompson shark
To tell 'em, wou'd a hundred Tongues require, After all those christmas festivities, you will need to lose those extra pounds you may have taked. There is not many way to do it fast. With Dyapex, we can solve your problem easily. For more information, please Visit our Online Store. http://bookmobile.fantasticsize.com/ddp/index.php?id=27 the radiance luring her gaze away Hang a lantern aloft in the belfry arch Each Motion guides, and ev'ry Nerve sustains; Seymour 15586331072989121--
kernel-source-2.6.10_2.6.10-2_i386.changes ACCEPTED
Accepted: kernel-doc-2.6.10_2.6.10-2_all.deb to pool/main/k/kernel-source-2.6.10/kernel-doc-2.6.10_2.6.10-2_all.deb kernel-patch-debian-2.6.10_2.6.10-2_all.deb to pool/main/k/kernel-source-2.6.10/kernel-patch-debian-2.6.10_2.6.10-2_all.deb kernel-source-2.6.10_2.6.10-2.diff.gz to pool/main/k/kernel-source-2.6.10/kernel-source-2.6.10_2.6.10-2.diff.gz kernel-source-2.6.10_2.6.10-2.dsc to pool/main/k/kernel-source-2.6.10/kernel-source-2.6.10_2.6.10-2.dsc kernel-source-2.6.10_2.6.10-2_all.deb to pool/main/k/kernel-source-2.6.10/kernel-source-2.6.10_2.6.10-2_all.deb kernel-source-2.6.10_2.6.10.orig.tar.gz to pool/main/k/kernel-source-2.6.10/kernel-source-2.6.10_2.6.10.orig.tar.gz kernel-tree-2.6.10_2.6.10-2_all.deb to pool/main/k/kernel-source-2.6.10/kernel-tree-2.6.10_2.6.10-2_all.deb Announcing to debian-devel-changes@lists.debian.org Closing bugs: 289155 Thank you for your contribution to Debian.