From: Lars Ellenberg <lars.ellenberg@linbit.com>
To: drbd-dev@lists.linbit.com
Subject: Re: [Drbd-dev] NULL pointer derefernce in 8.4.7-1 during drbd_destroy_connection()
Date: Tue, 27 Dec 2016 16:54:04 +0100 [thread overview]
Message-ID: <20161227155404.GQ4138@soda.linbit> (raw)
In-Reply-To: <CAAiCvkj-Z=vcp7MpOCRZwhrv_CLd2EmyvM=z=-6n54Ks1at8KQ@mail.gmail.com>
On Sun, Dec 25, 2016 at 11:58:32PM +0800, Feng Sun wrote:
> On Wed, 30 Mar 2016, Lars Ellenberg wrote:
>
> >* On Wed, Mar 30, 2016 at 02:19:07AM +0000, Eric Wheeler wrote:
> *>* > Hello all,
> *>* >
> *>* > We are getting kernel crashes in linux 4.1.20 with the drbd-8.4.git tree
> *>* > at commit 3a6a769340ef93b1ba2792c6461250790795db49 .
> *>* >
> *>* > I don't see anything in the newer commits that addresses this issue so
> *>* > I'm posting---but I'll try the latest commit in master, too, just in case.
> *>* >
> *>* > Please see the backtrace below. I also included our global_common.conf
> *>* > further down. This is protocol A and the link is quite slow. This NULL
> *>* > ptr dereference appears to show up when the drbd kernel thread is blocked
> *>* > for a long time. It might happen at reconnect time because the
> BUG didn't
> *>* > show up until 13 seconds after the P_BARRIER error.
> *>* >
> *>* > The problem is pretty reproducable, so I can probably test patches.
> *>* > Please let me know what I can do to help test.
> *> >* DRBD logs of both peers leading up to the incident may be useful.*
>
>
> *I have met same issue with 8.4.9, but I cannot reproduce this easily.can
You likely want to apply this:
http://git.linbit.com/drbd-8.4.git/commitdiff/e0645836e870346cafe688cbdd8ec29092f6cdb5
> you help to share about the reproduce steps? *
Provoke:
you need a kernel >= 4.0,
you need to to hit congestion, but have "ko-count" set "high enough",
and DRBD pings on our meta socket need to still "feel" responsive
(ping-timeout is high enough).
It helps if DRBD does not use sendpage, which means you use protocol A,
or have "data-integrity-alg" enabled,
or have explicitly disabled sendpage (drbd module parameter)
or have some file system or other user that keeps submitting slab pages
or other pages with a reference count of zero.
Thanks,
--
: Lars Ellenberg
: LINBIT | Keeping the Digital World Running
: DRBD -- Heartbeat -- Corosync -- Pacemaker
: R&D, Integration, Ops, Consulting, Support
DRBD® and LINBIT® are registered trademarks of LINBIT
next prev parent reply other threads:[~2016-12-27 15:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-25 15:58 [Drbd-dev] NULL pointer derefernce in 8.4.7-1 during drbd_destroy_connection() Feng Sun
2016-12-27 15:54 ` Lars Ellenberg [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-03-30 2:19 [Drbd-dev] NULL pointer derefernce in 8.4.7-1 Eric Wheeler
2016-03-30 12:00 ` Lars Ellenberg
2016-03-30 19:52 ` [Drbd-dev] NULL pointer derefernce in 8.4.7-1 during drbd_destroy_connection() Eric Wheeler
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=20161227155404.GQ4138@soda.linbit \
--to=lars.ellenberg@linbit.com \
--cc=drbd-dev@lists.linbit.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