linux-kernel - Re: [take2 1/4] kevent: core files.

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: <20060801135538.GA356@2ka.mipt.ru>
Date:	Tue, 1 Aug 2006 17:55:38 +0400
From:	Evgeniy Polyakov <johnpol@....mipt.ru>
To:	James Morris <jmorris@...ei.org>
Cc:	lkml <linux-kernel@...r.kernel.org>,
	David Miller <davem@...emloft.net>,
	Ulrich Drepper <drepper@...hat.com>,
	netdev <netdev@...r.kernel.org>,
	Zach Brown <zach.brown@...cle.com>
Subject: Re: [take2 1/4] kevent: core files.

On Tue, Aug 01, 2006 at 09:46:58AM -0400, James Morris (jmorris@...ei.org) wrote:
> On Tue, 1 Aug 2006, Evgeniy Polyakov wrote:
> 
> > +	u->ready_num = 0;
> > +#ifdef CONFIG_KEVENT_USER_STAT
> > +	u->wait_num = u->im_num = u->total = 0;
> > +#endif
> 
> Generally, #ifdefs in the body of the kernel code are discouraged.  Can 
> you abstract these out as static inlines?

Yes, it is possible.
I would ask is it needed at all? It contains number of immediately fired
events (i.e. those which were ready when event was added and thus
syscall returned immediately showing that it is ready), total number of
events, which were inserted in the given queue and number of events
which were marked as ready after they were inserted.
Currently it is compilation option which ends up in printk with above
info when kevent queue is removed.
 
> - James
> -- 
> James Morris
> <jmorris@...ei.org>

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