All of lore.kernel.org
 help / color / mirror / Atom feed
From: dann frazier <dannf@debian.org>
To: mark_salyzyn@adaptec.com, linux-kernel@vger.kernel.org, md@Linux.IT
Cc: 404927@bugs.debian.org, 404927-submitter@bugs.debian.org,
	debian-kernel@lists.debian.org
Subject: udev/aacraid interaction - should aacraid set 'removable'?
Date: Wed, 3 Jan 2007 08:57:50 -0700	[thread overview]
Message-ID: <20070103155749.GT13154@colo> (raw)
In-Reply-To: <20070103104951.GC11745@bongo.bofh.it>

(lkml readers: this concerns a security issue reported to debian by a
user of udev/aacraid. udev gives the aacraid devices the floppy group
because it reports block devices as 'removable'. See
http://bugs.debian.org/404927 for the entire thread).

On Wed, Jan 03, 2007 at 11:49:51AM +0100, Marco d'Itri wrote:
> On Jan 03, dann frazier <dannf@debian.org> wrote:
> 
> >  Can you elaborate on what you believe the kernel is doing
> > incorrectly? My first guess would be the setting of the removable
> > flag, but aacraid claims to be setting this to prevent partition table
> > caching - do you believe that to be an incorrect usage?
> Yes, this looks like an abuse of the interface to me.

Ok, let's ask lkml

> > It seems like there is precedence for workarounds for older kernels in
> > permissions.rules, so would it be appropriate to add an override of
> > the default floppy rule for aacraid devices for compatability even if
> > this is a kernel bug?
> There are workarounds for bugs which are going to be fixed, but looks
> like this is going to stay forever...
> Are there other drivers in this situation?

I didn't turn up any otherwise when I was grepping yesterday, but my
search terms may have been too naive. I also checked a machine I had
w/ cciss - it did not have the removable flag set.

I found a message from Mark Salyzyn from last year that suggested this
was more pervasive:
  http://www.ussg.iu.edu/hypermail/linux/kernel/0602.2/1231.html
Mark: Can you identify some of these other drivers?


-- 
dann frazier


       reply	other threads:[~2007-01-03 16:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200612290952.kBT9qg6h009021@alpha.it.teithe.gr>
     [not found] ` <20061229102959.GB10643@bongo.bofh.it>
     [not found]   ` <20070103080325.GN13154@colo>
     [not found]     ` <20070103104951.GC11745@bongo.bofh.it>
2007-01-03 15:57       ` dann frazier [this message]
2007-01-03 17:17 udev/aacraid interaction - should aacraid set 'removable'? Salyzyn, Mark
2007-01-05 20:13 ` dann frazier
  -- strict thread matches above, loose matches on Subject: below --
2007-01-05 21:15 Salyzyn, Mark

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=20070103155749.GT13154@colo \
    --to=dannf@debian.org \
    --cc=404927-submitter@bugs.debian.org \
    --cc=404927@bugs.debian.org \
    --cc=debian-kernel@lists.debian.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    --cc=md@Linux.IT \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.