Fix Linux 6.5 support to avoid fortify panic #948
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello,
I believe this patch is a fix for issue #937 where fortify causes a panic in
tc_configure()
due to a "detected buffer overflow in strcpy". Thenlattr *
is set to&nlreq.hdr
which has a fixed size causing the overflow. By settingnlattr *
to&nlreq
instead, the code sees the 100 bytebuf
space and does not panic. I tested this on kernel 6.5.0-21 and verified theqdisc
name was properly set by usingtc
. With the fix I could runpkt-gen
on multiple emulated netmap interfaces without seeing a panic.While here I removed a duplicate
strcpy()
innetmap_sink_init()
. I assumed "nmsink" is preferred to "nmsink%d".