X-Git-Url: https://git.whamcloud.com/?a=blobdiff_plain;f=lnet%2FChangeLog;h=037318e11ea00622c0aa9b6b1ca4d64014db25f8;hb=b7c0c4241034fce9486d408040189e0cb08def8b;hp=099530526fa3cc0fb8ed1185d06a530521fcd8e9;hpb=c78cfaaa580da8d2c883c38e8baa493c302c3264;p=fs%2Flustre-release.git diff --git a/lnet/ChangeLog b/lnet/ChangeLog index 0995305..037318e 100644 --- a/lnet/ChangeLog +++ b/lnet/ChangeLog @@ -1,41 +1,155 @@ -2007-04-23 Cluster File Systems, Inc. +2007-08-27 Cluster File Systems, Inc. + * version 1.6.2 + * Support for networks: + socklnd - kernels up to 2.6.16, + qswlnd - Qsnet kernel modules 5.20 and later, + openiblnd - IbGold 1.8.2, + o2iblnd - OFED 1.1 and 1.2, + viblnd - Voltaire ibhost 3.4.5 and later, + ciblnd - Topspin 3.2.0, + iiblnd - Infiniserv 3.3 + PathBits patch, + gmlnd - GM 2.1.22 and later, + mxlnd - MX 1.2.1 or later, + ptllnd - Portals 3.3 / UNICOS/lc 1.5.x, 2.0.x + +Severity : normal +Bugzilla : 13279 +Description: open files rlimit 1024 reached while liblustre testing +Details : ulnds/socklnd must close open socket after unsuccessful + 'say hello' attempt. + +------------------------------------------------------------------------------ + +2007-07-30 Cluster File Systems, Inc. * version 1.4.11 / 1.6.1 * Support for networks: - socklnd - kernels up to 2.6.16 - qswlnd - Qsnet kernel modules 5.20 and later - openiblnd - IbGold 1.8.2 - o2iblnd - OFED 1.1 - viblnd - Voltaire ibhost 3.4.5 and later - ciblnd - Topspin 3.2.0 - iiblnd - Infiniserv 3.3 + PathBits patch - gmlnd - GM 2.1.22 and later - mxlnd - MX 1.2.1 or later + socklnd - kernels up to 2.6.16, + qswlnd - Qsnet kernel modules 5.20 and later, + openiblnd - IbGold 1.8.2, + o2iblnd - OFED 1.1 and 1.2, + viblnd - Voltaire ibhost 3.4.5 and later, + ciblnd - Topspin 3.2.0, + iiblnd - Infiniserv 3.3 + PathBits patch, + gmlnd - GM 2.1.22 and later, + mxlnd - MX 1.2.1 or later, ptllnd - Portals 3.3 / UNICOS/lc 1.5.x, 2.0.x - * bug fixes + +Severity : minor +Bugzilla : 13288 +Description: Initialize cpumask before use + +Severity : major +Bugzilla : 12014 +Description: ASSERTION failures when upgrading to the patchless zero-copy + socklnd +Details : This bug affects "rolling upgrades", causing an inconsistent + protocol version negotiation and subsequent assertion failure + during rolling upgrades after the first wave of upgrades. + +Severity : minor +Bugzilla : 11223 +Details : Change "dropped message" CERRORs to D_NETERROR so they are + logged instead of creating "console chatter" when a lustre + timeout races with normal RPC completion. + +Severity : minor +Details : lnet_clear_peer_table can wait forever if user forgets to + clear a lazy portal. + +Severity : minor +Details : libcfs_id2str should check pid against LNET_PID_ANY. + +Severity : major +Bugzilla : 10916 +Description: added LNET self test +Details : landing b_self_test + +Severity : minor +Frequency : rare +Bugzilla : 12227 +Description: cfs_duration_{u,n}sec() wrongly calculate nanosecond part of + struct timeval. +Details : do_div() macro is used incorrectly. + +2007-04-23 Cluster File Systems, Inc. + +Severity : normal +Bugzilla : 11680 +Description: make panic on lbug configurable + +Severity : major +Bugzilla : 12316 +Description: Add OFED1.2 support to o2iblnd +Details : o2iblnd depends on OFED's modules, if out-tree OFED's modules + are installed (other than kernel's in-tree infiniband), there + could be some problem while insmod o2iblnd (mismatch CRC of + ib_* symbols). + If extra Module.symvers is supported in kernel (i.e, 2.6.17), + this link provides solution: + https://bugs.openfabrics.org/show_bug.cgi?id=355 + if extra Module.symvers is not supported in kernel, we will + have to run the script in bug 12316 to update + $LINUX/module.symvers before building o2iblnd. + More details about this are in bug 12316. ------------------------------------------------------------------------------ 2007-04-01 Cluster File Systems, Inc. * version 1.4.10 / 1.6.0 * Support for networks: - socklnd - kernels up to 2.6.16 - qswlnd - Qsnet kernel modules 5.20 and later - openiblnd - IbGold 1.8.2 - o2iblnd - OFED 1.1 - viblnd - Voltaire ibhost 3.4.5 and later - ciblnd - Topspin 3.2.0 - iiblnd - Infiniserv 3.3 + PathBits patch - gmlnd - GM 2.1.22 and later - mxlnd - MX 1.2.1 or later + socklnd - kernels up to 2.6.16, + qswlnd - Qsnet kernel modules 5.20 and later, + openiblnd - IbGold 1.8.2, + o2iblnd - OFED 1.1, + viblnd - Voltaire ibhost 3.4.5 and later, + ciblnd - Topspin 3.2.0, + iiblnd - Infiniserv 3.3 + PathBits patch, + gmlnd - GM 2.1.22 and later, + mxlnd - MX 1.2.1 or later, ptllnd - Portals 3.3 / UNICOS/lc 1.5.x, 2.0.x - * bug fixes + +Severity : minor +Frequency : rare +Description: Ptllnd didn't init kptllnd_data.kptl_idle_txs before it could be + possibly accessed in kptllnd_shutdown. Ptllnd should init + kptllnd_data.kptl_ptlid2str_lock before calling kptllnd_ptlid2str. +Severity : normal +Frequency : rare +Description: gmlnd ignored some transmit errors when finalizing lnet messages. + +Severity : minor +Frequency : rare +Description: ptllnd logs a piece of incorrect debug info in kptllnd_peer_handle_hello. + +Severity : minor +Frequency : rare +Description: the_lnet.ln_finalizing was not set when the current thread is + about to complete messages. It only affects multi-threaded + user space LNet. + +Severity : normal +Frequency : rare +Bugzilla : 11472 +Description: Changed the default kqswlnd ntxmsg=512 + +Severity : major +Frequency : rare +Bugzilla : 12458 +Description: Assertion failure in kernel ptllnd caused by posting passive + bulk buffers before connection establishment complete. + +Severity : major +Frequency : rare +Bugzilla : 12455 +Description: A race in kernel ptllnd between deleting a peer and posting + new communications for it could hang communications - + manifesting as "Unexpectedly long timeout" messages. + Severity : major Frequency : rare -Bugzilla : 11706 -Description: Added LNetSetAsync() to ensure single-threaded userspace - clients can be eager LNET receivers even when the application - is not executing in the filesystem. +Bugzilla : 12432 +Description: Kernel ptllnd lock ordering issue could hang a node. Severity : major Frequency : rare