Hi Sebastian, On 08.11.2015 15:06, Sebastian Andrzej Siewior wrote: > That said I hacked up something that is half way done i.e. not complete > or tested. I used nftw() and a mutex() since the function passed to > nftw() can't have a private argument and I kind of need it for struct > onas_ht *ht. And after seeing that thing above I was thinking about > pulling in fts() from glibc to remain bug compatible with upstream. And > then I was thinking about stable + oldstable and the amount of non-upstream > code we are pushing there I was thinking: > HEY! What about disabling FANOTIFY which disables this feature > and we don't have to worry about this and we enable it once > glibc 2.23 hits unstable? > > Any thoughts on this? We should react soon I think since we need to pass > the new queue.
I think it would be better to disable LFS instead: it is not enabled upstream and we only recently enabled it. Maybe filing a clamav upstream bug about this problem might be the way to go? Perhaps they can help adapting the code to nftw. Best regards, Andreas _______________________________________________ Pkg-clamav-devel mailing list [email protected] http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-clamav-devel
