X-Git-Url: http://git.lttng.org/?a=blobdiff_plain;ds=sidebyside;f=doc%2Fman%2Flttng-ust.3;fp=doc%2Fman%2Flttng-ust.3;h=4e30d7622c37e950e3c482141872b7e805ec63d9;hb=b3b8f5dfecadf554e7473b3c0af218e411f2f258;hp=7cc3bfde5b7112b354d6d5c4e81fc4c0115d45dc;hpb=116bdc41ac77a437f138fd0457a9da4b70411659;p=lttng-ust.git

diff --git a/doc/man/lttng-ust.3 b/doc/man/lttng-ust.3
index 7cc3bfde..4e30d762 100644
--- a/doc/man/lttng-ust.3
+++ b/doc/man/lttng-ust.3
@@ -362,10 +362,23 @@ startup time.
 .PP
 lttng-gen-tp(1), lttng(1), babeltrace(1), lttng-sessiond(8)
 .PP
+
+.SH "COMPATIBILITY"
+
+.PP
+Older lttng-ust libraries reject more recent, and incompatible, probe
+providers. Newer lttng-ust librairies accept older probe providers, even
+though some newer features might not be available with those providers.
+.PP
+
 .SH "BUGS"
 
 .PP
-No knows bugs at this point.
+LTTng-UST 2.0 and 2.1 lttng-ust libraries do not check for probe
+provider version compatibility. This can lead to out-of-bound accesses
+when using a more recent probe provider with an older lttng-ust library.
+These error only trigger when tracing is active. This issue has been
+fixed in LTTng-UST 2.2.
 
 If you encounter any issues or usability problem, please report it on
 our mailing list <lttng-dev@lists.lttng.org> to help improve this