From: Hugh Dickins <hughd@google.com>
To: Prarit Bhargava <prarit@redhat.com>
Cc: Hugh Dickins <hughd@google.com>,
Morten Stevens <mstevens@fedoraproject.org>,
Daniel Wagner <wagi@monom.org>,
Dave Chinner <david@fromorbit.com>,
Eric Paris <eparis@redhat.com>,
Eric Sandeen <esandeen@redhat.com>,
Andrew Morton <akpm@linux-foundation.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: linux 4.1-rc7 deadlock
Date: Sun, 14 Jun 2015 09:44:22 -0700 (PDT) [thread overview]
Message-ID: <alpine.LSU.2.11.1506140934280.11018@eggly.anvils> (raw)
In-Reply-To: <557A089A.3090202@redhat.com>
On Thu, 11 Jun 2015, Prarit Bhargava wrote:
> On 06/11/2015 04:06 PM, Hugh Dickins wrote:
> > On Tue, 9 Jun 2015, Morten Stevens wrote:
> >> 2015-06-09 16:10 GMT+02:00 Daniel Wagner <wagi@monom.org>:
> >>> On 06/09/2015 01:54 PM, Morten Stevens wrote:
> >
> > Reported-by: Prarit Bhargava <prarit@redhat.com>
> > Reported-by: Daniel Wagner <wagi@monom.org>
> > Reported-by: Morten Stevens <mstevens@fedoraproject.org>
> > Not-Yet-Signed-off-by: Hugh Dickins <hughd@google.com>
> > ---
> >
> > mm/shmem.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > --- 4.1-rc7/mm/shmem.c 2015-04-26 19:16:31.352191298 -0700
> > +++ linux/mm/shmem.c 2015-06-11 11:08:21.042745594 -0700
> > @@ -3401,7 +3401,7 @@ int shmem_zero_setup(struct vm_area_stru
> > struct file *file;
> > loff_t size = vma->vm_end - vma->vm_start;
> >
> > - file = shmem_file_setup("dev/zero", size, vma->vm_flags);
> > + file = __shmem_file_setup("dev/zero", size, vma->vm_flags, S_PRIVATE);
>
> Perhaps,
>
> file = shmem_kernel_file_setup("dev/zero", size, vma->vm_flags) ?
Perhaps. I couldn't decide whether this is a proper intended use of
shmem_kernel_file_setup(), or a handy reuse of its flag. Andrew asked
for a comment, so in the end I left that line as is, but refer to
shmem_kernel_file_setup() in the comment. And that forced me to look a
little closer at the security implications: but we do seem to be safe.
>
> Tested-by: Prarit Bhargava <prarit@redhat.com>
Thank you: I had been hoping for some corroboration from one of the other
guys (no offence to you, but 33% looks a bit weak!), but now it's Sunday
so I think I'd better send this off in the hope that it makes -rc8.
Hugh
>
> P.
>
> > if (IS_ERR(file))
> > return PTR_ERR(file);
--
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>
prev parent reply other threads:[~2015-06-14 16:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <5576D3E7.40302@fedoraproject.org>
[not found] ` <5576F3DA.7000106@monom.org>
[not found] ` <CAKSJeFLb523beVQHqWhCtaBOECfeYrwWdojb5M8wqQWMfwJ72A@mail.gmail.com>
2015-06-11 20:06 ` linux 4.1-rc7 deadlock Hugh Dickins
2015-06-11 22:15 ` Prarit Bhargava
2015-06-14 16:44 ` Hugh Dickins [this message]
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=alpine.LSU.2.11.1506140934280.11018@eggly.anvils \
--to=hughd@google.com \
--cc=akpm@linux-foundation.org \
--cc=david@fromorbit.com \
--cc=eparis@redhat.com \
--cc=esandeen@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mstevens@fedoraproject.org \
--cc=prarit@redhat.com \
--cc=wagi@monom.org \
/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