I'll do that tomorrow. But yes I agree it shouldn't trigger that error, which
was the other reason I posted it.
"Török Edvin" <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
To
"ClamAV
users ML" <clamav-users@lists.clamav.net>
09/24/2007 02:02 PM
cc
Subject
Please respond to Re:
[Clamav-users] Scanning hardware devices fails
ClamAV users ML <clamav-users@lists.clamav.net>
On 9/24/07, Christopher X. Candreva <[EMAIL PROTECTED]> wrote:
> On Mon, 24 Sep 2007, [EMAIL PROTECTED] wrote:
>
> > after a while I get this:
> >
> > /sys/devices/pci0000:00/0000:00:06.0/config: OK
> > /sys/devices/pci0000:00/0000:00:06.0/0000:17:00.0/host1/sfp: OK
> > /sys/devices/pci0000:00/0000:00:06.0/0000:17:00.0/host1/vpd: Empty file
> > /sys/devices/pci0000:00/0000:00:06.0/0000:17:00.0/host1/optrom_ctl: Empty
> > file
> > /sys/devices/pci0000:00/0000:00:06.0/0000:17:00.0/host1/optrom: OK
> > *** stack smashing detected ***: clamscan terminated
>
> > Should I be excluding /sys/devices/pci0000.00:00 ? I don't want to exclude
> > anything but I consistently get the error when I scan this dir.
>
> You should be excluding /sys and /dev at least, probably /proc too. You are
> scanning your hardware devices.
Strange things can happen if you scan your /sys (for a good reason), look in
your dmesg for the cause.
However that is not supposed to make clamscan crash with a stack error!
I would be interested to know if clamscan got killed because it
scanned some "forbidden" file in /sys, or because of something else.
Please run 'strace clamscan -r /sys/devices/pci0000:00', and
'clamscan --debug -r /sys/devices/pci0000:00', and attach the output
to a bugreport. Mark the bug as minor severity.
Thanks,
Edwin
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
_______________________________________________
Help us build a comprehensive ClamAV guide: visit http://wiki.clamav.net
http://lurker.clamav.net/list/clamav-users.html
