From: Arnd Bergmann <arnd@arndb.de>
To: Vasily Tarasov <vtaras@openvz.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>, Jan Kara <jack@suse.cz>,
Alan Cox <alan@lxorguk.ukuu.org.uk>, Roman Kagan <rkagan@sw.ru>,
Randy Dunlap <rdunlap@xenotime.net>,
Dmitry Mishin <dim@openvz.org>, Andi Kleen <ak@suse.de>,
Vasily Averin <vvs@sw.ru>, Christoph Hellwig <hch@infradead.org>,
Kirill Korotaev <dev@openvz.org>,
OpenVZ Developers List <devel@openvz.org>
Subject: Re: [PATCH] diskquota: 32bit quota tools on 64bit architectures
Date: Wed, 25 Oct 2006 13:03:48 +0200 [thread overview]
Message-ID: <200610251303.50551.arnd@arndb.de> (raw)
In-Reply-To: <200610251003.k9PA38kD018604@vass.7ka.mipt.ru>
On Wednesday 25 October 2006 12:03, Vasily Tarasov wrote:
> + * This code works only for 32 bit quota tools over 64 bit OS (x86_64, ia64)
> + * and is necessary due to alignment problems.
> + */
> +struct compat_if_dqblk {
> + compat_uint_t dqb_bhardlimit[2];
> + compat_uint_t dqb_bsoftlimit[2];
> + compat_uint_t dqb_curspace[2];
> + compat_uint_t dqb_ihardlimit[2];
> + compat_uint_t dqb_isoftlimit[2];
> + compat_uint_t dqb_curinodes[2];
> + compat_uint_t dqb_btime[2];
> + compat_uint_t dqb_itime[2];
> + compat_uint_t dqb_valid;
> +};
> +
> +/* XFS structures */
> +struct compat_fs_qfilestat {
> + compat_uint_t dqb_bhardlimit[2];
> + compat_uint_t qfs_nblks[2];
> + compat_uint_t qfs_nextents;
> +};
> +
The patch looks technically correct, but you have defined the structures
in a somewhat unusual way. I'd have defined them with
attribute((packed, aligned(4))) in the end.
Or even better, we should probably add a
typedef unsigned long long __attribute__((aligned(4))) compat_u64;
for x86 compat and use that instead of compat_uint_t foo[2].
Arnd <><
next prev parent reply other threads:[~2006-10-25 11:04 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-25 10:03 [PATCH] diskquota: 32bit quota tools on 64bit architectures Vasily Tarasov
2006-10-25 11:03 ` Arnd Bergmann [this message]
2006-10-25 11:25 ` Vasily Tarasov
2006-10-25 11:50 ` Arnd Bergmann
-- strict thread matches above, loose matches on Subject: below --
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
2007-06-15 11:08 Mikael Pettersson
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 9:01 Vasily Tarasov
2007-06-15 8:59 Vasily Tarasov
2006-10-20 5:59 Vasily Tarasov
2006-10-19 12:32 Vasily Tarasov
2006-10-19 13:06 ` Alan Cox
2006-10-19 15:22 ` Randy Dunlap
2006-10-19 16:09 ` Andi Kleen
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
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=200610251303.50551.arnd@arndb.de \
--to=arnd@arndb.de \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=dev@openvz.org \
--cc=devel@openvz.org \
--cc=dim@openvz.org \
--cc=hch@infradead.org \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
--cc=rkagan@sw.ru \
--cc=vtaras@openvz.org \
--cc=vvs@sw.ru \
/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.