From: Andreas Gruenbacher <agruenba@redhat.com>
To: cluster-devel.redhat.com
Subject: [Cluster-devel] kernel BUG at fs/gfs2/inode.h:64
Date: Wed, 9 Jan 2019 21:00:55 +0100 [thread overview]
Message-ID: <CAHc6FU6R5qas26ZBFe4EngP+mLOFkZseqS95DTS4gPZCA4M7pg@mail.gmail.com> (raw)
In-Reply-To: <3vkfw9efgsm8uwdc0kp83e7g.1547059260503@email.citrix.com>
On Wed, 9 Jan 2019 at 19:44, Mark Syms <Mark.Syms@citrix.com> wrote:
>
> So, actually the original comparison in the assert (dodgy scaling factor not withstanding) was probably correct in that we don't ever want to remove all blocks from the inode as one of them is used for the inode itself? Or do we still think it should allow for change to be the negative of current blocks?
It doesn't make a difference; all we care about is that we don't go
negative. I think the updated comparison better reflects that goal.
Andreas
prev parent reply other threads:[~2019-01-09 20:00 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-08 13:32 [Cluster-devel] kernel BUG at fs/gfs2/inode.h:64 Mark Syms
2019-01-09 12:05 ` Tim Smith
2019-01-09 13:31 ` Andreas Gruenbacher
2019-01-09 13:43 ` Mark Syms
2019-01-09 15:35 ` Andreas Gruenbacher
2019-01-09 17:14 ` Tim Smith
2019-01-09 17:18 ` Steven Whitehouse
2019-01-09 17:24 ` Andreas Gruenbacher
2019-01-09 18:43 ` Mark Syms
2019-01-09 20:00 ` Andreas Gruenbacher [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=CAHc6FU6R5qas26ZBFe4EngP+mLOFkZseqS95DTS4gPZCA4M7pg@mail.gmail.com \
--to=agruenba@redhat.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).