On Wed, 25 Jul 2018 22:03:46 +0200 Sebastian Andrzej Siewior <sebast...@breakpoint.cc> 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