Message ID | 20240123152850.2880226-1-luiz.dentz@gmail.com (mailing list archive) |
---|---|
State | Accepted |
Commit | eb057846cf0304c5faec30f510965f9071d45e57 |
Headers | show |
Series | [BlueZ,v1] isotest: Fix not handling 0 length packets | expand |
Context | Check | Description |
---|---|---|
tedd_an/pre-ci_am | success | Success |
tedd_an/CheckPatch | warning | WARNING:TYPO_SPELLING: 'sucess' may be misspelled - perhaps 'success'? #92: means their status is not sucess. ^^^^^^ /github/workspace/src/src/13527607.patch total: 0 errors, 1 warnings, 16 lines checked NOTE: For some of the reported defects, checkpatch may be able to mechanically convert to the typical style using --fix or --fix-inplace. /github/workspace/src/src/13527607.patch has style problems, please review. NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO NOTE: If any of the errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS. |
tedd_an/GitLint | success | Gitlint PASS |
tedd_an/BuildEll | success | Build ELL PASS |
tedd_an/BluezMake | success | Bluez Make PASS |
tedd_an/MakeCheck | success | Bluez Make Check PASS |
tedd_an/MakeDistcheck | success | Make Distcheck PASS |
tedd_an/CheckValgrind | success | Check Valgrind PASS |
tedd_an/CheckSmatch | success | CheckSparse PASS |
tedd_an/bluezmakeextell | success | Make External ELL PASS |
tedd_an/IncrementalBuild | success | Incremental Build PASS |
tedd_an/ScanBuild | success | Scan Build PASS |
This is automated email and please do not reply to this email! Dear submitter, Thank you for submitting the patches to the linux bluetooth mailing list. This is a CI test results with your patch series: PW Link:https://patchwork.kernel.org/project/bluetooth/list/?series=819152 ---Test result--- Test Summary: CheckPatch FAIL 0.61 seconds GitLint PASS 0.23 seconds BuildEll PASS 24.01 seconds BluezMake PASS 720.96 seconds MakeCheck PASS 11.97 seconds MakeDistcheck PASS 166.30 seconds CheckValgrind PASS 228.76 seconds CheckSmatch PASS 344.76 seconds bluezmakeextell PASS 112.21 seconds IncrementalBuild PASS 690.32 seconds ScanBuild PASS 955.84 seconds Details ############################## Test: CheckPatch - FAIL Desc: Run checkpatch.pl script Output: [BlueZ,v1] isotest: Fix not handling 0 length packets WARNING:TYPO_SPELLING: 'sucess' may be misspelled - perhaps 'success'? #92: means their status is not sucess. ^^^^^^ /github/workspace/src/src/13527607.patch total: 0 errors, 1 warnings, 16 lines checked NOTE: For some of the reported defects, checkpatch may be able to mechanically convert to the typical style using --fix or --fix-inplace. /github/workspace/src/src/13527607.patch has style problems, please review. NOTE: Ignored message types: COMMIT_MESSAGE COMPLEX_MACRO CONST_STRUCT FILE_PATH_CHANGES MISSING_SIGN_OFF PREFER_PACKED SPDX_LICENSE_TAG SPLIT_STRING SSCANF_TO_KSTRTO NOTE: If any of the errors are false positives, please report them to the maintainer, see CHECKPATCH in MAINTAINERS. --- Regards, Linux Bluetooth
Hello: This patch was applied to bluetooth/bluez.git (master) by Luiz Augusto von Dentz <luiz.von.dentz@intel.com>: On Tue, 23 Jan 2024 10:28:50 -0500 you wrote: > From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> > > It is in fact possible to receive 0 length packets since that probably > means their status is not sucess. > --- > tools/isotest.c | 4 ++-- > 1 file changed, 2 insertions(+), 2 deletions(-) Here is the summary with links: - [BlueZ,v1] isotest: Fix not handling 0 length packets https://git.kernel.org/pub/scm/bluetooth/bluez.git/?id=eb057846cf03 You are awesome, thank you!
diff --git a/tools/isotest.c b/tools/isotest.c index 771d24b6d2a6..7e875fa58b15 100644 --- a/tools/isotest.c +++ b/tools/isotest.c @@ -642,7 +642,7 @@ static void dump_mode(int fd, int sk, char *peer) } syslog(LOG_INFO, "Receiving ..."); - while ((len = read(sk, buf, data_size)) > 0) { + while ((len = read(sk, buf, data_size)) >= 0) { if (fd >= 0) { len = write(fd, buf, len); if (len < 0) { @@ -680,7 +680,7 @@ static void recv_mode(int fd, int sk, char *peer) int r; r = recv(sk, buf, data_size, 0); - if (r <= 0) { + if (r < 0) { if (r < 0) syslog(LOG_ERR, "Read failed: %s (%d)", strerror(errno), errno);
From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com> It is in fact possible to receive 0 length packets since that probably means their status is not sucess. --- tools/isotest.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)