xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Al Viro <viro@ZenIV.linux.org.uk>
To: Ian Jackson <ian.jackson@eu.citrix.com>
Cc: Evgeniy Dushistov <dushistov@mail.ru>,
	xen-devel@lists.xensource.com,
	Linus Torvalds <torvalds@linux-foundation.org>,
	Jonathan Cameron <jic23@kernel.org>, Jens Axboe <axboe@fb.com>,
	linux-fsdevel@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: ufs build failure (no __udivdi3) on i386 in linux tip (edf9364d3f92)
Date: Mon, 19 Jun 2017 16:08:18 +0100	[thread overview]
Message-ID: <20170619150818.GC10672@ZenIV.linux.org.uk> (raw)
In-Reply-To: <22855.57727.390987.969954@mariner.uk.xensource.com>

On Mon, Jun 19, 2017 at 03:36:47PM +0100, Ian Jackson wrote:
> osstest service owner writes ("[linux-linus bisection] complete build-i386-pvops"):
> > branch xen-unstable
> > xenbranch xen-unstable
> > job build-i386-pvops
> > testid kernel-build
> > 
> > Tree: linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> > Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
> > 
> > *** Found and reproduced problem changeset ***
> > 
> >   Bug is in tree:  linux git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
> >   Bug introduced:  edf9364d3f924aff6f77176b8e52a4b68e5c30d6
> >   Bug not present: 791a9a666d1afe2603bcb2c6a4852d684e879252
> >   Last fail repro: http://logs.test-lab.xenproject.org/osstest/logs/110566/
> 
> This is a merge commit, so the bisection result is not very useful:
> 
>    git-log --pretty=oneline 791a9a666d1afe2603bcb2c6a4852d684e879252..edf9364d3f924aff6f77176b8e52a4b68e5c30d6 | wc -l
>    2233
> 
> The error message is this:
> 
>    ERROR: "__udivdi3" [fs/ufs/ufs.ko] undefined!
>    scripts/Makefile.modpost:91: recipe for target '__modpost' failed
>    make[1]: *** [__modpost] Error 1

It's 64bit ->s_dsize going through "multiply by this, divide by 100".
Can be papered over by using mul_64_u32_div() in ufs_new_fragments(),
but
	* expression remains unchanged, so it's better done at
mount time
	* there's a braino (since circa 2002) in the same code
- the expression(s) are for the levels of fragmentation that
trigger switches in hysteresis loop and both switches lead to
the same state due to cut'n'paste damage
	* for really low minfree we get those levels too close
to each other - at minfree 5 we get 0.025 .. 0.03, at minfree 4
they outright merge and below that the upper bound is less than
the lower one.  We'd copied the original 4.4BSD here; at 1995
FreeBSD got switched to "minfree 5 or below means using OPTSPACE
all the time".

Fixed in vfs.git#ufs-fixes; see commit 77e9ce327d9b607cd6e57c0f4524a654dc59c4b1
there.  Not sure if it's worth splitting...

  reply	other threads:[~2017-06-19 15:08 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-19 13:48 [linux-linus bisection] complete build-i386-pvops osstest service owner
2017-06-19 14:36 ` ufs build failure (no __udivdi3) on i386 in linux tip (edf9364d3f92) Ian Jackson
2017-06-19 15:08   ` Al Viro [this message]
2017-06-19 17:22     ` Geert Uytterhoeven
2017-06-19 17:34       ` Al Viro

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=20170619150818.GC10672@ZenIV.linux.org.uk \
    --to=viro@zeniv.linux.org.uk \
    --cc=axboe@fb.com \
    --cc=dushistov@mail.ru \
    --cc=ian.jackson@eu.citrix.com \
    --cc=jic23@kernel.org \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.org \
    --cc=xen-devel@lists.xensource.com \
    /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;
as well as URLs for NNTP newsgroup(s).