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]
Date:	Sun, 4 Sep 2011 21:17:02 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	Lin Ming <mlin@...pku.edu.cn>
cc:	Dave Young <hidave.darkstar@...il.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	Andrew Morton <akpm@...ux-foundation.org>,
	<fengguang.wu@...el.com>, <linux-usb@...r.kernel.org>
Subject: Re: [BUG] D state process after unplug and umount usb disk

On Sun, 4 Sep 2011, Lin Ming wrote:

> On Sun, Sep 4, 2011 at 9:49 PM, Alan Stern <stern@...land.harvard.edu> wrote:
> >
> >> Where does this exit signal come from?
> >> Does USB interrupt handler will send kill signal to all processes
> >> accessing it when it's unplugged(by hand)?
> >
> > The USB stack does not send any signals at all unless a process
> > specifically asks for them.
> 
> How to ask?

With the USBDEVFS_DISCSIGNAL ioctl.

> I have not checked, but think umount code path will not send signal to process.

I don't think so either.

Alan Stern

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