linux-kernel - Re: [take12 0/3] kevent: Generic event handling mechanism.

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: <20060823083859.GA8936@2ka.mipt.ru>
Date:	Wed, 23 Aug 2006 12:39:00 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	Jari Sundell <sundell.software@...il.com>
Cc:	David Miller <davem@...emloft.net>, kuznet@....inr.ac.ru,
	nmiell@...cast.net, linux-kernel@...r.kernel.org,
	drepper@...hat.com, akpm@...l.org, netdev@...r.kernel.org,
	zach.brown@...cle.com, hch@...radead.org
Subject: Re: [take12 0/3] kevent: Generic event handling mechanism.

On Wed, Aug 23, 2006 at 10:22:06AM +0200, Jari Sundell (sundell.software@...il.com) wrote:
> On 8/23/06, Evgeniy Polyakov <johnpol@....mipt.ru> wrote:
> >void * in structure exported to userspace is forbidden.
> 
> Only void * I'm seeing belongs to the user, (udata) perhaps you are
> talking of something different?

Yes, exactly about it.

I put union {
	u32 a[2];
	void *b;
} 
epcially to eliminate that problem.

And I'm not that sure aboit stuff like uptr_t or how they call pointers
in userspace and kernelspace.

> >long in syscall requires wrapper in per-arch code (although that
> >workaround _is_ there, it does not mean that broken interface should
> >be used).
> >poll uses millisecods - it is perfectly ok.
> 
> The kernel is there to hide those ugly implementation details from the
> user, so I don't care that much about a workaround being required in
> some cases. More important, IMHO is consistency with the POSIX system
> calls.
> 
> I guess as long as you use usec, at least it won't be a pain to use.

Andrew suggested to use nanoseconds there in u64 variable.
I think it is ok.

> Rakshasa

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