linux-kernel - Re: raw1394 problems galore FIXED!!!!!

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: <453440C7.2060800@verizon.net>
Date:	Mon, 16 Oct 2006 22:32:39 -0400
From:	Gene Heskett <gene.heskett@...izon.net>
To:	For users of Fedora Core releases <fedora-list@...hat.com>
Cc:	Stefan Richter <stefanr@...6.in-berlin.de>,
	linux-kernel@...r.kernel.org, linux1394-user@...ts.sourceforge.net
Subject: Re: raw1394 problems galore FIXED!!!!!

[...]

This is going to sound rather silly, because I did try a couple of 
earlier kernels before I started posting about this problem.

Tonight, I saw that kernel-2.6.18-1.2200.fc5.i686 was available, along 
with the matching kmod-ndiswrapper pieces and kmod-ntfs in versions 
2.6.18-1.2200.fc5 were available, so I installed them and rebooted.

Now kino-0.8 works sortof, wants to crash.
And kino-0.9.2 apparently works flawlessly, as does dvcont.

Looking into the logs, I see this during the boot:
Oct 16 20:20:29 diablo kernel: ohci1394: fw-host0: OHCI-1394 1.1 (PCI): 
IRQ=[10]  MMIO=[c0209000-c02097ff]  Max Packet=[2048]  IR/IT contexts=[
4/8]
Oct 16 20:20:29 diablo kernel: audit(1161044396.750:4): avc:  denied  { 
getattr } for  pid=1310 comm="pam_console_app" name="raw1394" dev=tmpfs
  ino=4494 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255 
tcontext=system_u:object_r:device_t:s0 tclass=chr_file
Oct 16 20:20:29 diablo kernel: audit(1161044396.750:5): avc:  denied  { 
setattr } for  pid=1310 comm="pam_console_app" name="raw1394" dev=tmpfs
  ino=4494 scontext=system_u:system_r:pam_console_t:s0-s0:c0.c255 
tcontext=system_u:object_r:device_t:s0 tclass=chr_file

And I believe the camera was plugged in and powered up during the boot 
as there are no further messages in the log & I've been playing with a 
very wide grin on my face for about half an hour with it.

So it was a kernel problem all along!

Just one question here.  Am I the only idiot that actually wants to do 
work on linux?  On second thought, I might not like the answer :-)

Anyway, end of thread, till the next time :)

-- 
Cheers, Gene

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