Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
MIME-Version: 1.0
References: <CANX2M5Yphi3JcCsMf3HgPPkk9XCfOKO85gyMdxQf3_O74yc1Hg@mail.gmail.com>
 <Ytzy9IjGXziLaVV0@kroah.com> <CANX2M5bxA5FF2Z8PFFc2p-OxkhOJQ8y=8PGF1kdLsJo+C92_gQ@mail.gmail.com>
 <Yt1MX1Z6z0y82i1I@kroah.com>
In-Reply-To: <Yt1MX1Z6z0y82i1I@kroah.com>
From:   Dipanjan Das <mail.dipanjan.das@gmail.com>
Date:   Thu, 28 Jul 2022 12:24:59 -0700
Message-ID: <CANX2M5aX=JnKD-8kPyAN0Q64HvLoSO+3LvNvuaxkexCgeDWZHA@mail.gmail.com>
Subject: Re: general protection fault in sock_def_error_report
To:     Greg KH <gregkh@linuxfoundation.org>
Cc:     davem@davemloft.net, ast@kernel.org, daniel@iogearbox.net,
        kafai@fb.com, songliubraving@fb.com, yhs@fb.com, andriin@fb.com,
        sashal@kernel.org, edumazet@google.com,
        steffen.klassert@secunet.com, netdev@vger.kernel.org,
        linux-kernel@vger.kernel.org, bpf@vger.kernel.org,
        syzkaller@googlegroups.com, fleischermarius@googlemail.com,
        its.priyanka.bose@gmail.com
Content-Type: text/plain; charset="UTF-8"
Precedence: bulk

On Sun, Jul 24, 2022 at 6:43 AM Greg KH <gregkh@linuxfoundation.org> wrote:
>
> It is worth the effort if the problem is still in the latest kernel
> release as that is the only place that new development happens.

The problem does not exist in the latest release.

> If the issue is not reproducible on Linus's current releases, then finding the
> change that solved the problem is also good so that we can then backport
> it to the stable/long term kernel release for everyone to benefit from.

The change that solved the issue in the mainline is this:
341adeec9adad0874f29a0a1af35638207352a39

Here is one additional piece of information that you may find useful.
Though we originally reported the bug for the longterm release
v5.4.206, we noticed that the same issue exists in another longterm
release v5.10.131, too. We manually bisected the commits in those two
longterm branches to find the bug-introducing commits. We observe that
the commits d6e981ec9491be5ec46d838b1151e7edefe607f5 and
ff6eeb627898c179aac421af5d6515d3f50b84df introduced the bug in 5.4.y
and 5.10.y branches, respectively.

-- 
Thanks and Regards,

Dipanjan