From: Cyrill Gorcunov <gorcunov@gmail.com>
To: Konstantin Osipov <kostja.osipov@gmail.com>
Cc: tml <tarantool-patches@dev.tarantool.org>
Subject: Re: [Tarantool-patches] [PATCH v10 3/4] box/applier: prevent nil dereference on applier rollback
Date: Sat, 15 Feb 2020 21:24:59 +0300 [thread overview]
Message-ID: <20200215182459.GD2527@uranus> (raw)
In-Reply-To: <20200215173741.GC19902@atlas>
On Sat, Feb 15, 2020 at 08:37:41PM +0300, Konstantin Osipov wrote:
> * Cyrill Gorcunov <gorcunov@gmail.com> [20/02/14 17:06]:
> > + /*
> > + * FIXME: Do not clear fiber()->diag since it
> > + * cause nil dereference
> > + *
> > + * applier_subscribe
> > + * applier_apply_tx
> > + * diag_raise
> > + *
> > + * In turn we need to redesign this code:
> > + * - preserve original error or log it somewhere
> > + * - make the error path more clear
> > + *
> > + * We must never reach this point with clean diag
> > + * area, if we do it means we're simply screwed
> > + * somewhere and there is a bug.
>
> I think this comment is obsolete now with the fix below.
The thing is that I saw once the error path which may end
up here without setting diag (well, to be honest i can't
plot a call graph right now but it was related to our
"light" salad helpers and [probably] bptree). That's why
I don't wanted to put assert. But if you prefer sure, I
may update the comment and put assert.
>
> You no longer clear fiber->diag.
>
> > + */
> > +
> > + if (!diag_is_empty(diag_get()))
> > + diag_log();
> > + else
> > + say_warn_ratelimited("applier_txn_rollback_cb: empty diag");
>
> You can also add assert here for debug mode. It should never
> happen.
>
> > +
> > /* Setup shared applier diagnostic area. */
> > diag_set(ClientError, ER_WAL_IO);
> > - diag_move(&fiber()->diag, &replicaset.applier.diag);
> > + diag_add_error(&replicaset.applier.diag,
> > + diag_last_error(&fiber()->diag));
> > +
>
> It would be nice to explain in the comment why you want to
> preserve the original error in the fiber here: because when later
> this fiber is joined in (add call site here), we may want to check
> its diagnostics area.
You know I think we might need to drop replicaset.diag completely
and use applier.diag instead. But again, Kostya, I don't fully
understand this code yet, so I need more time to come with some
clean solution (which I plan to implement on the top).
>
> > /* Broadcast the rollback event across all appliers. */
> > trigger_run(&replicaset.applier.on_rollback, event);
> > /* Rollback applier vclock to the committed one. */
>
> --
> Konstantin Osipov, Moscow, Russia
>
Cyrill
next prev parent reply other threads:[~2020-02-15 18:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-14 14:03 [Tarantool-patches] [PATCH v10 0/4] box/replication: add missing diag set and fix sigsegv Cyrill Gorcunov
2020-02-14 14:03 ` [Tarantool-patches] [PATCH v10 1/4] box/request: add missing OutOfMemory diag_set Cyrill Gorcunov
2020-02-15 17:33 ` Konstantin Osipov
2020-02-14 14:03 ` [Tarantool-patches] [PATCH v10 2/4] box/applier: add missing diag_set on region_alloc failure Cyrill Gorcunov
2020-02-15 17:34 ` Konstantin Osipov
2020-02-14 14:03 ` [Tarantool-patches] [PATCH v10 3/4] box/applier: prevent nil dereference on applier rollback Cyrill Gorcunov
2020-02-15 17:37 ` Konstantin Osipov
2020-02-15 18:24 ` Cyrill Gorcunov [this message]
2020-02-15 18:51 ` Konstantin Osipov
2020-02-14 14:03 ` [Tarantool-patches] [PATCH v10 4/4] test: add replication/applier-rollback Cyrill Gorcunov
2020-02-15 17:38 ` Konstantin Osipov
2020-02-15 17:59 ` Cyrill Gorcunov
2020-02-14 14:12 ` [Tarantool-patches] [PATCH v10 0/4] box/replication: add missing diag set and fix sigsegv Cyrill Gorcunov
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=20200215182459.GD2527@uranus \
--to=gorcunov@gmail.com \
--cc=kostja.osipov@gmail.com \
--cc=tarantool-patches@dev.tarantool.org \
--subject='Re: [Tarantool-patches] [PATCH v10 3/4] box/applier: prevent nil dereference on applier rollback' \
/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
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox