linux-kernel - Re: WARNING in 2.6.25-07422-gb66e1f1

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] [thread-next>] [day] [month] [year] [list]

Message-ID: <481DB3F3.5080102@gmail.com>
Date:	Sun, 04 May 2008 15:02:43 +0200
From:	Jacek Luczak <difrost.kernel@...il.com>
To:	Prakash Punnoor <prakash@...noor.de>
CC:	Linux Kernel list <linux-kernel@...r.kernel.org>,
	Jens Axboe <jens.axboe@...cle.com>, neilb@...e.de
Subject: Re: WARNING in 2.6.25-07422-gb66e1f1

Hi,

I've CC:-ed few guys which may help.

Prakash Punnoor pisze:
> Hi, I got this on boot:
>
> usb 2-1.3: new full speed USB device using ehci_hcd and address 3
> usb 2-1.3: configuration #1 chosen from 1 choice
> Clocksource tsc unstable (delta = -117343945 ns)
> ------------[ cut here ]------------
> WARNING: at include/linux/blkdev.h:443 blk_remove_plug+0x7d/0x90()
> Modules linked in: kvm_amd kvm powernow_k8 ehci_hcd ohci_hcd usbcore forcedeth
> Pid: 1681, comm: fsck.ext3 Not tainted 2.6.25-07422-gb66e1f1-dirty #74
> 
> Call Trace:
>  [<ffffffff80236354>] warn_on_slowpath+0x64/0xa0
>  [<ffffffff803b6a04>] generic_make_request+0x194/0x250
>  [<ffffffff803b82e7>] submit_bio+0x97/0x140
>  [<ffffffff803b756d>] blk_remove_plug+0x7d/0x90
>  [<ffffffff8049d4d4>] raid5_unplug_device+0x44/0x110
>  [<ffffffff802666ce>] sync_page+0x2e/0x50
>  [<ffffffff805a0985>] __wait_on_bit+0x65/0x90
>  [<ffffffff802669c8>] wait_on_page_bit+0x78/0x80
>  [<ffffffff8024bb70>] wake_bit_function+0x0/0x40
>  [<ffffffff8026f1ba>] pagevec_lookup_tag+0x1a/0x30
>  [<ffffffff80266fbd>] wait_on_page_writeback_range+0xbd/0x130
>  [<ffffffff8026d5e0>] do_writepages+0x20/0x40
>  [<ffffffff802670a2>] __filemap_fdatawrite_range+0x52/0x60
>  [<ffffffff80267334>] filemap_write_and_wait+0x44/0x50
>  [<ffffffff802bd968>] __blkdev_put+0x148/0x1b0
>  [<ffffffff80293441>] __fput+0xb1/0x1c0
>  [<ffffffff80290178>] filp_close+0x48/0x80
>  [<ffffffff80291a1f>] sys_close+0x9f/0x110
>  [<ffffffff8020c42b>] system_call_after_swapgs+0x7b/0x80
> 
> ---[ end trace 94c0787a2e4d19eb ]---
> EXT3 FS on md1, internal journal
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS on md2, internal journal
> EXT3-fs: mounted filesystem with writeback data mode.
> kjournald starting.  Commit interval 5 seconds
> EXT3 FS on md3, internal journal
> EXT3-fs: mounted filesystem with writeback data mode.
> eth0: no link during initialization.
> r8169: eth1: link up
> r8169: eth1: link up
> NFSD: Using /var/lib/nfs/v4recovery as the NFSv4 state recovery directory
> NFSD: starting 90-second grace period

Is this problem reproducible?

Trace is printed by last change from Jens on Apr-29 (commit:
7663c1e2792a9662b23dec6e19bfcd3d55360b8f, Improve queue_is_locked()), but it
looks like raid5_unplug_device() is called during EXT3 check on md0 [why?].

-Jacek
--
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/