Skip to content

Protect from GCC garbage input in GCOV

Leon Romanovsky lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest4 patches 12 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/4gcov: Open-code kmemdup() to work correctly with kernel and user space pointerskernel/gcov/gcc_4_7.c+4 -45 replies
2/4gcov: Use proper duplication routine for const pointerkernel/gcov/gcc_4_7.c+2 -22 replies
3/4gcov: Protect from uninitialized number of functions provided by GCC 10.2kernel/gcov/gcc_4_7.c+3 -21 reply
4/4gcov: Don't print out-of-memory print for all failed fileskernel/gcov/fs.c+3 -20 replies

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.

Read the v1 thread

Cover letter [PATCH -rc 0/4] Protect from GCC garbage input in GCOV

From: Leon Romanovsky <[email protected]>

Hi Linus,

Both Colin in Ubuntu [1] and I in FC 32 are having same kernel crashes while GCOV is enabled. The reason to it that n_fuction variable that should be provided by GCC is not initialized (or wrongly set).

This patch is based on the RFC [2] which I sent to gather feedback, but didn't get any response, so sending it to you in proper -rc format.

Bottom line, GCOV is broken on GCC 10.2.

Thanks

[1] https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1891288
[2] https://lore.kernel.org/lkml/[email protected]

Leon Romanovsky (4):
gcov: Open-code kmemdup() to work correctly with kernel and user space
pointers
gcov: Use proper duplication routine for const pointer
gcov: Protect from uninitialized number of functions provided by GCC

    10.2

gcov: Don't print out-of-memory print for all failed files

 kernel/gcov/fs.c      |  5 +++--
 kernel/gcov/gcc_4_7.c | 17 +++++++++--------
 2 files changed, 12 insertions(+), 10 deletions(-)

--
2.26.2