linux-kernel - Re: [workqueue] WARNING: CPU: 0 PID: 76 at drivers/block/floppy.c:968 schedule

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20140708144632.GF4979@htj.dyndns.org>
Date:	Tue, 8 Jul 2014 10:46:32 -0400
From:	Tejun Heo <tj@...nel.org>
To:	Fengguang Wu <fengguang.wu@...el.com>
Cc:	Jet Chen <jet.chen@...el.com>, Su Tao <tao.su@...el.com>,
	Yuanhan Liu <yuanhan.liu@...el.com>, LKP <lkp@...org>,
	linux-kernel@...r.kernel.org, Jiri Kosina <jkosina@...e.cz>
Subject: Re: [workqueue] WARNING: CPU: 0 PID: 76 at
 drivers/block/floppy.c:968 schedule_bh()

On Tue, Jul 08, 2014 at 10:04:30AM -0400, Tejun Heo wrote:
...
> Hmmm... this is schedule_bh() in floppy.c complaining that the work
> item is already pending.  The cond_resched() addition by b22ce2785d97
> doesn't change the semantics around work item execution although it
> could have exposed an existing problem in the floppy driver.  I'll
> look into how this could happen.

It doesn't reproduce here and nothing really stands out to me.  It
probably involves floppy_work requeueing itself and something else
getting executed inbetween which wouldn't have happend before, but I
can't figure out what that could be and either can I follow the
control flow the driver. :)

Jiri, any ideas?

Thanks.

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