From: Tejun Heo <tj@kernel.org>
To: Sasha Levin <sasha.levin@oracle.com>
Cc: Greg KH <greg@kroah.com>, LKML <linux-kernel@vger.kernel.org>
Subject: Re: kernfs: possible deadlock between of->mutex and mmap_sem
Date: Mon, 3 Mar 2014 17:46:09 -0500 [thread overview]
Message-ID: <20140303224609.GF26523@mtj.dyndns.org> (raw)
In-Reply-To: <531505E4.8020802@oracle.com>
On Mon, Mar 03, 2014 at 05:44:52PM -0500, Sasha Levin wrote:
> >>I'll send a patch to fix it some time next week unless someone beats me to it :)
> >
> >How are you planning to fix it? Prolly the right thing to do would be
> >caching atomic_write_len in open_file and copy data before grabbing
> >any locks.
>
> I've actually didn't have a plan when I wrote that, was just
> planning on putting effort into it.
I'll prolly work on it tomorrow unless you beat me to it. :)
Thanks.
--
tejun
next prev parent reply other threads:[~2014-03-03 22:46 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-01 1:14 kernfs: possible deadlock between of->mutex and mmap_sem Sasha Levin
2014-03-01 23:18 ` Dave Chinner
2014-03-03 22:39 ` Tejun Heo
2014-03-03 22:44 ` Sasha Levin
2014-03-03 22:46 ` Tejun Heo [this message]
2014-03-04 20:38 ` [PATCH driver-core-next] kernfs: cache atomic_write_len in kernfs_open_file Tejun Heo
2014-03-05 2:50 ` Greg KH
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=20140303224609.GF26523@mtj.dyndns.org \
--to=tj@kernel.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sasha.levin@oracle.com \
/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