From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id 0B95C467AB for ; Wed, 21 May 2025 13:16:30 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 08578427AB; Wed, 21 May 2025 13:16:30 +0200 (CEST) Received: from dpdk.org (dpdk.org [92.243.24.197]) by mails.dpdk.org (Postfix) with ESMTP id 2DD1A427A4 for ; Wed, 21 May 2025 13:16:29 +0200 (CEST) Received: by dpdk.org (Postfix, from userid 65534) id 29CB0123FAA; Wed, 21 May 2025 13:15:58 +0200 (CEST) Subject: |WARNING| pw153563 [PATCH v1 2/4] ring/soring: fix head-tail synchronization issue In-Reply-To: <20250521111432.207936-3-konstantin.ananyev@huawei.com> References: <20250521111432.207936-3-konstantin.ananyev@huawei.com> To: test-report@dpdk.org From: checkpatch@dpdk.org Cc: Konstantin Ananyev Message-Id: <20250521111558.29CB0123FAA@dpdk.org> Date: Wed, 21 May 2025 13:15:58 +0200 (CEST) X-BeenThere: test-report@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: automatic DPDK test reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: test-report-bounces@dpdk.org Test-Label: checkpatch Test-Status: WARNING http://dpdk.org/patch/153563 _coding style issues_ WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'? #34: Subject: [PATCH v1 2/4] ring/soring: fix head-tail synchronization issue WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'? #57: While running soring_stress_autotest on machine with Ampere Altra Max CPU, WARNING:COMMIT_LOG_LONG_LINE: Possible unwrapped commit description (prefer a maximum 75 chars per line) #61: test_worker_prcs:_st_ring_dequeue_bulk: check_updt_elem(lc=11, num=42) failed at 11-th iter, offending object: 0x103df1480 WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'? #63: EAL: PANIC in soring_verify_state(): WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'? #64: line:382 from:acquire_state_update: soring=0x103c72c00, stage=0, idx=0x7fb8, expected={.stnum=0, .ftoken=0}, actual={.stnum=0x80000028, .ftoken=0x47fb8}; WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'? #82: do { …; success=(CAS(&head); } while(success==0); WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'? #83: loop, i.e. – only when first CAS(&cons.head) attempt fails. WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'? #86: 1) soring_dequeue() calls _fianlize() WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'? #90: 2) soring_dequeue() calls move_cons_head() again. WARNING:TYPO_SPELLING: 'soring' may be misspelled - perhaps 'sorting'? #93: 3) soring_dequeue() is called on different thread WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'? #97: Then CAS(cons.head) fails and returns a new value for it, WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'? #109: for CAS operation. WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'? #110: While in rte_ring_c11_pvt.h – CAS operation is invoked with relaxed WARNING:TYPO_SPELLING: 'SORING' may be misspelled - perhaps 'SORTING'? #113: To fix that issue for SORING - I introduced an extra release fence straight WARNING:TYPO_SPELLING: 'CAS' may be misspelled - perhaps 'CASE'? #124: for CAS(&head) operation in move_head(). WARNING:TYPO_SPELLING: 'couterpart' may be misspelled - perhaps 'counterpart'? #126: couterpart 'tail' latest value will also become visible. total: 0 errors, 16 warnings, 17 lines checked