From: Oleg Nesterov <oleg@redhat.com>
To: "Toralf Förster" <toralf.foerster@gmx.de>,
"Andrey Vagin" <avagin@openvz.org>
Cc: "Serge E. Hallyn" <serue@us.ibm.com>,
"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, 28 Jul 2013 19:58:28 +0200 [thread overview]
Message-ID: <20130728175828.GA15020@redhat.com> (raw)
In-Reply-To: <51F5381D.1080904@gmx.de>
On 07/28, Toralf Förster wrote:
>
> The attached patch works - applied on top of current git -
> at least the issue cannot be reproduced then.
Thanks Toralf.
I'll write the changelog and send the patch tomorrow.
Andrey, any chance you can check that with this patch free_ipc_ns()
doesn't have any problem with ->shm_file ?
e7b2c406 should be enough to fix that leak, but it would be nice if
you can confirm.
> On 07/27/2013 07:00 PM, Oleg Nesterov wrote:
> > On 07/27, Toralf Förster wrote:
> >>
> >> I do have a user mode linux image (stable 32 bit Gentoo Linux ) which erratically crashes
> >> while fuzz tested with trinity if the victim files are located on a NFS share.
> >>
> >> The back trace of the core dumps always looks like the attached.
> >>
> >> To bisect it is hard. However after few attempts in the last weeks the following
> >> commit is either the first bad commit or at least the upper limit (less likely).
> >>
> >>
> >> commit 8aac62706adaaf0fab02c4327761561c8bda9448
> >> Author: Oleg Nesterov <oleg@redhat.com>
> >> Date: Fri Jun 14 21:09:49 2013 +0200
> >>
> >> move exit_task_namespaces() outside of exit_notify()
> >>
> >> #15 nlmclnt_setlockargs (req=0x48e18860, fl=0x48f27c8c) at fs/lockd/clntproc.c:131
> >
> > Thanks.
> >
> > 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();
> >
> >
> >
>
>
> --
> MfG/Sincerely
> Toralf Förster
> pgp finger print: 7B1A 07F4 EC82 0F90 D4C2 8936 872A E508 7DB6 9DA3
next prev parent reply other threads:[~2013-07-28 18:03 UTC|newest]
Thread overview: 21+ 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 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 [this message]
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
-- 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=20130728175828.GA15020@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 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).