From: Tetsuo Handa <penguin-kernel@I-love.SAKURA.ne.jp>
To: syzbot <syzbot+131d2229316b7012ac06@syzkaller.appspotmail.com>,
syzkaller-bugs@googlegroups.com
Cc: b.a.t.m.a.n@lists.open-mesh.org, jmorris@namei.org,
linux-kernel@vger.kernel.org,
linux-security-module@vger.kernel.org, netdev@vger.kernel.org,
serge@hallyn.com, Casey Schaufler <casey@schaufler-ca.com>
Subject: Re: general protection fault in smack_socket_sendmsg (2)
Date: Fri, 29 Nov 2019 18:39:49 +0900 [thread overview]
Message-ID: <ee964c66-da56-def6-9525-6d960ab9487a@I-love.SAKURA.ne.jp> (raw)
In-Reply-To: <000000000000723a32059870fbd4@google.com>
On 2019/11/29 9:05, syzbot wrote:
> rxrpc_send_keepalive+0x254/0x3c0 net/rxrpc/output.c:655
Again net/rxrpc/output.c:655
#syz dup: KMSAN: use-after-free in rxrpc_send_keepalive
prev parent reply other threads:[~2019-11-29 9:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-29 0:05 general protection fault in smack_socket_sendmsg (2) syzbot
2019-11-29 9:39 ` 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=ee964c66-da56-def6-9525-6d960ab9487a@I-love.SAKURA.ne.jp \
--to=penguin-kernel@i-love.sakura.ne.jp \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=casey@schaufler-ca.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-security-module@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=serge@hallyn.com \
--cc=syzbot+131d2229316b7012ac06@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;
as well as URLs for NNTP newsgroup(s).