From: Al Viro <viro@zeniv.linux.org.uk>
To: Christian Brauner <christian@brauner.io>
Cc: syzbot+002e636502bc4b64eb5c@syzkaller.appspotmail.com,
jannh@google.com, akpm@linux-foundation.org,
arunks@codeaurora.org, ebiederm@xmission.com,
elena.reshetova@intel.com, gregkh@linuxfoundation.org,
guro@fb.com, ktsanaktsidis@zendesk.com,
linux-kernel@vger.kernel.org, mhocko@suse.com, mingo@kernel.org,
peterz@infradead.org, riel@surriel.com, rppt@linux.vnet.ibm.com,
scuttimmy@gmail.com, syzkaller-bugs@googlegroups.com,
tglx@linutronix.de, willy@infradead.org, yuehaibing@huawei.com
Subject: Re: [PATCH] fork: return proper negative error code
Date: Mon, 1 Jul 2019 17:26:30 +0100 [thread overview]
Message-ID: <20190701162629.GZ17978@ZenIV.linux.org.uk> (raw)
In-Reply-To: <20190701144808.6804-1-christian@brauner.io>
On Mon, Jul 01, 2019 at 04:48:08PM +0200, Christian Brauner wrote:
> Make sure to return a proper negative error code from copy_process()
> when anon_inode_getfile() fails with CLONE_PIDFD.
Acked-by: Al Viro <viro@zeniv.linux.org.uk>
next prev parent reply other threads:[~2019-07-01 16:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-01 13:17 general protection fault in get_task_pid syzbot
2019-07-01 13:32 ` Christian Brauner
2019-07-01 14:48 ` [PATCH] fork: return proper negative error code Christian Brauner
2019-07-01 14:50 ` Christian Brauner
2019-07-01 16:26 ` Al Viro [this message]
2019-07-01 16:15 ` [GIT PULL] fixes for v5.2-rc8 Christian Brauner
2019-07-03 8:20 ` pr-tracker-bot
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=20190701162629.GZ17978@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=akpm@linux-foundation.org \
--cc=arunks@codeaurora.org \
--cc=christian@brauner.io \
--cc=ebiederm@xmission.com \
--cc=elena.reshetova@intel.com \
--cc=gregkh@linuxfoundation.org \
--cc=guro@fb.com \
--cc=jannh@google.com \
--cc=ktsanaktsidis@zendesk.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=riel@surriel.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=scuttimmy@gmail.com \
--cc=syzbot+002e636502bc4b64eb5c@syzkaller.appspotmail.com \
--cc=syzkaller-bugs@googlegroups.com \
--cc=tglx@linutronix.de \
--cc=willy@infradead.org \
--cc=yuehaibing@huawei.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
all inboxes | Powered by JetHome®