[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <45b601aebda1225b38b62c95b2c12e0fce76ee80.camel@redhat.com>
Date: Thu, 13 Oct 2022 13:13:58 +0200
From: Paolo Abeni <pabeni@...hat.com>
To: shaozhengchao <shaozhengchao@...wei.com>,
netdev <netdev@...r.kernel.org>
Cc: Jakub Kicinski <kuba@...nel.org>,
David Miller <davem@...emloft.net>, edumazet@...gle.com,
sgarzare@...hat.com, ast@...nel.org, nikolay@...dia.com,
mkl@...gutronix.de, cong.wang@...edance.com
Subject: Re: net/kcm: syz issue about general protection fault in skb_unlink
On Thu, 2022-10-13 at 18:51 +0800, shaozhengchao wrote:
> I found that the syz issue("general protection fault in skb_unlink")
> still happen in Linux -next branch.
> commit: 082fce125e57cff60687181c97f3a8ee620c38f5
> Link:
> https://groups.google.com/g/syzkaller-bugs/c/ZfR2B5KaQrA/m/QfnGHCYSBwAJ
> Please ask:
> Is there any problem with this patch? Why is this patch not merged into
> the Linux -next branch or mainline?
I never submitted the patch formally. So much time has passed that I
don't recall exactly why. Possibly the patch fell outside my radar
after hitting a syzkaller infrastructure issue.
Apart from that, the patch is quite invasinve, especially for a
subsystem with no selftest and that I don't know particularly well.
As a possible option I can try to post it for net-next, when it will
re-open - assuming there is agreement on that.
Cheers,
Paolo
Powered by blists - more mailing lists