From: Joseph C. <jos...@gm...> - 2005-05-20 22:12:51
|
I am reworking the app and env so I don't need unionfs I will let you all know in a day or 2 on that one. On 5/20/05, Joseph Cohen <jos...@gm...> wrote: > Sorry forgot to CC the list >=20 > On 5/20/05, Joseph Cohen <jos...@gm...> wrote: > > Thanks for the reply. The arch is a AMD64 with Gentoo Linux. I > > believed the problem to be the fuse since the very 1st error was > > caused by my application which is using fuse also. I was thinking that > > maybe the error was being caused since I have had to many filesystems > > stacked on it. This is again just for playing around and learning the > > fuse arch but what my stack was some sshfs mounts and some samba > > mounts that were then combined with unionfs and then combined with > > some mount binds then with my guxfs app. > > > > Doesn't unionfs use fuse also? > > > > The other reason why I was thinking it was in fuse was because with > > out my app the problem never occurs but with my app all I need to do > > is put some decent IO on it then it breaks like this, otherwise with > > out my ip I can keep the io channel and cpu maxed for several hours > > without this problem. > > > > On 5/20/05, Miklos Szeredi <mi...@sz...> wrote: > > > > Hi so I've tried to make my 1st fuse driver but noticed I am able t= o > > > > crash my kernel which leads me to the question of how can I do this > > > > with a userland application? > > > > > > You shouldn't be able to. > > > > > > > But anyways I think the bug is in the fuse driver or library since = I > > > > am only doing a little modification to the example app fusexmp. All > > > > I'm doing is a simple rot13 to the filenames to help me learn fuse.= I > > > > have checked, double checked and even had others check my code for = C > > > > errors and such. Here is what my kernel log reports: > > > > > > > > [kernel] Unable to handle kernel NULL pointer dereference at > > > > 0000000000000021 RIP: > > > > > > > > > > > > Here is my dmesg, as you can tell my simple fuse app is guxfs.64 an= d > > > > I'm also stacking unionfs to it to prevent me from screwing up my l= ive > > > > system. Let me know what you think: > > > > > > The Oops is in unionfs, which may mean anything. It's probably a bad > > > interaction between FUSE and unionfs. > > > > > > What's the architecture? The Oops output seems strange to me. > > > > > > Can you please try if you can reporoduce it without unionfs? > > > > > > Thanks, > > > Miklos > > > > > > |