From: Marcus Nutzinger <marcus@nuuz.at>
To: linux-kernel@vger.kernel.org
Cc: Greg KH <greg@kroah.com>
Subject: Re: Kernel BUG at fs/sysfs/file.c:552
Date: Sat, 12 Apr 2008 17:12:12 +0200 [thread overview]
Message-ID: <4800D14C.8020209@nuuz.at> (raw)
In-Reply-To: <20080412043139.GB13154@kroah.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
> With the nvidia driver, you're not going to get much help on this list
> :(
Well I don't like the driver either but the problem is really totally
unrealted I think..
> Hm, did you create two files with the same name?
No I only wanted to create one file on the first try, just to test the
sysfs interface. It should only give an attribute under /sys/devices,
called "writer_pid", which prints 0 or an actual PID of a process
writing to my virtual device.
I've just tried some other stuff just this minute and now it seems to
work, I get a directory under /sys/devices! Unfortunately I can't say
what the real problem was and why this kernel bug occured...
But I've another question: This directory doesn't only contain the
attribute ("writer_pid") which I've created in the code, but also a
subdirectory "power" and another attribute "uevent".. Could you explain
to me what's this all about? Are these just standard attributes which
are added to every device which registers there? (Sounds obviousely
because other directories under my /sys/devices tree contain them too..).
> Care to post your code?
I've uploaded it to http://www.nuuz.at/temp/vdd.c. I didn't want to post
the whole code here, I hope that's ok!
thanks for replying,
regards
Marcus Nutzinger
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFIANFMeEFjZ1Jaui4RAlbfAJ9XzbidhogUUMexqhuc/YPMzIaAjgCdGEtA
0NtTj7FkOfpaYdXQZklTlf0=
=FmIo
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2008-04-12 15:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-09 14:07 Kernel BUG at fs/sysfs/file.c:552 Marcus Nutzinger
2008-04-12 4:31 ` Greg KH
2008-04-12 15:12 ` Marcus Nutzinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4800D14C.8020209@nuuz.at \
--to=marcus@nuuz.at \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox