public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Mark Haverkamp <markh@osdl.org>
Cc: Christoph Hellwig <hch@infradead.org>,
	James Bottomley <James.Bottomley@steeleye.com>,
	linux-scsi <linux-scsi@vger.kernel.org>,
	Mark Salyzyn <mark_salyzyn@adaptec.com>
Subject: Re: [PATCH] aacraid 32/64 ioctl support (update)
Date: Wed, 16 Jun 2004 18:19:24 +0100	[thread overview]
Message-ID: <20040616171924.GA15925@infradead.org> (raw)
In-Reply-To: <1087405920.13488.82.camel@markh1.pdx.osdl.net>

On Wed, Jun 16, 2004 at 10:12:00AM -0700, Mark Haverkamp wrote:
> On Wed, 2004-06-16 at 09:02, Christoph Hellwig wrote:
> > On Wed, Jun 16, 2004 at 05:01:07PM +0100, Christoph Hellwig wrote:
> > > > +		register_ioctl32_conversion(2131, NULL);
> > > > +#	endif
> > > 
> > > #ifdef please and no additional indentation inside the ifdef please.
> > 
> > btw, what's ioctl2131?  It doesn't seem to be implemented, so no need to translate it.
> 
> Christoph,
> 
> I think that I have addressed all of your comments in this patch.
> 
> removed != 0
> fixed indentation
> fixed include order
> fixed ifdefs
> used compat_alloc_user_space

Although the compat_alloc_user_space implementations I looked at don't fail I
think a check for NULL wouldn't hurt.

> I checked, and 2131 is implemented in aachba.c and looks like it gets
> container info.

Hmm, could we please get a symbolic name for that from adaptec?

> +#ifdef CONFIG_COMPAT
> +/* 
> + * Promote 32 bit apps that call get_next_adapter_fib_ioctl to 64 bit version 
> + */
> +int aac_get_next_adapter_fib_ioctl(unsigned int fd, unsigned int cmd, 
> +		unsigned long arg, struct file *file)

hmm, should probably be static.

> +{
> +	struct fib_ioctl *f;
> +	int retval;
> +
> +	f = compat_alloc_user_space(sizeof(*f));
> +	memset (f, 0, sizeof(*f));

superflous space before the opening brace here.

> +	if (copy_from_user((void *)f, (void *)arg, 
> +				sizeof(struct fib_ioctl) - sizeof(u32)))
> +		return -EFAULT;
> +	retval = sys_ioctl(fd, cmd, (unsigned long)f);
> +	return retval;

No need for retval here.


  reply	other threads:[~2004-06-16 17:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-16 15:52 [PATCH] aacraid 32/64 ioctl support (update) Mark Haverkamp
2004-06-16 16:01 ` Christoph Hellwig
2004-06-16 16:02   ` Christoph Hellwig
2004-06-16 17:12     ` Mark Haverkamp
2004-06-16 17:19       ` Christoph Hellwig [this message]
2004-06-16 17:51         ` Mark Haverkamp
2004-06-16 17:53           ` Christoph Hellwig
2004-06-16 17:52             ` David S. Miller
2004-06-16 18:23         ` Mark Haverkamp

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=20040616171924.GA15925@infradead.org \
    --to=hch@infradead.org \
    --cc=James.Bottomley@steeleye.com \
    --cc=linux-scsi@vger.kernel.org \
    --cc=mark_salyzyn@adaptec.com \
    --cc=markh@osdl.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox