On Mon, Jul 21, 2014 at 08:47:16PM +0800, pp wrote: > As reuse the cdev may cause panic. After we unregister the tty device, we may > use tty_hangup() o > other similar function to send a signal(SIGHUP) to process which has opend > our device. But that > not succeed if the process couldn't get the signal. for example, a process > forked > but his parent quited never get SIGHUP. > > Here is our scence. > tty driver register its device and init the cdevs, then process "A" open one > cdev. > tty driver unregister its device and cdev_del the cdevs, call tty_hangup to > (S)send signal SIGHUP to process A. > But that step(S) fails.
How can that fail? What driver does this fail for? > tty driver register its device and (D)init the cdevs again. What driver does this with an "old" device, it should have created a new one, otherwise, as you have pointed out, it's a bug. thanks, greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
