LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Oleg Nesterov <oleg@redhat.com>
To: Tycho Andersen <tycho@tycho.ws>
Cc: Kees Cook <keescook@chromium.org>,
Andy Lutomirski <luto@amacapital.net>,
"Eric W . Biederman" <ebiederm@xmission.com>,
"Serge E . Hallyn" <serge@hallyn.com>,
Christian Brauner <christian@brauner.io>,
Tyler Hicks <tyhicks@canonical.com>,
Akihiro Suda <suda.akihiro@lab.ntt.co.jp>,
Aleksa Sarai <asarai@suse.de>,
linux-kernel@vger.kernel.org,
containers@lists.linux-foundation.org, linux-api@vger.kernel.org
Subject: Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace
Date: Thu, 1 Nov 2018 14:56:34 +0100 [thread overview]
Message-ID: <20181101135633.GB23232@redhat.com> (raw)
In-Reply-To: <20181029224031.29809-2-tycho@tycho.ws>
On 10/29, Tycho Andersen wrote:
>
> +static int seccomp_notify_release(struct inode *inode, struct file *file)
> +{
> + struct seccomp_filter *filter = file->private_data;
> + struct seccomp_knotif *knotif;
> +
> + mutex_lock(&filter->notify_lock);
> +
> + /*
> + * If this file is being closed because e.g. the task who owned it
> + * died, let's wake everyone up who was waiting on us.
> + */
> + list_for_each_entry(knotif, &filter->notif->notifications, list) {
> + if (knotif->state == SECCOMP_NOTIFY_REPLIED)
> + continue;
> +
> + knotif->state = SECCOMP_NOTIFY_REPLIED;
> + knotif->error = -ENOSYS;
> + knotif->val = 0;
> +
> + complete(&knotif->ready);
> + }
> +
> + wake_up_all(&filter->notif->wqh);
Why? __fput() is not possible if there is another user of this file sleeping
in seccomp_notify_poll().
> + kfree(filter->notif);
Hmm, this looks wrong... we can't kfree ->notif if its ->notifications list
is not empty, otherwise seccomp_do_user_notification()->list_del(&n.list)
can write to the freed memory.
I think _release() should do list_for_each_entry_safe() + list_del_init()
and seccomp_do_user_notification() should use list_del_init() too.
Or, simpler, seccomp_do_user_notification() should do
if (!match->notif)
goto out;
instead of "goto remove_list".
Oleg.
next prev parent reply other threads:[~2018-11-01 13:56 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 22:40 [PATCH v8 0/2] seccomp " Tycho Andersen
2018-10-29 22:40 ` [PATCH v8 1/2] seccomp: add a return code to " Tycho Andersen
2018-10-30 14:32 ` Oleg Nesterov
2018-10-30 15:32 ` Tycho Andersen
2018-11-01 14:48 ` Oleg Nesterov
2018-11-01 20:33 ` Tycho Andersen
2018-11-02 11:29 ` Oleg Nesterov
2018-11-02 13:50 ` Tycho Andersen
2018-10-30 15:02 ` Oleg Nesterov
2018-10-30 15:54 ` Tycho Andersen
2018-10-30 16:27 ` Oleg Nesterov
2018-10-30 16:39 ` Oleg Nesterov
2018-10-30 17:21 ` Tycho Andersen
2018-10-30 21:32 ` Kees Cook
2018-10-31 13:04 ` Oleg Nesterov
2018-10-30 21:38 ` Kees Cook
2018-10-30 21:49 ` Kees Cook
2018-10-30 21:54 ` Tycho Andersen
2018-10-30 22:00 ` Kees Cook
2018-10-30 22:32 ` Tycho Andersen
2018-10-30 22:34 ` Kees Cook
2018-10-31 0:29 ` Tycho Andersen
2018-10-31 1:29 ` Kees Cook
2018-11-01 13:40 ` Oleg Nesterov
2018-11-01 19:56 ` Tycho Andersen
2018-11-02 10:02 ` Oleg Nesterov
2018-11-02 13:38 ` Tycho Andersen
2018-11-01 13:56 ` Oleg Nesterov [this message]
2018-11-01 19:58 ` Tycho Andersen
2018-11-29 23:08 ` Tycho Andersen
2018-11-30 10:17 ` Oleg Nesterov
2018-10-29 22:40 ` [PATCH v8 2/2] samples: add an example of seccomp user trap Tycho Andersen
2018-10-29 23:31 ` Serge E. Hallyn
2018-10-30 2:05 ` Tycho Andersen
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=20181101135633.GB23232@redhat.com \
--to=oleg@redhat.com \
--cc=asarai@suse.de \
--cc=christian@brauner.io \
--cc=containers@lists.linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=keescook@chromium.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=luto@amacapital.net \
--cc=serge@hallyn.com \
--cc=suda.akihiro@lab.ntt.co.jp \
--cc=tycho@tycho.ws \
--cc=tyhicks@canonical.com \
--subject='Re: [PATCH v8 1/2] seccomp: add a return code to trap to userspace' \
/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
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).