The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: weigelt@metux.de
Cc: linux kernel list <linux-kernel@vger.kernel.org>
Subject: Re: scanner interface proposal was: [TALPA] Intro to a linux interface for on access scanning (fwd)
Date: Mon, 1 Dec 2008 10:03:50 +0000	[thread overview]
Message-ID: <20081201100350.34af705e@lxorguk.ukuu.org.uk> (raw)
In-Reply-To: <20081201005142.GA27387@nibiru.local>

On Mon, 1 Dec 2008 01:51:42 +0100
Enrico Weigelt <weigelt@metux.de> wrote:

> * Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> > > Fine. Why not just putting this into a userland filesystem ?
> > 
> > 1. Performance
> 
> Does it really hurt so bad, compared with all actual AV stuff ?
> It has to go to userland anyway, in case you don't intend to 
> put the scanner into the kernel ;-o

That depends on the scanning and what you are using it for - at least
part of the interest is in asynchronous indexing systems in which case
the answer appears to be no, the scanner doesn't trash your performance.
> 
> > 2. Networked file systems
> 
> What's the problem ?
> (btw: 9P already *IS* an network filesystem ;-P)

Try 9P with an NFS backing store. Try a cluster file system.

> > 3. Ioctls
> 
> Ah, just forgot a while that this crap still exists ;-o
> 
> BUT: do the affected dirs have to contain devices ? 
> Is there any point for pulling /dev through the AV scanner ?

Lots of ioctls apply to files. Please think about what is involved rather
than just assuming.

      parent reply	other threads:[~2008-12-01 10:03 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-18  1:25 scanner interface proposal was: [TALPA] Intro to a linux interface for on access scanning (fwd) david
2008-08-18 10:30 ` [malware-list] " tvrtko.ursulin
2008-08-18 11:44   ` david
2008-08-18 12:18     ` tvrtko.ursulin
2008-08-18 12:34       ` david
2008-11-23 22:37 ` Enrico Weigelt
2008-11-23 23:03   ` Alan Cox
2008-12-01  0:51     ` Enrico Weigelt
2008-12-01  5:22       ` david
2008-12-01 10:03       ` Alan Cox [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=20081201100350.34af705e@lxorguk.ukuu.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=weigelt@metux.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