Bug #62059: valgrind: Syscall param write(buf) points to uninitialised byte(s) - rgw - Ceph

Actions

Copy link

Bug #62059

open

valgrind: Syscall param write(buf) points to uninitialised byte(s)

Added by Casey Bodley 10 months ago. Updated 9 months ago.

Status:

Pending Backport

Priority:

Urgent

Assignee:

Casey Bodley

Target version:

% Done:

Source:

Tags:

valgrind backport_processed

Backport:

reef

Regression:

Severity:

3 - minor

Reviewed:

Affected Versions:

ceph-qa-suite:

Pull request ID:

52521

Crash signature (v1):

Crash signature (v2):

Description

very similar to https://tracker.ceph.com/issues/61428 except call_init was call_init.part.0

happening on centos9 jobs in https://pulpito.ceph.com/cbodley-2023-07-17_21:26:30-rgw-main-distro-default-smithi/
ex http://qa-proxy.ceph.com/teuthology/cbodley-2023-07-17_21:26:30-rgw-main-distro-default-smithi/7342699/teuthology.log

<error>
  <unique>0x0</unique>
  <tid>1</tid>
  <kind>SyscallParam</kind>
  <what>Syscall param write(buf) points to uninitialised byte(s)</what>
  <stack>
    <frame>
      <ip>0x78D5E5D</ip>
      <obj>/usr/lib64/libc.so.6</obj>
      <fn>syscall</fn>
    </frame>
    <frame>
      <ip>0x995F941</ip>
      <obj>/usr/lib64/libunwind.so.8.0.1</obj>
    </frame>
    <frame>
      <ip>0x995FA57</ip>
      <obj>/usr/lib64/libunwind.so.8.0.1</obj>
    </frame>
    <frame>
      <ip>0x9964179</ip>
      <obj>/usr/lib64/libunwind.so.8.0.1</obj>
    </frame>
    <frame>
      <ip>0x99651A1</ip>
      <obj>/usr/lib64/libunwind.so.8.0.1</obj>
      <fn>_ULx86_64_step</fn>
    </frame>
    <frame>
      <ip>0x6F5471A</ip>
      <obj>/usr/lib64/libtcmalloc.so.4.5.9</obj>
    </frame>
    <frame>
      <ip>0x6F53C6F</ip>
      <obj>/usr/lib64/libtcmalloc.so.4.5.9</obj>
    </frame>
    <frame>
      <ip>0x6F3A371</ip>
      <obj>/usr/lib64/libtcmalloc.so.4.5.9</obj>
    </frame>
    <frame>
      <ip>0x6F399E6</ip>
      <obj>/usr/lib64/libtcmalloc.so.4.5.9</obj>
    </frame>
    <frame>
      <ip>0x400A1AD</ip>
      <obj>/usr/lib64/ld-linux-x86-64.so.2</obj>
      <fn>call_init</fn>
      <dir>/usr/src/debug/glibc-2.34-54.el9.x86_64/elf</dir>
      <file>dl-init.c</file>
      <line>70</line>
    </frame>
    <frame>
      <ip>0x400A1AD</ip>
      <obj>/usr/lib64/ld-linux-x86-64.so.2</obj>
      <fn>call_init</fn>
      <dir>/usr/src/debug/glibc-2.34-54.el9.x86_64/elf</dir>
      <file>dl-init.c</file>
      <line>26</line>
    </frame>
    <frame>
      <ip>0x400A29B</ip>
      <obj>/usr/lib64/ld-linux-x86-64.so.2</obj>
      <fn>_dl_init</fn>
      <dir>/usr/src/debug/glibc-2.34-54.el9.x86_64/elf</dir>
      <file>dl-init.c</file>
      <line>117</line>
    </frame>
    <frame>
      <ip>0x4020BD9</ip>
      <obj>/usr/lib64/ld-linux-x86-64.so.2</obj>
    </frame>
    <frame>
      <ip>0xD</ip>
    </frame>
    <frame>
      <ip>0x1FFF000A96</ip>
    </frame>
    <frame>
      <ip>0x1FFF000A9E</ip>
    </frame>
    <frame>
      <ip>0x1FFF000AAE</ip>
    </frame>
    <frame>
      <ip>0x1FFF000ABC</ip>
    </frame>
    <frame>
      <ip>0x1FFF000ABF</ip>
    </frame>
    <frame>
      <ip>0x1FFF000AC8</ip>
    </frame>
    <frame>
      <ip>0x1FFF000AD2</ip>
    </frame>
    <frame>
      <ip>0x1FFF000AD7</ip>
    </frame>
    <frame>
      <ip>0x1FFF000ADA</ip>
    </frame>
    <frame>
      <ip>0x1FFF000AFA</ip>
    </frame>
    <frame>
      <ip>0x1FFF000B05</ip>
    </frame>
    <frame>
      <ip>0x1FFF000B29</ip>
    </frame>
    <frame>
      <ip>0x1FFF000B43</ip>
    </frame>
    <frame>
      <ip>0x1FFF000B77</ip>
    </frame>
  </stack>
  <auxwhat>Address 0x1fff000000 is on thread 1's stack</auxwhat>
</error>

Related issues 1 (1 open — 0 closed)