mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: ebiederm@xmission.com (Eric W. Biederman)
To: Seokmann Ju <sju@lsil.com>
Cc: Andrew Morton <akpm@osdl.org>,
	James Bottomley <James.Bottomley@SteelEye.com>,
	linux-scsi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/1] scsi : megaraid_{mm, mbox} : irq data type fix
Date: Thu, 10 Aug 2006 11:34:40 -0600	[thread overview]
Message-ID: <m1vep01olr.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <1155228887.6698.7.camel@dhcp-65-957.se.lsil.com> (Seokmann Ju's message of "Thu, 10 Aug 2006 12:54:47 -0400")

Seokmann Ju <sju@lsil.com> writes:

> This patch fixes incorrect irq data type in the driver which led driver
> initialization failure in some cases.
> The problem was reported by Eric @. Biederman <ebiederm@xmission.com>.

We have a race going on, I read your first message then this one pops up.
But I will reply again for wider distribution.

Nacked-by: Eric Biederman.

The problem is that struct mcontroller is exported to user space
and is a packed structure so it has no free bytes.

Therefore you will break user space when you add bytes in the
middle of your structure.  We can't do that.  You either need
to add an extra field at the end (while keeping the structure size the
same) or you need to add a new ioctl that gets this information correct,
or you need to give up entirely on the idea of exporting the irq
number to user space this way.

What you need not to do is break the kernel<->user space ABI.  That
is just confusing and couples the kernel and user space in unpleasant
ways.

I believe struct mraid_hba_info has the same problem but I could not
see where it was exported to user space.

Eric

      parent reply	other threads:[~2006-08-10 17:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-10 16:54 Seokmann Ju
2006-08-10 17:32 ` James Bottomley
2006-08-10 17:34 ` Eric W. Biederman [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=m1vep01olr.fsf@ebiederm.dsl.xmission.com \
    --to=ebiederm@xmission.com \
    --cc=James.Bottomley@SteelEye.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=sju@lsil.com \
    /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

all inboxes | Powered by JetHome®