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>] [day] [month] [year] [list]
Message-ID: <3aadbf9e0708051121m3ce8e044g104f58c17466eb60@mail.gmail.com>
Date:	Mon, 6 Aug 2007 02:21:55 +0800
From:	"Othello Reversi" <othello.reversi@...glemail.com>
To:	linux-kernel@...r.kernel.org
Subject: Calling add_disk() from a work_queue item

Hi List,

    I would like to know why calling add_disk() from a kernel thread
which is running from a work_queue would cause the work item to block
with the "D" (disk wait) state at best under kernel 2.6.17 and cause a
hard-lockup on kernel 2.6.22.1?

    If I    recall correctly, work items running on the work_queue are
allowed to sleep, and add_disk() is known to sleep.  Did I miss out
some details such as a lock I have to acquire?

    Hope to hear a reply soon.

Regards,
Othello

PS: Would like to be CC'ed comments and replies.
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ