linux-kernel - Re: [PATCH 1/1] eventfd new tag EFD

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: <5d44edf655e193789823094d1b4301fd@suse.de>
Date:   Thu, 06 Jun 2019 22:11:57 +0200
From:   Roman Penyaev <rpenyaev@...e.de>
To:     Renzo Davoli <renzo@...unibo.it>
Cc:     Greg KH <gregkh@...uxfoundation.org>,
        Alexander Viro <viro@...iv.linux.org.uk>,
        Davide Libenzi <davidel@...ilserver.org>,
        linux-fsdevel@...r.kernel.org, linux-kernel@...r.kernel.org,
        linux-api@...r.kernel.org, linux-kernel-owner@...r.kernel.org
Subject: Re: [PATCH 1/1] eventfd new tag EFD_VPOLL: generate epoll events

Hi Renzo,

On 2019-06-03 17:00, Renzo Davoli wrote:
> Hi Roman,
> 
> 	 I sorry for the delay in my answer, but I needed to set up a minimal
> tutorial to show what I am working on and why I need a feature like the
> one I am proposing.
> 
> Please, have a look of the README.md page here:
> https://github.com/virtualsquare/vuos
> (everything can be downloaded and tested)

Is that similar to what user-mode linux does?  I mean the principle.

> I am not trying to port some tools to use user-space implemented
> stacks or device
> drivers/emulators, I am seeking to a general purpose approach.

You still intersect *each* syscall, why not to do the same for 
epoll_wait()
and replace events with correct value?  Seems you do something similar 
already
in a vu_wrap_poll.c: wo_epoll_wait(), right?

Don't get me wrong, I really want to understand whether everything 
really
looks so bad without proposed change. It seems not, because the whole 
principle
is based on intersection of each syscall, thus one more one less - it 
does not
become more clean and especially does not look like a generic purpose 
solution,
which you seek.  I may be wrong.

--
Roman