From: Mark Rutland <mark.rutland@arm.com>
To: Hillf Danton <hdanton@sina.com>
Cc: syzbot <syzbot+09329bd987ebca21bced@syzkaller.appspotmail.com>,
john.fastabend@gmail.com, linux-kernel@vger.kernel.org,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com,
Robin Murphy <robin.murphy@arm.com>
Subject: Re: [syzbot] kernel stack overflow in sock_close
Date: Fri, 9 Dec 2022 14:19:34 +0000 [thread overview]
Message-ID: <Y5ND9qNFXOxOuEMQ@FVFF77S0Q05N> (raw)
In-Reply-To: <20221209133214.1934-1-hdanton@sina.com>
On Fri, Dec 09, 2022 at 09:32:14PM +0800, Hillf Danton wrote:
> On 9 Dec 2022 13:15:39 +0000 Mark Rutland <mark.rutland@arm.com>
> > On Thu, Dec 08, 2022 at 02:05:36AM -0800, syzbot wrote:
> > > Hello,
> > >
> > > syzbot found the following issue on:
> > >
> > > HEAD commit: e3cb714fb489 Merge branch 'for-next/core' into for-kernelci
> >
> > This commit has a known-broken parent where some uaccess copies appeared to
> > result in stack corruption:
> >
> > https://lore.kernel.org/linux-arm-kernel/Y44gVm7IEMXqilef@FVFF77S0Q05N.cambridge.arm.com/
> >
> > ... which has now been dropped from the arm64 for-next/core branch, but
> > anything found on commit e3cb714fb489 will be suspect due to that.
> >
> > This *might* a manifestation of the same issue; I'll have a go at reproducing
> > it locally.
>
> Take a look at the reproducer [1] before kicking off your Harley.
>
> [1] https://lore.kernel.org/lkml/00000000000073b14905ef2e7401@google.com/
Ah, yes; this is clearly not arm64-specific, and therefore has
nothing to do with the uaccess issue.
Sorry for the noise, and thanks for the pointer!
Mark.
prev parent reply other threads:[~2022-12-09 14:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-08 10:05 [syzbot] kernel stack overflow in sock_close syzbot
2022-12-09 13:15 ` Mark Rutland
[not found] ` <20221209133214.1934-1-hdanton@sina.com>
2022-12-09 14:19 ` Mark Rutland [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Y5ND9qNFXOxOuEMQ@FVFF77S0Q05N \
--to=mark.rutland@arm.com \
--cc=hdanton@sina.com \
--cc=john.fastabend@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=robin.murphy@arm.com \
--cc=syzbot+09329bd987ebca21bced@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox