From: Tejun Heo <tj@kernel.org>
To: Ben Greear <greearb@candelatech.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Deadlock related to file permissions and/or cgroup, 4.4.6+
Date: Wed, 13 Apr 2016 15:00:25 -0400 [thread overview]
Message-ID: <20160413190025.GJ3676@htj.duckdns.org> (raw)
In-Reply-To: <5706D84D.6070706@candelatech.com>
Hello,
On Thu, Apr 07, 2016 at 02:59:41PM -0700, Ben Greear wrote:
> This is from a modified 4.4.6+ kernel, with local patches. Git tree found
> below, but I don't think this lockup is related to any local changes we have made.
>
> http://dmz2.candelatech.com/?p=linux-4.4.dev.y/.git;a=summary
>
> The test case involves using a libcurl based application that
> is making an ftp request to a second port on the same machine.
> vsftp is serving up the ftp file.
> The ports are looped together with an ethernet cable, and routing rules
> are set up so that traffic flows over the external interface.
>
> The key change from a working solution and kernel deadlock, is that
> with the file-to-be-read has permissions 700, it fails, but 600
> does not. (As I was writing this up, our system-test guy managed to
> lock it up with 600 permissions as well, so it is not *just* related to
> permission 700).
>
> This is very repeatable permissions 700.
>
> The tainting probably comes from a warning in another (GPL, but out-of-tree module that we write),
> but very unlikely that has anything to do with this issue.
Can you please try to reproduce the problem with lockdep turned on and
without the out-of-tree module? Lockdep should be able to point to
where the actual deadlock is happening.
Thanks.
--
tejun
prev parent reply other threads:[~2016-04-13 19:00 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-07 21:59 Deadlock related to file permissions and/or cgroup, 4.4.6+ Ben Greear
2016-04-13 19:00 ` Tejun Heo [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=20160413190025.GJ3676@htj.duckdns.org \
--to=tj@kernel.org \
--cc=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).