linux-kernel - Re: [suspend/resume] Re: userspace notification from module

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]

Message-ID: <6f52f5b81001020756i73fbb137if1af8ac8b306f6ba@mail.gmail.com>
Date:	Sat, 2 Jan 2010 16:56:15 +0100
From:	Daniel Borkmann <danborkmann@...glemail.com>
To:	Andy Walls <awalls@...ix.net>
Cc:	Bartłomiej Zimoń <uzi18@...pl>,
	linux-kernel@...r.kernel.org
Subject: Re: [suspend/resume] Re: userspace notification from module

Hi Andy,

2010/1/2 Andy Walls <awalls@...ix.net>:
> Why not:
>
> a. write a module that implements a device node that supports poll(),
> and
>
> b. have a user space process select() on the fd for read or exception
> notification
>
> ?

This is, of course, another possible solution that is more "cleaner"
than the one with the signals.
Then, your userspace program would have another thread polling for the
device node. Question is which timeout would be appropriate to be "CPU
friendly" and to keep notification latency short?

Cheers,
Daniel
--
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/