Your message dated Thu, 9 Feb 2012 16:01:50 -0600 with message-id <20120209220150.GA3153@burratino> and subject line Re: linux-2.6: Removal and reinsertion of floppy or mtdblock device can cause oops has caused the Debian Bug report #593304, regarding linux-2.6: Removal and reinsertion of floppy or mtdblock device can cause oops 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 this message is talking about, this may indicate a serious mail system misconfiguration somewhere. Please contact owner@bugs.debian.org immediately.) -- 593304: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=593304 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: linux-2.6: Removal and reinsertion of floppy or mtdblock device can cause oops
- From: Ben Hutchings <ben@decadent.org.uk>
- Date: Tue, 17 Aug 2010 04:09:46 +0100
- Message-id: <1282014586.3454.56.camel@localhost>
Package: linux-2.6 Version: 2.6.26-24 Severity: important There is a bug in the backing-device sysfs code, added in 2.6.26 and fixed in 2.6.28 by the following commits: commit f1d0b063d993527754f062c589b73f125024d216 Author: Kay Sievers <kay.sievers@vrfy.org> Date: Tue Dec 2 10:31:50 2008 -0800 bdi: register sysfs bdi device only once per queue Devices which share the same queue, like floppies and mtd devices, get registered multiple times in the bdi interface, but bdi accounts only the last registered device of the devices sharing one queue. On remove, all earlier registered devices leak, stay around in sysfs, and cause "duplicate filename" errors if the devices are re-created. commit 69fc208be5b7eb18d22d1eca185b201400fd5ffc Author: Andrew Morton <akpm@linux-foundation.org> Date: Tue Dec 9 13:14:06 2008 -0800 mm/backing-dev.c: remove recently-added WARN_ON() On second thoughts, this is just going to disturb people while telling us things which we already knew. In the case of mtdblock the result of the bug is not just a warning but an oops (use of null pointer) that leaves the system unusable. I'm not sure about the floppy driver. In any case, these changes are small and seem low-risk; they were also accepted in stable version 2.6.27.51. Ben. -- Ben Hutchings Once a job is fouled up, anything done to improve it makes it worse.Attachment: signature.asc
Description: This is a digitally signed message part
--- End Message ---
--- Begin Message ---
- To: 593304-done@bugs.debian.org
- Subject: Re: linux-2.6: Removal and reinsertion of floppy or mtdblock device can cause oops
- From: Jonathan Nieder <jrnieder@gmail.com>
- Date: Thu, 9 Feb 2012 16:01:50 -0600
- Message-id: <20120209220150.GA3153@burratino>
- In-reply-to: <1282099931.3454.133.camel@localhost>
- References: <1282014586.3454.56.camel@localhost> <1282099931.3454.133.camel@localhost>
Ben Hutchings wrote: > On Tue, 2010-08-17 at 04:09 +0100, Ben Hutchings wrote: >> There is a bug in the backing-device sysfs code, added in 2.6.26 and >> fixed in 2.6.28 by the following commits: [...] > Does this look worth fixing in lenny? Closing for end of lenny support.
--- End Message ---