关于iprute2使用ip link xstats查询发生coredump的问题

我在使用iprute2使用ip link xstats查询bond信息时遇到一个问题，当我创建bond后打算用ip link xstats命令查询bond扩展信息时发生了栈溢出接着coredump了，我并没有通过代码看出根因所以需要一些帮助，以下是我发现问题的过程

示例：
ifconfig eth1 up
modprobe bonding mode=4 max_bonds=1 lacp_rate=1 miimon=100
ip addr add 7.7.0.100/24 dev bond0
ip link xstats type bond dev bond0

结果如下：
[root@localhost /]# ip link xstats type bond
bond0
                    LACPDU Rx 0
                    LACPDU Tx 0
                    LACPDU Unknown type Rx 0
                    LACPDU Illegal Rx 0
                    Marker Rx 0
                    Marker Tx 0
                    Marker response Rx 0
                    Marker response Tx 0
                    Marker unknown type Rx 0
*** stack smashing detected ***: terminated
Aborted (core dumped)

通过valgrind的定位的结果如下：
[root@localhost /]# valgrind ip link xstats type bond dev bond0
==242893== Memcheck, a memory error detector
==242893== Copyright (C) 2002-2022, and GNU GPL'd, by Julian Seward et al.
==242893== Using Valgrind-3.22.0 and LibVEX; rerun with -h for copyright info
==242893== Command: ip link xstats type bond dev bond0
==242893==
bond0
                    LACPDU Rx 0
                    LACPDU Tx 0
                    LACPDU Unknown type Rx 0
                    LACPDU Illegal Rx 0
                    Marker Rx 0
                    Marker Tx 0
                    Marker response Rx 0
                    Marker response Tx 0
                    Marker unknown type Rx 0
*** stack smashing detected ***: terminated
==242893==
==242893== Process terminating with default action of signal 6 (SIGABRT)
==242893==    at 0x498AB5C: __pthread_kill_implementation (pthread_kill.c:44)
==242893==    by 0x493CF45: raise (raise.c:26)
==242893==    by 0x492733B: abort (abort.c:79)
==242893==    by 0x49281A8: __libc_message.cold (libc_fatal.c:152)
==242893==    by 0x4A1621A: __fortify_fail (fortify_fail.c:24)
==242893==    by 0x4A17435: __stack_chk_fail (stack_chk_fail.c:24)
==242893==    by 0x157A81: bond_print_stats_attr (iplink_bond.c:877)
==242893==    by 0x157B02: bond_print_xstats (iplink_bond.c:895)
==242893==    by 0x1846A9: rtnl_dump_filter_l (libnetlink.c:926)
==242893==    by 0x185A01: rtnl_dump_filter_nc (libnetlink.c:969)
==242893==    by 0x16B0BF: iplink_ifla_xstats (iplink_xstats.c:71)
==242893==    by 0x118C3C: do_cmd (ip.c:131)
==242893==
==242893== HEAP SUMMARY:
==242893==     in use at exit: 33,878 bytes in 4 blocks
==242893==   total heap usage: 8 allocs, 4 frees, 66,755 bytes allocated
==242893==
==242893== LEAK SUMMARY:
==242893==    definitely lost: 0 bytes in 0 blocks
==242893==    indirectly lost: 0 bytes in 0 blocks
==242893==      possibly lost: 0 bytes in 0 blocks
==242893==    still reachable: 33,878 bytes in 4 blocks
==242893==         suppressed: 0 bytes in 0 blocks
==242893== Rerun with --leak-check=full to see details of leaked memory
==242893==
==242893== For lists of detected and suppressed errors, rerun with: -s
==242893== ERROR SUMMARY: 0 errors from 0 contexts (suppressed: 0 from 0)
Aborted (core dumped)

通过gdb调试，在bond_print_stats_attr这个函数执行完毕后触发了__stack_chk_fail
这个问题我最先在6.6.0版本发现，替换了最新的6.15.0版本后发现仍然有这个问题，我还尝试了5.15.0版本，发现是正常的
因此我怀疑有一些修改触发了这个问题，但我不能确定问题根因，希望得到帮助

src-openEuler/iproute

内容风险标识

评论 (1)

src-openEuler/iproute .gitee-modal { width: 500px !important; }

内容风险标识