Uploaded image for project: 'Lustre'
  1. Lustre
  2. LU-4871

missing newlines at end of error messages

Details

    • 3
    • 13464

    Description

      There are 70 odd CERROR/CWARN/CDEBUG... messages with missing newlines. The attached file was generated a few weeks ago.

      Attachments

        Issue Links

          Activity

            [LU-4871] missing newlines at end of error messages

            Resolving ticket since patch for LU-5551, http://review.whamcloud.com/#/c/11996/3 , landed to master (pre-2.7)

            jamesanunez James Nunez (Inactive) added a comment - Resolving ticket since patch for LU-5551 , http://review.whamcloud.com/#/c/11996/3 , landed to master (pre-2.7)

            That message should be cleaned up with the LU-5551 patch at http://review.whamcloud.com/#/c/11996/3

            jamesanunez James Nunez (Inactive) added a comment - That message should be cleaned up with the LU-5551 patch at http://review.whamcloud.com/#/c/11996/3

            Me too.

            simmonsja James A Simmons added a comment - Me too.
            cliffw Cliff White (Inactive) added a comment - - edited

            With latest master, 2.6.53, I am getting buried in these messages:

            iwc12 kernel: format at osc_cache.c:1473:osc_enter_cache_try doesn't end in newline

            cliffw Cliff White (Inactive) added a comment - - edited With latest master, 2.6.53, I am getting buried in these messages: iwc12 kernel: format at osc_cache.c:1473:osc_enter_cache_try doesn't end in newline

            Patch landed to master

            jamesanunez James Nunez (Inactive) added a comment - Patch landed to master

            John,

            Patch http://review.whamcloud.com/#/c/10000/ landed. Should we close this ticket or do you want to generate a new list to see if there are new cases of missing newlines in the latest master?

            James

            jamesanunez James Nunez (Inactive) added a comment - John, Patch http://review.whamcloud.com/#/c/10000/ landed. Should we close this ticket or do you want to generate a new list to see if there are new cases of missing newlines in the latest master? James
            jamesanunez James Nunez (Inactive) added a comment - Proposed patch at http://review.whamcloud.com/#/c/10000/

            The double newlines are a results of LDLM_DEBUG_NOLOCK being defined as:
            #define LDLM_DEBUG_NOLOCK(format, a...) \
            CDEBUG(D_DLMTRACE, "### " format "\n" , ##a)

            So, anyone using LDLM_DEBUG_NOLOCK should not use a newline character at the end of the message. At least two uses of LDLM_DEBUG_NOLOCK used the newline, producing the double newlines printed and there are several examples of calling LDLM_DEBUG_NOLOCK without the newline character.

            We have other examples of defining new routines based on CDEBUG, CL_LOCK_DEBUG for example, and we don’t add a newline character in the definition of those routines. I think we should be consistent and leave out the "\n" in the definition of LDLM_DEBUG_NOLOCK.

            jamesanunez James Nunez (Inactive) added a comment - The double newlines are a results of LDLM_DEBUG_NOLOCK being defined as: #define LDLM_DEBUG_NOLOCK(format, a...) \ CDEBUG(D_DLMTRACE, "### " format "\n" , ##a) So, anyone using LDLM_DEBUG_NOLOCK should not use a newline character at the end of the message. At least two uses of LDLM_DEBUG_NOLOCK used the newline, producing the double newlines printed and there are several examples of calling LDLM_DEBUG_NOLOCK without the newline character. We have other examples of defining new routines based on CDEBUG, CL_LOCK_DEBUG for example, and we don’t add a newline character in the definition of those routines. I think we should be consistent and leave out the "\n" in the definition of LDLM_DEBUG_NOLOCK.
            jhammond John Hammond added a comment -

            I also noticed two messages with double newlines:

            ll_layout_refresh
            osc_lock_init
            
            --
            00000008:00010000:3.0:1397487994.678070:0:5401:0:(osc_lock.c:1753:osc_lock_init()) ### lock ffff8801e4af0ed0, osc lock ffff8801e457bcc0, flags 41000
            
            --
            00000080:00010000:3.0:1397487994.678467:0:5401:0:(file.c:3975:ll_layout_refresh()) ### lustre: requeue layout lock for file [0x280000400:0x12b:0x0](ffff8802002c4b78)
            
            
            jhammond John Hammond added a comment - I also noticed two messages with double newlines: ll_layout_refresh osc_lock_init -- 00000008:00010000:3.0:1397487994.678070:0:5401:0:(osc_lock.c:1753:osc_lock_init()) ### lock ffff8801e4af0ed0, osc lock ffff8801e457bcc0, flags 41000 -- 00000080:00010000:3.0:1397487994.678467:0:5401:0:(file.c:3975:ll_layout_refresh()) ### lustre: requeue layout lock for file [0x280000400:0x12b:0x0](ffff8802002c4b78)
            pjones Peter Jones added a comment -

            James

            Could you please take care of this one?

            Thanks

            Peter

            pjones Peter Jones added a comment - James Could you please take care of this one? Thanks Peter

            People

              jamesanunez James Nunez (Inactive)
              jhammond John Hammond
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: