group.of.nepali.translators team mailing list archive

[ Christian Ehrhardt  <1582318@xxxxxxxxxxxxxxxxxx>]

Hi Helge,
You are right, the issue exists there.
But IMHO the backport has as SRU to Xenial has quite some regression risk and actually low gain.
Let me outline why I think so:

Looking at people that:
1. had amavisd running without - nvidia nvcc not installed
   => Things working fine
2. had amavisd running without - nvidia nvcc installed
   => amavisd is broken by this bug, but then can be fixed with a conscious config file change
3. had amavisd running without - norman AV nvcc installed
   => Things working fine WITH norman AV

Now if we would SRU something we would:
- not help #1 being not affected
- #2 was broken, so we fix something unused (and flagging all mails can be a thing as well since https://xkcd.com/1172/)
- for those people in #3 we would break a valid working setup

It is sort of unfortunate, but at least in my limited POV the risk actually outweighs the gain in this case.
Also setting up "new" Xenial should no more be a major tasks these days with Bionic being available for quite a while now.

just my 2 cents, feel free to discuss if you think otherwise.

** Also affects: amavisd-new (Ubuntu Xenial)
   Importance: Undecided
       Status: New

** Changed in: amavisd-new (Ubuntu Xenial)
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of नेपाली
भाषा समायोजकहरुको समूह, which is subscribed to Xenial.
Matching subscriptions: Ubuntu 16.04 Bugs
https://bugs.launchpad.net/bugs/1582318

Title:
  amavis virus check fails when nvidia CUDA is on the same system

Status in amavisd-new:
  Fix Released
Status in amavisd-new package in Ubuntu:
  Fix Released
Status in amavisd-new source package in Xenial:
  Won't Fix

Bug description:
  Amavis incorrectly assumes that /usr/bin/nvcc is the "Norman virus
  control" executable, and attempts to use it to virus check incoming
  emails.

  In systems with the NVIDIA CUDA compiler installed, the nvcc
  executable is actually the CUDA compiler, and so exits with a non-zero
  (exit) state every time amavis attempts to execute it on email
  traffic.

  This behavior results in all email traffic being marked (and
  quarantined) by amavis as containing a virus whenever NVIDIA CUDA is
  installed on the same system as amavisd-new.

  The increasing use of gpu acceleration for speeding up and
  multithreading particular server processing tasks means that in the
  future more servers may experience this problem as they have NVIDIA
  CUDA installed on them.

  I believe that amavis should verify that nvcc is the Norman virus
  control executable prior to attempting to use it as a virus check.

  A workaround for this bug on current ubuntu systems is to modify the default /etc/amavis/conf.d/15-av_scanners file and comment out the following three lines:
    ['Norman Virus Control v5 / Linux', 'nvcc',
      '-c -l:0 -s -u -temp:$TEMPBASE {}', [0,10,11], [1,2,14],
      qr/(?i).* virus in .* -> \'(.+)\'/m ],

  ---------------
  lsb_release -rd
  Description:	Ubuntu 16.04 LTS
  Release:	16.04

  ---------------
  apt-cache policy amavisd-new
  amavisd-new:
    Installed: 1:2.10.1-2ubuntu1
    Candidate: 1:2.10.1-2ubuntu1
    Version table:
   *** 1:2.10.1-2ubuntu1 500
          500 http://au.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
          500 http://au.archive.ubuntu.com/ubuntu xenial/main i386 Packages
          100 /var/lib/dpkg/status

  ProblemType: Bug
  DistroRelease: Ubuntu 16.04
  Package: amavisd-new 1:2.10.1-2ubuntu1
  ProcVersionSignature: Ubuntu 4.4.0-22.39-generic 4.4.8
  Uname: Linux 4.4.0-22-generic x86_64
  NonfreeKernelModules: nvidia_uvm nvidia_modeset nvidia
  ApportVersion: 2.20.1-0ubuntu2
  Architecture: amd64
  CurrentDesktop: GNOME
  Date: Tue May 17 00:11:34 2016
  PackageArchitecture: all
  SourcePackage: amavisd-new
  UpgradeStatus: Upgraded to xenial on 2016-04-27 (19 days ago)
  modified.conffile..etc.amavis.conf.d.05-node_id: [modified]
  modified.conffile..etc.amavis.conf.d.15-av_scanners: [modified]
  modified.conffile..etc.amavis.conf.d.15-content_filter_mode: [modified]
  modified.conffile..etc.amavis.conf.d.20-debian_defaults: [modified]
  modified.conffile..etc.amavis.conf.d.50-user: [modified]
  mtime.conffile..etc.amavis.conf.d.05-node_id: 2008-07-24T09:24:40
  mtime.conffile..etc.amavis.conf.d.15-av_scanners: 2016-05-05T16:49:24.747435
  mtime.conffile..etc.amavis.conf.d.15-content_filter_mode: 2008-07-24T09:26:06
  mtime.conffile..etc.amavis.conf.d.20-debian_defaults: 2016-05-05T16:43:45.387437
  mtime.conffile..etc.amavis.conf.d.50-user: 2008-07-24T09:25:35

To manage notifications about this bug go to:
https://bugs.launchpad.net/amavisd-new/+bug/1582318/+subscriptions