mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: xypron.glpk@gmx.de
Cc: eparis@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] Enable fanotify API by default.
Date: Sat, 15 Jun 2013 11:00:14 -0700	[thread overview]
Message-ID: <20130615180014.GA30406@kroah.com> (raw)
In-Reply-To: <1371313047-17753-1-git-send-email-xypron.glpk@gmx.de>

On Sat, Jun 15, 2013 at 06:17:27PM +0200, xypron.glpk@gmx.de wrote:
> From: Heinrich Schuchardt <xypron.glpk@gmx.de>
> 
> The fanotify interface is the basis for on access malware detection
> in the Linux kernel. The development of a prior solution (DazukoFS)
> has been stopped therefore.
> 
> Both free (ClamAV) as well as commercial viurs scanners (Sophos
> Anti-Virus, AVG) using this interface exist.
> 
> Since kernel version 3.8.0 the implementationof the fanotify inter-
> face is errorfree enough to be used on a productive system.
> Personally I have been using it for virus scanning on multiple
> systems for several months without issues while a developing a
> wrapper around ClamAV, see
> https://github.com/xypron/skyldav
> 
> A large scale usage of the fanotify interface can only expected if
> the API is enabled by default.

We only set options to 'default Y' if they are needed in order to keep
your machine working properly.  Now that this option has been around for
a while, changing the default will not affect anyone's machines, as they
will not see that change.

Why not just work with the distros to enable fanotify, that's where you
need this enabled, not here.  Those are the majority of users, not
kernel developers who pick their own kernel configurations.

thanks,

greg k-h

      reply	other threads:[~2013-06-15 17:59 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-15 16:17 xypron.glpk
2013-06-15 18:00 ` Greg KH [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130615180014.GA30406@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=eparis@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=xypron.glpk@gmx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome