From: Al Viro <viro@ZenIV.linux.org.uk>
To: Guenter Roeck <linux@roeck-us.net>
Cc: Evgeniy Dushistov <dushistov@mail.ru>,
Mark Brown <broonie@kernel.org>,
linux-kernel@vger.kernel.org, Arnd Bergmann <arnd@arndb.de>
Subject: Re: [PATCH] ufs: Fix build errors on 32 bit machines
Date: Sat, 17 Jun 2017 19:23:28 +0100 [thread overview]
Message-ID: <20170617182328.GV31671@ZenIV.linux.org.uk> (raw)
In-Reply-To: <1497720913-10787-1-git-send-email-linux@roeck-us.net>
On Sat, Jun 17, 2017 at 10:35:13AM -0700, Guenter Roeck wrote:
> Various 32 builds fail with error messages such as
>
> ERROR: "__udivdi3" [fs/ufs/ufs.ko] undefined!
>
> due to a variable type change from 32 bit to 64 bit.
Actually, that's not the only problem in that place. The breakage
came in 2.4.14.7; the critical part was this:
default:
- usb1->fs_optim = SWAB32(UFS_OPTTIME);
+ usb1->fs_optim = cpu_to_fs32(sb, UFS_OPTTIME);
case UFS_OPTTIME:
request = uspi->s_fpb;
- if (SWAB32(usb1->fs_cstotal.cs_nffree) < uspi->s_dsize *
+ if (fs32_to_cpu(sb, usb1->fs_cstotal.cs_nffree) < uspi->s_dsize *
(uspi->s_minfree - 2) / 100)
break;
- usb1->fs_optim = SWAB32(UFS_OPTSPACE);
+ usb1->fs_optim = cpu_to_fs32(sb, UFS_OPTTIME);
break;
See the problem? Instead of hysteresis loop flipping between optspace and opttime
allocation policies, it *never* switches out of opttime.
That came in
commit 6293d56ca18db9ed322b2a5550ac7b27bd538cff
Author: Linus Torvalds <torvalds@athlon.transmeta.com>
Date: Mon Feb 4 20:33:51 2002 -0800
v2.4.14.6 -> v2.4.14.7
- Jeff Garzik: network driver updates
- Christoph Hellwig: UFS filesystem byteorder cleanups
- me: modified Andrea VM page allocator tuning
so probably a typo in Christoph's patches, missed by everyone at the time.
And I would prefer to have the nffree levels at which we switch back and
forth precalculated at mount time. I'll send a fix (along with those
for the last remaining xfstests failures) later today.
next prev parent reply other threads:[~2017-06-17 18:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-17 17:35 [PATCH] ufs: Fix build errors on 32 bit machines Guenter Roeck
2017-06-17 18:23 ` Al Viro [this message]
2017-06-17 18:51 ` Al Viro
2017-06-18 9:30 ` Guenter Roeck
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=20170617182328.GV31671@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=arnd@arndb.de \
--cc=broonie@kernel.org \
--cc=dushistov@mail.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
/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.