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: <ddef1cf.2c9460e3.4b3f8fd5.c10cd@o2.pl>
Date:	Sat, 02 Jan 2010 19:26:29 +0100
From:	Bartłomiej Zimoń <uzi18@...pl>
To:	Andy Walls <awalls@...ix.net>,
	Daniel Borkmann <danborkmann@...glemail.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [suspend/resume] Re: userspace notification from module

Dnia 2 stycznia 2010 16:56 	Daniel Borkmann <danborkmann@...glemail.com> napisał(a):
> 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?
> 

Just need as fast as possible solution and on the other hand acceptable for kernel sources.
Usually programs needs just to disconnect something or set one flag.
Even if program will have no time for this it could be enough just to send this precious info.

Best regards.
Barłomiej Zimoń
PLD Linux, Kadu Team
--
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/