From: compudj@krystal.dyndns.org (Mathieu Desnoyers)
Subject: [ltt-dev] LTTng formal verification fix, take 2
Date: Tue, 14 Oct 2008 20:34:19 -0400 [thread overview]
Message-ID: <20081015003418.GA6713@Krystal> (raw)
Hi,
I went over the formal verification fix about the reader thinking that
subbuffers are full when in fact they are empty, which could happen with
particularly small subbuffers or large events.
The initial version I did have gross errors in offset handling. This
version seems to be much better. I went over all the changes one by one
and found out my previous mistakes.
Those changes are introduced by
lttng-transport-formal-verif-fix-2.patch
http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git;a=commit;h=ff21b5f94a5134ddc3d838f4c81b9b2a5d0828a6
and
lttng-transport-locked-formal-verif-fix-2-port.patch
http://git.kernel.org/?p=linux/kernel/git/compudj/linux-2.6-lttng.git;a=commit;h=77a5887ad065a3bb3156c6ba910d785e03def3de
in LTTng 0.41.
Feel free to review and test them.
Thanks,
Mathieu
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
reply other threads:[~2008-10-15 0:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20081015003418.GA6713@Krystal \
--to=compudj@krystal.dyndns.org \
/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