From: Cyrill Gorcunov <gorcunov@gmail.com> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: tml <tarantool-patches@dev.tarantool.org> Subject: Re: [Tarantool-patches] [PATCH v5 4/4] crash: report crash data to the feedback server Date: Wed, 23 Dec 2020 21:57:57 +0300 [thread overview] Message-ID: <20201223185757.GF8261@grain> (raw) In-Reply-To: <30a781d7-4f4e-3543-f67e-2fb1f7cce172@tarantool.org> On Wed, Dec 23, 2020 at 07:47:44PM +0100, Vladislav Shpilevoy wrote: > > > > +/** > > + * Mark an environment that we're in crashinfo handling, this > > + * allows us to escape recursive attempts to send report, > > + * if the action of sending report is failing itself. > > + */ > > +static int > > +crash_mark_env_mode(void) > > 1. You don't need to change 'env'. Because in the new process > send_crashinfo will be false. Therefore it won't send the crash > anyway. Yeah, good catch! Will drop this. > > +/** > > + * Zap reserved symbols. > > + */ > > +static char * > > +json_zap(char *s) > > 2. Why can't you simply call json_escape(), which we > already have? Yes, it may add a few more bytes, but it > is not something super bad. json_escape() returns number > of written bytes, so you can use it quite easy. Ah, I didn't know that we have this helper. Thanks, Vlad! > > It would look even simpler, if you would use the existing > SNPRINT() macros. It returns -1 on fail, but you could patch > it or introduce SNPRINT_GO which would goto to a given label. > Or keep return -1, and do it like in sio_socketname_to_buffer() - > it has a separate function to do all the prints. > > I tried to do that in my diff. > > > +{ > > + if (s == NULL) > > + return NULL; > > + > > + /* > > + * Actually we should escape them but for > > + * now lets just zap without changing source > > + * size. > > + */ > > + for (size_t i = 0; i < strlen(s); i++) { > > 3. Strlen() is going to be called on each iteration. Please, save > the result into a variable. Or just use json_escape(). Nope, it won't. gcc is smart enough to move this bb out of cycle. This is known for decades already. Still if I gonna use json helper you pointed above I'll not need this function completely. > Consider my fixes below and on top of the branch in a separate > commit. I didn't test them though. So there are likely to be a > few typos. Yeah, thanks a lot. Will update and report you.
next prev parent reply other threads:[~2020-12-23 18:58 UTC|newest] Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-12-23 15:41 [Tarantool-patches] [PATCH v5 0/4] Our feedback daemon sends only a few portions of usage Cyrill Gorcunov 2020-12-23 15:41 ` [Tarantool-patches] [PATCH v5 1/4] util: introduce strlcpy helper Cyrill Gorcunov 2020-12-23 15:41 ` [Tarantool-patches] [PATCH v5 2/4] backtrace: allow to specify destination buffer Cyrill Gorcunov 2020-12-23 15:41 ` [Tarantool-patches] [PATCH v5 3/4] crash: move fatal signal handling in Cyrill Gorcunov 2020-12-23 15:41 ` [Tarantool-patches] [PATCH v5 4/4] crash: report crash data to the feedback server Cyrill Gorcunov 2020-12-23 18:47 ` Vladislav Shpilevoy 2020-12-23 18:57 ` Cyrill Gorcunov [this message] 2020-12-23 21:22 ` Cyrill Gorcunov 2020-12-24 13:16 ` Cyrill Gorcunov 2020-12-24 17:15 ` Vladislav Shpilevoy 2020-12-24 17:33 ` Cyrill Gorcunov 2020-12-24 18:22 ` Vladislav Shpilevoy 2020-12-24 18:33 ` 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=20201223185757.GF8261@grain \ --to=gorcunov@gmail.com \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH v5 4/4] crash: report crash data to the feedback server' \ /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