From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot <syzbot+314db21f0d5c1f53856c@syzkaller.appspotmail.com>,
netdev@vger.kernel.org, syzkaller-bugs@googlegroups.com
Cc: andriin@fb.com, anton@enomsg.org, ast@kernel.org,
bpf@vger.kernel.org, ccross@android.com, daniel@iogearbox.net,
eparis@parisplace.org, kafai@fb.com, keescook@chromium.org,
linux-kernel@vger.kernel.org, paul@paul-moore.com,
sds@tycho.nsa.gov, selinux@vger.kernel.org,
songliubraving@fb.com, tony.luck@intel.com, yhs@fb.com
Subject: Re: general protection fault in selinux_socket_sendmsg (2)
Date: Tue, 26 Nov 2019 07:03:51 +0900 [thread overview]
Message-ID: <2340a1a3-37cf-5f55-1f9a-9052a557f579@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <0000000000006c9f4e059830c33c@google.com>
On 2019/11/26 4:28, syzbot wrote:
> Hello,
>
> syzbot found the following crash on:
>
> HEAD commit: 6b8a7946 Merge tag 'for_linus' of git://git.kernel.org/pub..
> git tree: upstream
> console output: https://syzkaller.appspot.com/x/log.txt?x=1680ab8ce00000
> kernel config: https://syzkaller.appspot.com/x/.config?x=4737c15fc47048f2
> dashboard link: https://syzkaller.appspot.com/bug?extid=314db21f0d5c1f53856c
> compiler: gcc (GCC) 9.0.0 20181231 (experimental)
>
> Unfortunately, I don't have any reproducer for this crash yet.
Original bug has syz reproducer.
>
> IMPORTANT: if you fix the bug, please add the following tag to the commit:
> Reported-by: syzbot+314db21f0d5c1f53856c@syzkaller.appspotmail.com
>
net/rxrpc/output.c:655
#syz dup: KMSAN: use-after-free in rxrpc_send_keepalive
prev parent reply other threads:[~2019-11-25 22:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-25 19:28 general protection fault in selinux_socket_sendmsg (2) syzbot
2019-11-25 22:03 ` Tetsuo Handa [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=2340a1a3-37cf-5f55-1f9a-9052a557f579@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=andriin@fb.com \
--cc=anton@enomsg.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=ccross@android.com \
--cc=daniel@iogearbox.net \
--cc=eparis@parisplace.org \
--cc=kafai@fb.com \
--cc=keescook@chromium.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=paul@paul-moore.com \
--cc=sds@tycho.nsa.gov \
--cc=selinux@vger.kernel.org \
--cc=songliubraving@fb.com \
--cc=syzbot+314db21f0d5c1f53856c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tony.luck@intel.com \
--cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).