All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Vasily Tarasov <vtaras@openvz.org>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] diskquota: 32bit quota tools on 64bit architectures
Date: 19 Oct 2006 18:09:35 +0200	[thread overview]
Message-ID: <p73hcy0b83k.fsf@verdi.suse.de> (raw)
In-Reply-To: <200610191232.k9JCW7CF015486@vass.7ka.mipt.ru>

Vasily Tarasov <vtaras@openvz.org> writes:

> OpenVZ Linux kernel team has discovered the problem 
> with 32bit quota tools working on 64bit architectures.
> In 2.6.10 kernel sys32_quotactl() function was replaced by sys_quotactl() with
> the comment "sys_quotactl seems to be 32/64bit clean, enable it for 32bit"
> However this isn't right. Look at if_dqblk structure:
> 
> struct if_dqblk {
>         __u64 dqb_bhardlimit;
>         __u64 dqb_bsoftlimit;
>         __u64 dqb_curspace;
>         __u64 dqb_ihardlimit;
>         __u64 dqb_isoftlimit;
>         __u64 dqb_curinodes;
>         __u64 dqb_btime;
>         __u64 dqb_itime;
>         __u32 dqb_valid;
> };
> 
> For 32 bit quota tools sizeof(if_dqblk) == 0x44.
> But for 64 bit kernel its size is 0x48, 'cause of alignment!
> Thus we got a problem.
> Attached patch reintroduce sys32_quotactl() function,
> that handles the situation.

Thanks. But the code should be probably common somewhere in fs/*, not 
duplicated.

-Andi

  parent reply	other threads:[~2006-10-19 16:09 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-19 12:32 [PATCH] diskquota: 32bit quota tools on 64bit architectures Vasily Tarasov
2006-10-19 13:06 ` Alan Cox
2006-10-19 15:22 ` Randy Dunlap
2006-10-19 16:09 ` Andi Kleen [this message]
2006-10-20  6:30   ` Vasily Tarasov
2006-10-20  7:12     ` Christoph Hellwig
2006-10-20 12:21     ` Andi Kleen
2006-10-19 17:29 ` Christoph Hellwig
2006-10-20  6:10   ` Vasily Tarasov
2006-10-21 16:28     ` Arnd Bergmann
2006-10-23  2:12       ` David Chinner
2006-10-23 10:51       ` Vasily Tarasov
  -- strict thread matches above, loose matches on Subject: below --
2006-10-20  5:59 Vasily Tarasov
2006-10-25 10:03 Vasily Tarasov
2006-10-25 11:03 ` Arnd Bergmann
2006-10-25 11:25   ` Vasily Tarasov
2006-10-25 11:50     ` Arnd Bergmann
2007-06-15  8:59 Vasily Tarasov
2007-06-15  9:01 Vasily Tarasov
2007-06-15 10:03 Mikael Pettersson
2007-06-15 10:41 ` Vasily Tarasov
2007-06-15 10:43 ` Arnd Bergmann
2007-06-15 11:00   ` Vasily Tarasov
2007-06-15 14:48   ` Vasily Tarasov
2007-06-15 15:24     ` Arnd Bergmann
2007-06-18  7:41       ` Vasily Tarasov
2007-06-15 11:08 Mikael Pettersson
2007-06-18  8:21 Vasily Tarasov
2007-06-19 19:33 ` Andrew Morton
2007-06-19 20:09   ` Mikael Pettersson
2007-06-19 22:34   ` David Miller

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=p73hcy0b83k.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vtaras@openvz.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.