linux-kernel - [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]

Date:	Sat, 02 Jan 2010 15:27:12 +0100
From:	Bartłomiej Zimoń <uzi18@...pl>
To:	linux-kernel@...r.kernel.org
Subject: [suspend/resume] Re: userspace notification from module

Dnia 2 stycznia 2010 15:04 	Daniel Borkmann <danborkmann@...glemail.com> napisał(a):
> Hi Bartłomiej,
> 
> Bartłomiej Zimoń wrote:
> > Dnia 2 stycznia 2010 13:36 	Daniel Borkmann <llug.dan@...glemail.com> napisał(a):
> > I will explain more what i'm going to do.
> > The idea is simple. Kernel before suspend/resume sends notification to 
> > registered kernel objects. So i have written small module to register
> > there and want now pass these data to /dev/file. It is 1byte so not a big deal.
> > 
> > I'm searching now for notification about new byte in buffer, as it is almost 
> > clear for async: http://www.xml.com/ldd/chapter/book/ch05.html#t4
> > but for sync still haven't find.
> 
> This sounds very interesting... a "hack" could be the following:
> 
> Register your pids to the kernel module, e.g. via ioctl, and if the
> (intra-kernel) notification will be delivered to your module you just
> send a signal to your registered processes via kill_proc_info(). Guess
> this is at least better than polling a file or sth similar.
> 
> I guess netlink could be the "cleaner" solution, but with more overhead?!
> 

This looks like more simple and could be good, after all i think about sending this 
module here to add to kernel. So if this solution could be ok i will start to code this part.

Question is now what signal to choose to not terminate process and to be compatible 
with rest of Linux kernel?

Best regards
Bartłomiej Zimoń

--
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/