linux-kernel - Re: Floppy constantly accessed in 2.6.31-rc2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Date:	Mon, 13 Jul 2009 17:36:45 -0600
From:	Robert Hancock <hancockrwd@...il.com>
To:	Paul Bolle <pebolle@...cali.nl>
CC:	linux-kernel@...r.kernel.org,
	Andrew Morton <akpm@...ux-foundation.org>
Subject: Re: Floppy constantly accessed in 2.6.31-rc2

On 07/13/2009 05:06 PM, Paul Bolle wrote:
> On Sun, 2009-07-12 at 23:44 -0600, Robert Hancock wrote:
>> On 2.6.31-rc2 (actually current git as of today) the floppy drive is
>> constantly being accessed with these messages being reported:
>>
>> Platform driver 'floppy' needs updating - please use dev_pm_ops
>> Floppy drive(s): fd0 is 1.44M
>> FDC 0 is a post-1991 82077
>> end_request: I/O error, dev fd0, sector 0
>> end_request: I/O error, dev fd0, sector 0
>> end_request: I/O error, dev fd0, sector 0
>> end_request: I/O error, dev fd0, sector 0
>> end_request: I/O error, dev fd0, sector 0
>> end_request: I/O error, dev fd0, sector 0
>> end_request: I/O error, dev fd0, sector 0
>>
>> lsof reports no process with /dev/fd0 open so it is not clear what is
>> causing this activity. It looks like the access starts when I log in to
>> X, but doesn't stop when I log out. I'm guessing HAL or something checks
>> the floppy drive and then the kernel somehow gets stuck in a loop
>> retrying the request..
>
> That does look a bit like
> https://bugzilla.redhat.com/show_bug.cgi?id=489083 (and its duplicate
> https://bugzilla.redhat.com/show_bug.cgi?id=496586 ).

Indeed, it is.. It looks like in 2.6.29.5 the floppy module isn't being 
autoloaded and in 2.6.31-rc2 it is, which causes the DeviceKit bug to 
show up. Updating DeviceKit seems to fix the problem.

So, not a kernel regression.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/