linux-kernel - Re: [PATCH 5/5] CUSE: implement CUSE

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:	Thu, 28 Aug 2008 19:20:47 -0700
From:	Andrew Morton <akpm@...ux-foundation.org>
To:	Tejun Heo <tj@...nel.org>
Cc:	fuse-devel@...ts.sourceforge.net, miklos@...redi.hu,
	greg@...ah.com, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 5/5] CUSE: implement CUSE - Character device in
 Userspace

On Fri, 29 Aug 2008 04:09:16 +0200 Tejun Heo <tj@...nel.org> wrote:

> >> +static int __init cuse_init(void)
> >> +{
> >> +	int rc;
> >> +
> >> +	/* inherit and extend fuse_dev_operations */
> >> +	cuse_channel_fops		= fuse_dev_operations;
> >> +	cuse_channel_fops.owner		= THIS_MODULE;
> >> +	cuse_channel_fops.open		= cuse_channel_open;
> >> +	cuse_channel_fops.release	= cuse_channel_release;
> > 
> > Can't these initialisations be performed at compile-time?
> 
> Only by listing every member.  I can't think of a good way to inherit
> all and then override some in C initialization.  Hmmm.... then again,
> maybe it's better to list every member.

oop, I failed to note the struct assignment there.  The usual rule of
thumb applies: I can be safely ignored.

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