I am writting a device driver (character, not block). User applications
communicate with it through ioctl calls. It maps our PCI cards memory
space into user space so the application can have direct access to it.
If the user applicaiton is sent a SIGABRT or SIGQUIT after it has mmap-ed
the device into its address space, the whole OS hangs. SIGKILL and SIGTERM
do not appear to have this affect. Am I supposed to do something special
in the device driver to handle these types of terminations? Whenever I
ctrl-C the user application, the release methos of the file operations
structure is called and everything packs up nicely, are the other signals
somehow different?
Regards
Greg.
-- +----------------------------------------------------+ | Do you want to know more? | | --== Greg Johnson ==-- | | HW/SW Engineer gjohnson@research.canon.com.au | | Canon Information Systems Research Australia | | 1 Thomas Holt Dr, North Ryde, NSW, 2113, Australia | | "I FLEXed my BISON and it went YACC!" - me. | +----------------------------------------------------+- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/