Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O

2018-11-03 Thread Scott Kitterman
On Wed, 25 Jul 2018 22:03:46 +0200 Sebastian Andrzej Siewior 
 wrote:
> On 2018-07-25 12:14:17 [+0900], Marc Dequènes (duck) wrote:
> > Quack,
> > 
> > I did not try to switch on ScanOnAccess on my production system, but with my
> > configuration, which is not that different, I do not have the problem.
> > 
> > I just tried loading Adam's configuration on another system to test the
> > ScanOnAccess, copied a clamav test file in one of the protected directory
> > and hit the problem. After that the whole machine becomes totally
> > unresponsive in a few seconds.
> 
> okay, that is good to know.
> 
> > I am using kernel 4.16.16-2~bpo9+1 on this machine.
> 
> Yeah. That "deadlock" message is only printed on Debian's kernel.

Does anyone still have this problem with 0.100.2?  It's been out awhile and 
this bug has gone quiet.

Scott K



Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O

2018-07-25 Thread Sebastian Andrzej Siewior
On 2018-07-25 12:14:17 [+0900], Marc Dequènes (duck) wrote:
> Quack,
> 
> I did not try to switch on ScanOnAccess on my production system, but with my
> configuration, which is not that different, I do not have the problem.
> 
> I just tried loading Adam's configuration on another system to test the
> ScanOnAccess, copied a clamav test file in one of the protected directory
> and hit the problem. After that the whole machine becomes totally
> unresponsive in a few seconds.

okay, that is good to know.

> I am using kernel 4.16.16-2~bpo9+1 on this machine.

Yeah. That "deadlock" message is only printed on Debian's kernel.

> \_o<
> 

Sebastian



Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O.

2018-07-25 Thread richard lucassen
On Tue, 24 Jul 2018 21:51:21 +0200
Sebastian Andrzej Siewior  wrote:

> > That looks like a different issue.  Does it still happen if you
> > remove clamav-unofficial-sigs?
> 
> This is #902899, the strace shows
> 
> |clamd: yara_exec.c:177: yr_execu
> 
> so were done here :)

Yep, that did it :) Thnx!

R.

-- 
richard lucassen
http://contact.xaq.nl/



Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O

2018-07-24 Thread duck

Quack,

On 2018-07-24 15:18, Sebastian Andrzej Siewior wrote:

On 2018-07-23 17:54:44 [+0900], Marc Dequènes wrote:

Quack,

Hi,


I just upgraded and cannot reproduce this problem. I'm not using the
ScanOnAccess feature.


just to confirm: you can not reproduce the problem.


I did not try to switch on ScanOnAccess on my production system, but 
with my configuration, which is not that different, I do not have the 
problem.


I just tried loading Adam's configuration on another system to test the 
ScanOnAccess, copied a clamav test file in one of the protected 
directory and hit the problem. After that the whole machine becomes 
totally unresponsive in a few seconds.


Jul 25 11:35:14 elwing kernel: [3112805.231170] clamd (13840): Using 
fanotify permission checks may lead to deadlock; tainting kernel
Jul 25 11:36:24 elwing kernel: [3112875.408154] kauditd_printk_skb: 7 
callbacks suppressed
Jul 25 11:36:24 elwing kernel: [3112875.408155] audit: type=1400 
audit(1532486184.205:794): apparmor="ALLOWED" operation="capable" 
profile="/usr/sbin/clamd" pid=13564 comm="clamd" capability=2  
capname="dac_read_search"
Jul 25 11:38:37 elwing kernel: [3113009.136000] INFO: task nfsd:20284 
blocked for more than 120 seconds.


I am using kernel 4.16.16-2~bpo9+1 on this machine.

\_o<

--
Marc Dequènes



Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O.

2018-07-24 Thread richard lucassen
On Tue, 24 Jul 2018 08:19:15 +0200
Sebastian Andrzej Siewior  wrote:

> Is the kernel complaining about something like in the other report
> where it claimed something about a deadlock?

No, no words like fanotify, deadlock or blocked appear in the logs.

I blocked and upgraded one of the (production) servers. After
upgrade clamd is running but as soon as a mail is received, it exits. I
ran an "strace -f -p " on a running clamd and sent a mail. The
output is here:

http://tmp.xaq.nl/clamd.strace

$ dpkg --get-selections | grep clam
clamav  install
clamav-base install
clamav-daemon   install
clamav-freshclaminstall
libclamav7:i386 install
libclamunrar7   install

plus a vanilla install of clamav-unofficial-sigs.

R.

-- 
richard lucassen
http://contact.xaq.nl/



Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O

2018-07-24 Thread Sebastian Andrzej Siewior
On 2018-07-23 17:54:44 [+0900], Marc Dequènes wrote:
> Quack,
Hi,

> I just upgraded and cannot reproduce this problem. I'm not using the
> ScanOnAccess feature.

just to confirm: you can not reproduce the problem.

> Follows collected config info.
> \_o<

Sebastian



Bug#904111: [Pkg-clamav-devel] Bug#904111: clamav-daemon causing deadlocks/blocking I/O.

2018-07-24 Thread Sebastian Andrzej Siewior
On 2018-07-23 18:26:04 [+0200], Richard Lucassen wrote:
> Same here (6 Postfix front-end servers), non-systemd, non-GUI system
> running Debian Stretch. Downgrading to 0.99 is a workaround.
> ScanOnAccess is set to false.

Is the kernel complaining about something like in the other report where
it claimed something about a deadlock?

> R.

Sebastian