linux-kernel - Re: [PATCH] Implement uhook(call kernel func from userspace) driver

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: <20120623044105.GA32663@kroah.com>
Date:	Fri, 22 Jun 2012 21:41:05 -0700
From:	Greg KH <gregkh@...uxfoundation.org>
To:	Peiyong Feng <peiyong.feng.kernel@...il.com>
Cc:	devel@...verdev.osuosl.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] Implement uhook(call kernel func from userspace) driver

On Sat, Jun 23, 2012 at 12:18:29PM +0800, Peiyong Feng wrote:
> 2012/6/23 Greg KH <gregkh@...uxfoundation.org>:
> > On Sat, Jun 23, 2012 at 11:20:35AM +0800, Peiyong Feng wrote:
> >> Hi all,
> >>
> >> This patch implement the uhook kernel driver. Here are some ideals and
> >> explanations:
> >>
> >> 1. What is uhook
> >>
> >> uhook(userspace kernel hook) means call kernel function from
> >> userspace. That is to say, we can
> >>
> >> write a function in kernel space and call it in userspace while the
> >> kernel Image is running. For example:
> >
> > That's, um, "interesting", but is of course, nothing we can accept into
> > the main kernel tree, as I'm sure you can understand.  Otherwise, you
> > just created a few thousand undocumented system calls whose behavior
> > changes every release which is not something we can accept.
> >
> > But it is a great hack, very nicely done.  I'm sure that some people
> > will like it for debugging, although I'm not quite sure you got all of
> 
> Well, is there some other tree I can commit the patch?

What do you mean by this?

> > the user/kernel boundry conditions correct, and I know the 32/64bit
> > issues aren't handled, which you might want to clean up sometime in the
> 
> I am still working on it. The ultimate aim is that the uhook module can process
> any funciton and any data type

Good luck :)

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