From: John Lightsey <john@nixnuts.net>
To: ocfs2-devel@oss.oracle.com
Subject: [Ocfs2-devel] [PATCH] Bug#841144: kernel BUG at /build/linux-Wgpe2M/linux-4.8.11/fs/ocfs2/alloc.c:1514!
Date: Mon, 20 Nov 2017 12:54:50 -0600 [thread overview]
Message-ID: <1511204090.3644.6.camel@nixnuts.net> (raw)
In January Ben Hutchings reported Debian bug 841144 to the ocfs2-devel
list:
https://oss.oracle.com/pipermail/ocfs2-devel/2017-January/012701.html
cPanel encountered this bug after upgrading our cluster to the 4.9
Debian stable kernel. In our environment, the bug would trigger every
few hours.
The core problem seems to be that the size of dw_zero_list is not
tracked correctly. This causes the ocfs2_lock_allocators() call in
ocfs2_dio_end_io_write() to underestimate the number of extents needed.
As a result, meta_ac is null when it's needed in ocfs2_grow_tree().
The attached patch is a forward-ported version of the fix we applied to
Debian's 4.9 kernel to correct the issue.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-Fix-OCFS2-extent-split-estimation-for-dio-allocators.patch
Type: text/x-patch
Size: 1712 bytes
Desc: not available
Url : http://oss.oracle.com/pipermail/ocfs2-devel/attachments/20171120/be39dbe1/attachment.bin
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part
Url : http://oss.oracle.com/pipermail/ocfs2-devel/attachments/20171120/be39dbe1/attachment-0001.bin
next reply other threads:[~2017-11-20 18:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-20 18:54 John Lightsey [this message]
2017-11-21 0:58 ` [Ocfs2-devel] [PATCH] Bug#841144: kernel BUG at /build/linux-Wgpe2M/linux-4.8.11/fs/ocfs2/alloc.c:1514! Changwei Ge
2017-11-21 2:45 ` John Lightsey
2017-11-21 5:58 ` Changwei Ge
2017-11-21 21:05 ` John Lightsey
2017-11-24 5:46 ` alex chen
2017-11-24 7:03 ` Changwei Ge
2017-11-24 10:06 ` alex chen
2017-11-28 14:34 ` John Lightsey
2017-11-29 4:37 ` alex chen
2017-11-21 3:04 ` piaojun
2017-11-21 4:24 ` John Lightsey
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=1511204090.3644.6.camel@nixnuts.net \
--to=john@nixnuts.net \
--cc=ocfs2-devel@oss.oracle.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 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.