From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: [git pull] ufs fixes
Date: Tue, 20 Jun 2017 06:17:20 +0100 [thread overview]
Message-ID: <20170620051720.GA15490@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20170618010923.GX31671@ZenIV.linux.org.uk>
More UFS fixes, unfortunately including build regression fix for the
64bit s_dsize commit. Fixed in this pile:
* trivial bug in signedness of 32bit timestamps on ufs1
* ESTALE instead of ufs_error() when doing open-by-fhandle on
something deleted
* build regression on 32bit in ufs_new_fragments() - calculating
that many percents of u64 pulls libgcc stuff on some of those. Mea culpa.
* fix hysteresis loop broken by typo in 2.4.14.7 (right next to
the location of previous bug).
* fix the insane limits of said hysteresis loop on filesystems with
very low percentage of reserved blocks. If it's 5% or less, just use the
OPTSPACE policy.
* calculate those limits once and mount time.
I can separate and send just the build regression part if you wish. I would
rather avoid that, though - mul_64_32_div() called again and again, to
calculate the same value... ugh.
That tree does pass xfstests clean (both ufs1 and ufs2) and it _does_ survive
cross-builds. Again, my apologies for missing that, especially since I have
noticed a related percentage-of-64bit issue in earlier patches (when dealing
with amount of reserved blocks). Self-LART applied...
The following changes since commit a8fad984833832d5ca11a9ed64ddc55646da30e3:
ufs_truncate_blocks(): fix the case when size is in the last direct block (2017-06-15 03:57:46 -0400)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git ufs-fixes
for you to fetch changes up to 77e9ce327d9b607cd6e57c0f4524a654dc59c4b1:
ufs: fix the logics for tail relocation (2017-06-17 17:22:42 -0400)
----------------------------------------------------------------
Al Viro (3):
fix signedness of timestamps on ufs1
ufs_iget(): fail with -ESTALE on deleted inode
ufs: fix the logics for tail relocation
fs/ufs/balloc.c | 22 ++++++----------------
fs/ufs/inode.c | 27 +++++++++++----------------
fs/ufs/super.c | 9 +++++++++
fs/ufs/ufs_fs.h | 2 ++
4 files changed, 28 insertions(+), 32 deletions(-)
prev parent reply other threads:[~2017-06-20 5:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-09 21:38 [git pull] first batch of ufs fixes Al Viro
2017-06-10 13:03 ` Richard Narron
2017-06-10 16:07 ` Al Viro
2017-06-10 18:08 ` Al Viro
2017-06-10 18:12 ` Linus Torvalds
2017-06-11 19:47 ` Richard Narron
2017-06-11 21:30 ` Al Viro
2017-06-12 6:14 ` Al Viro
2017-06-13 0:54 ` Richard Narron
2017-06-13 1:43 ` Al Viro
2017-06-13 21:56 ` Richard Narron
2017-06-14 7:11 ` Al Viro
2017-06-14 20:33 ` Richard Narron
2017-06-15 8:00 ` Al Viro
2017-06-16 14:29 ` Richard Narron
2017-06-17 2:15 ` Al Viro
2017-06-18 1:09 ` Al Viro
2017-06-18 20:45 ` Richard Narron
2017-06-20 5:17 ` Al Viro [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=20170620051720.GA15490@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).