Christian Prochaska e3005266b6 vfs: no 'handle_io_response()' in regular VFS functions ... Calling 'handle_io_response()' in a regular VFS function (in contrast to a post-signal hook) can cause problems if the caller of the VFS function holds a lock which prevents the io response handler from returning. With this commit, the user of the VFS becomes responsible for unblocking threads which might be blocking after a failed 'queue_read()', 'queue_sync()' or 'write()' call. Fixes #2896		2018-08-02 14:36:43 +02:00
..
app	Convert pdf_view to a Nitpicker client	2018-06-29 10:44:57 +02:00
drivers/framebuffer/vesa	Exclude higher-level repos from strict warnings	2018-01-17 12:14:36 +01:00
lib	vfs: no 'handle_io_response()' in regular VFS functions	2018-08-02 14:36:43 +02:00
server	os: new Input::Event representation	2018-05-03 15:31:25 +02:00
test	pthread: 'pthread_join()' improvements	2018-08-02 14:36:34 +02:00