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]

Message-Id: <E1L3o2v-0001Nz-Oi@pomaz-ex.szeredi.hu>
Date:	Sat, 22 Nov 2008 09:40:53 +0100
From:	Miklos Szeredi <miklos@...redi.hu>
To:	tj@...nel.org
CC:	miklos@...redi.hu, linux-kernel@...r.kernel.org,
	fuse-devel@...ts.sourceforge.net, akpm@...ux-foundation.org,
	greg@...ah.com
Subject: Re: [PATCH 5/5] CUSE: implement CUSE - Character device in Userspace

On Sat, 22 Nov 2008, Tejun Heo wrote:
> Miklos Szeredi wrote:
> > On Thu, 20 Nov 2008, Tejun Heo wrote:
> >> diff --git a/include/linux/miscdevice.h b/include/linux/miscdevice.h
> >> index 0be9245..d4dcca8 100644
> >> --- a/include/linux/miscdevice.h
> >> +++ b/include/linux/miscdevice.h
> >> @@ -28,6 +28,7 @@
> >>  #define MPT_MINOR		220
> >>  #define	HPET_MINOR		228
> >>  #define FUSE_MINOR		229
> >> +#define CUSE_MINOR		230
> > 
> > This doesn't work: device numbers have to be allocated by LANANA.
> 
> My last attempt at LANANA for extended devt didn't get me anywhere and
> I'm not sure LANANA is handling miscdevice minors at all.

Back then I did get the fuse device registered in LANANA database
(http://www.lanana.org/docs/device-list/devices-2.6+.txt)

>   If you go
> through the tree, there are quite a few duplicate allocations including
> FUSE_MINOR.  At any rate, we can definitely try LANANA.

Ugh, I suppose that's my fault for not putting the definition in
miscdevice.h (though apparently the duplicates didn't do so either).

Thanks,
Miklos
--
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/