All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: Linux 2.6.22 released
Date: Tue, 10 Jul 2007 14:41:50 -0400	[thread overview]
Message-ID: <4693D2EE.3020401@redhat.com> (raw)
In-Reply-To: <20070709111431.2fd3fba9@the-village.bc.nu>

On 07/09/2007 06:14 AM, Alan Cox wrote:
> Are the shortlogs useful - yes .. they catch what appear to be mistakes
> 
> Specifically: What happened to the aacraid ioctl security fix ? Did someone decide it
> wasn't needed or did it get lost somewhere on the way ?
> 
> While this looks scary the only obvious exploit cases are where the user can
> open a device level file on an AACraid. Very few people put scanners or CD
> devices on one so the actual impact is probably minimal.

I can't find that patch in any SCSI git tree.

> --- drivers/scsi/aacraid/linit.c~	2007-07-09 10:51:55.653223304 +0100
> +++ drivers/scsi/aacraid/linit.c	2007-07-09 10:51:55.653223304 +0100
> @@ -453,6 +453,8 @@
>  static int aac_ioctl(struct scsi_device *sdev, int cmd, void __user * arg)
>  {
>  	struct aac_dev *dev = (struct aac_dev *)sdev->host->hostdata;
> +	if (!capable(CAP_SYS_RAWIO))
> +		return -EPERM;

  reply	other threads:[~2007-07-10 18:41 UTC|newest]

Thread overview: 39+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-08 23:52 Linux 2.6.22 released Linus Torvalds
2007-07-09  0:19 ` Jesper Juhl
2007-07-09  1:08 ` Phil Oester
2007-07-09  6:06   ` Jan De Luyck
2007-07-09  5:00 ` Willy Tarreau
2007-07-09 10:14 ` Alan Cox
2007-07-10 18:41   ` Chuck Ebbert [this message]
2007-07-09 10:30 ` Jan Engelhardt
2007-07-09 11:45   ` Jan Engelhardt
2007-07-09 14:25 ` Michal Piotrowski
2007-07-10  7:17 ` Stefano Rivoir
2007-07-10  8:52   ` Andrew Morton
2007-07-10 15:39   ` Linus Torvalds
2007-07-10 15:59     ` Stefan Richter
2007-07-11  6:38     ` Stefano Rivoir
2007-07-11  7:05       ` Linus Torvalds
2007-07-11 10:55         ` Stephen Frost
2007-07-11 14:28           ` Stefano Rivoir
2007-07-11 12:35       ` Martin Orr
2007-07-11 14:27         ` Stefano Rivoir
2007-07-11 13:10       ` Andi Kleen
2007-07-11 17:51         ` Martin Orr
2007-07-11 18:01           ` Linus Torvalds
2007-07-11 21:00             ` Martin Orr
2007-07-11 21:29               ` Linus Torvalds
2007-07-11 22:16                 ` Andi Kleen
2007-07-11 22:33                   ` Serge Belyshev
2007-07-11 22:37                   ` Linus Torvalds
2007-07-11 22:43                     ` Andi Kleen
2007-07-11 23:56                     ` Stephen Frost
2007-07-14 15:48                   ` Martin Orr
2007-07-11 16:25       ` Theodore Tso
2007-07-10 19:39 ` Valdis.Kletnieks
2007-07-10 22:26   ` Adrian Bunk
2007-07-10 23:12     ` Stefan Richter
2007-07-11  0:00       ` Adrian Bunk
2007-07-11 10:57         ` Stefan Richter
2007-07-11  0:32       ` Valdis.Kletnieks
2007-07-11  0:01     ` david

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=4693D2EE.3020401@redhat.com \
    --to=cebbert@redhat.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    /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.