From: Oleg Nesterov <oleg@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
Andrey Vagin <avagin@openvz.org>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Al Viro <viro@zeniv.linux.org.uk>,
Linux NFS mailing list <linux-nfs@vger.kernel.org>
Subject: Re: fuzz tested user mode linux core dumps in fs/lockd/clntproc.c:131
Date: Sun, 22 Sep 2013 19:52:56 +0200 [thread overview]
Message-ID: <20130922175256.GA18473@redhat.com> (raw)
In-Reply-To: <523F22EA.2050609@gmx.de>
On 09/22, Toralf Förster wrote:
>
> On 07/27/2013 07:00 PM, Oleg Nesterov wrote:
> >
> > So nlmclnt_setlockargs()->utsname() crashes and we probably need
> > the patch below.
> >
> > But is it correct? I know _absolutely_ nothing about nfs/sunrpc/etc and
> > I never looked into this code before, most probably I am wrong.
> >
> > But it seems that __nlm_async_call() relies on workqueues.
> > nlmclnt_async_call() does rpc_wait_for_completion_task(), but what if
> > the caller is killed?
> >
> > nlm_rqst can't go away, ->a_count was incremented. But can't the caller
> > exit before call->name is used? In this case the memory it points to
> > can be already freed.
> >
> > Oleg.
> >
> > --- x/kernel/exit.c
> > +++ x/kernel/exit.c
> > @@ -783,8 +783,8 @@ void do_exit(long code)
> > exit_shm(tsk);
> > exit_files(tsk);
> > exit_fs(tsk);
> > - exit_task_namespaces(tsk);
> > exit_task_work(tsk);
> > + exit_task_namespaces(tsk);
> > check_stack_usage();
> > exit_thread();
> >
> >
> >
> /me wonders if/when this will go in the main kernel ?
I think this was fixed by 9a1b6bf818e74 ?
Oleg.
next prev parent reply other threads:[~2013-09-22 17:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-27 10:03 fuzz tested user mode linux core dumps in fs/lockd/clntproc.c:131 Toralf Förster
2013-07-27 13:18 ` [uml-devel] Fwd: " Toralf Förster
2013-07-27 17:00 ` Oleg Nesterov
2013-07-27 17:27 ` Oleg Nesterov
2013-07-28 15:26 ` Toralf Förster
2013-07-28 17:58 ` Oleg Nesterov
2013-07-28 18:56 ` [uml-devel] Fwd: " Toralf Förster
2013-07-28 18:56 ` Toralf Förster
2013-07-29 6:29 ` Andrew Vagin
2013-07-29 13:10 ` Oleg Nesterov
2013-07-29 14:27 ` Andrew Vagin
2013-07-29 14:51 ` Oleg Nesterov
2013-07-29 15:43 ` Andrey Vagin
2013-07-29 0:10 ` Eric W. Biederman
2013-07-29 0:32 ` Eric W. Biederman
2013-07-29 14:17 ` Oleg Nesterov
2013-07-29 17:42 ` fuzz tested user mode linux core dumps in fs/lockd/clntproc.c:131 (nfs in a netns utsns problems?) Eric W. Biederman
2013-07-29 18:03 ` Oleg Nesterov
2013-07-29 18:17 ` Eric W. Biederman
2013-07-30 21:12 ` J. Bruce Fields
2013-07-30 21:20 ` Myklebust, Trond
2013-09-22 17:03 ` fuzz tested user mode linux core dumps in fs/lockd/clntproc.c:131 Toralf Förster
2013-09-22 17:52 ` Oleg Nesterov [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-07-27 9:53 Toralf Förster
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=20130922175256.GA18473@redhat.com \
--to=oleg@redhat.com \
--cc=avagin@openvz.org \
--cc=ebiederm@xmission.com \
--cc=linux-nfs@vger.kernel.org \
--cc=serue@us.ibm.com \
--cc=toralf.foerster@gmx.de \
--cc=viro@zeniv.linux.org.uk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.