Details

    • Bug
    • Resolution: Fixed
    • Trivial
    • Lustre 2.3.0
    • Lustre 2.0.0, Lustre 2.1.0, Lustre 1.8.x (1.8.0 - 1.8.5)
    • 4623

    Description

      I recently noticed these:

      1. The doxygen comment above LNetNIInit in lnet/lnet/api-ni.c says:
      "return 0 on success, and non-zero error code on failures."

      This is wrong. LNetNIInit can return > 0 on success.

      2. In lst_test_add_ioctl()

      753 LIBCFS_ALLOC(dstgrp, args->lstio_tes_dgrp_nmlen + 1);
      754 if (srcgrp == NULL)$
      755 goto out;

      In line 754, s/srcgrp/dstgrp/?

      I don't have time to fix and test and so on. Please fix them.

      Attachments

        Issue Links

          Activity

            [LU-1078] two minor issues in lnet
            pjones Peter Jones added a comment -

            Landed for 2.3

            pjones Peter Jones added a comment - Landed for 2.3
            pjones Peter Jones added a comment -

            Reassigning to Bob

            pjones Peter Jones added a comment - Reassigning to Bob
            mdiep Minh Diep added a comment -

            sure

            mdiep Minh Diep added a comment - sure
            pjones Peter Jones added a comment -

            Minh

            Why don't you clean these LNET issues up when you get a chance?

            Thanks

            Peter

            pjones Peter Jones added a comment - Minh Why don't you clean these LNET issues up when you get a chance? Thanks Peter

            Well, please reassign it to me then. When I have a chance I'll have a look at the document and fix it.

            isaac Isaac Huang (Inactive) added a comment - Well, please reassign it to me then. When I have a chance I'll have a look at the document and fix it.

            I don't have time to fix and test and so on. Please fix them.

            Isaac,
            as you can well imagine, everyone is busy with projects of their own as well, so the best way to fix minor issues like this is to do it yourself. The time it takes to submit a patch for such a minor change is very minimal with the new automated build and test system. Creating a patch, commit it to Git with a proper commit comment referencing this LU-1078 ticket (see http://wiki.whamcloud.com/display/PUB/Commit+Comments for details), pushing it to Gerrit, and asking for reviews is sufficient, since the patch will be built and tested automatically before it could land in any case.

            adilger Andreas Dilger added a comment - I don't have time to fix and test and so on. Please fix them. Isaac, as you can well imagine, everyone is busy with projects of their own as well, so the best way to fix minor issues like this is to do it yourself. The time it takes to submit a patch for such a minor change is very minimal with the new automated build and test system. Creating a patch, commit it to Git with a proper commit comment referencing this LU-1078 ticket (see http://wiki.whamcloud.com/display/PUB/Commit+Comments for details), pushing it to Gerrit, and asking for reviews is sufficient, since the patch will be built and tested automatically before it could land in any case.

            People

              bogl Bob Glossman (Inactive)
              isaac Isaac Huang (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: