From: Andrea Arcangeli <aarcange@redhat.com>
To: Andrew Morton <akpm@linux-foundation.org>,
Eric Biggers <ebiggers3@gmail.com>
Cc: Mike Rapoport <rppt@linux.vnet.ibm.com>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org,
viro@zeniv.linux.org.uk, linux-mm@kvack.org,
syzkaller-bugs@googlegroups.com
Subject: [PATCH 0/1] Re: kernel BUG at fs/userfaultfd.c:LINE!
Date: Sat, 23 Dec 2017 01:25:04 +0100 [thread overview]
Message-ID: <20171223002505.593-1-aarcange@redhat.com> (raw)
In-Reply-To: <20171222222346.GB28786@zzz.localdomain>
Hello,
Thanks for the CC, I'm temporarily very busy so if there's something
urgent, safer to CC.
This passed both testcases, the hard part was already done. I'm glad
there was nothing wrong in the previous fix that had to be redone.
Simply we forgot to undo the vma->vm_userfaultfd_ctx = NULL after
aborting the new child uffd ctx, the original code of course didn't do
that either.
Having just seen this issue, this isn't very well tested.
Thank you,
Andrea
Andrea Arcangeli (1):
userfaultfd: clear the vma->vm_userfaultfd_ctx if UFFD_EVENT_FORK
fails
fs/userfaultfd.c | 20 ++++++++++++++++++--
1 file changed, 18 insertions(+), 2 deletions(-)
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2017-12-23 0:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 21:37 kernel BUG at fs/userfaultfd.c:LINE! syzbot
2017-12-22 22:23 ` Eric Biggers
2017-12-23 0:25 ` Andrea Arcangeli [this message]
2017-12-23 0:25 ` [PATCH 1/1] userfaultfd: clear the vma->vm_userfaultfd_ctx if UFFD_EVENT_FORK fails Andrea Arcangeli
2017-12-25 9:07 ` Mike Rapoport
2017-12-23 7:31 ` [PATCH 0/1] Re: kernel BUG at fs/userfaultfd.c:LINE! Dmitry Vyukov
2018-01-17 8:56 ` Pavel Machek
2018-01-17 23:26 ` Eric Biggers
2018-01-18 8:24 ` Pavel Machek
2018-01-31 1:31 ` Eric Biggers
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=20171223002505.593-1-aarcange@redhat.com \
--to=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=ebiggers3@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rppt@linux.vnet.ibm.com \
--cc=syzkaller-bugs@googlegroups.com \
--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).