Using size of sk_psock as the size for kcm_psock_cache size no longer
reproduces the issue. There might be a better way to solve this issue
though so I would like to ask for feedback.
Reported-and-tested-by: [email protected]
Link: https://syzkaller.appspot.com/bug?extid=1fa91bcd05206ff8cbb5
Khalid Masum (1):
net: kcm: Use sk_psock size for kcm_psock_cache
net/kcm/kcmsock.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.36.1