public inbox for linux-mtd@lists.infradead.org
 help / color / mirror / Atom feed
From: Artem Bityutskiy <dedekind@infradead.org>
To: Geert Uytterhoeven <Geert.Uytterhoeven@sonycom.com>
Cc: linux-mtd@lists.infradead.org
Subject: Re: Missing ioctl32 for ubi
Date: Wed, 14 Jan 2009 16:19:31 +0200	[thread overview]
Message-ID: <1231942771.5973.74.camel@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.64.0901141501240.31703@vixen.sonytel.be>

On Wed, 2009-01-14 at 15:12 +0100, Geert Uytterhoeven wrote:
> 	Hi Артём,
> 
> On Wed, 14 Jan 2009, Artem Bityutskiy wrote:
> > On Wed, 2009-01-14 at 14:48 +0100, Geert Uytterhoeven wrote:
> > > When running ubimkvol (32-bit userland) on a PS3 (ppc64), I get:
> > > 
> > > | # ubimkvol /dev/ubi0 -N test -s 200MiB
> > > | ubimkvol: error!: cannot UBI create volume
> > > |           error 22 (Invalid argument)
> > > | #
> > > 
> > > and in the kernel log:
> > > 
> > > | ioctl32(ubimkvol:2207): Unknown cmd fd(3) cmd(80986f00){t:'o';sz:152} arg(ff88a888) on /dev/ubi0
> > > 
> > > This is on 2.6.29-rc1+.
> > 
> > Hmm, frankly I have no idea what this could be. I'll look and try ti
> > figure out, though.
> 
> When running 32-bit userland on a 64-bit kernel, ioctls have to be translated.
> 
> I noticed the drivers/mtd/ubi/cdev.c:ubi_*cdev_operations structures don't have
> .compat_ioctl entries, which would handle those translations.

Oh, right. This is about implementing compat_ioctl's. I'll put this to
my TODO list and look at this unless you come up with a patch faster :-)

Thank you for noticing this.

-- 
Best regards,
Artem Bityutskiy (Битюцкий Артём)

      reply	other threads:[~2009-01-14 14:20 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14 13:48 Missing ioctl32 for ubi Geert Uytterhoeven
2009-01-14 13:57 ` Artem Bityutskiy
2009-01-14 14:12   ` Geert Uytterhoeven
2009-01-14 14:19     ` Artem Bityutskiy [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=1231942771.5973.74.camel@localhost.localdomain \
    --to=dedekind@infradead.org \
    --cc=Geert.Uytterhoeven@sonycom.com \
    --cc=linux-mtd@lists.infradead.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