From: Greg KH <gregkh@linuxfoundation.org>
To: Mark <zxm927@163.com>
Cc: linux-fsdevel@vger.kernel.org
Subject: Re: Can I move a kernel thread into a special mount namespace
Date: Sun, 13 Nov 2016 10:43:32 +0100 [thread overview]
Message-ID: <20161113094332.GA20134@kroah.com> (raw)
In-Reply-To: <c944717e-dd0a-db52-fb3c-109f1da0d25e@163.com>
On Sun, Nov 13, 2016 at 04:50:09PM +0800, Mark wrote:
>
>
> On 2016/10/26 20:31, Greg KH Wrote:
> > On Sun, Oct 16, 2016 at 07:18:43PM +0800, Mark wrote:
> > > Hi,
> > >
> > > Our requirement is, a user process sends a command to a kernel (3.10)
> > > module, and the kernel module creates a kernel thread, which has to be
> > > in same mount space with the user process since they have to access a
> > > same path, which is not mounted in root namespace. But seems all kernel
> > > threads have one parent "threadd", which is in root name space.
> >
> > Very odd requirement, do you have a pointer to your code anywhere? What
> > exactly will that kernel thread do?
> >
> > And why use such an obsolete and old kernel version?
> >
> > thanks,
> >
> > greg k-h
> >
>
> The kernel thread checks a file and if it exists then do something, but
> the file is created in a separate namespace. Is this an odd requirement?
Yes, why should the kernel care about a file, the kernel should never be
reading files directly from userspace.
> I cannot post the code.
Why not? You have our code, why can't you post yours? :)
> It's on an android release so kernel is 3.10. Is there a solution on a
> newer kernel release?
I don't understand the problem you are trying to solve, can you perhaps
explain the issue, not the potential solution you are trying to use?
That would make it easier to understand.
thanks,
greg k-h
prev parent reply other threads:[~2016-11-13 9:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-16 11:18 Can I move a kernel thread into a special mount namespace Mark
2016-10-26 12:31 ` Greg KH
2016-11-13 8:50 ` Mark
2016-11-13 9:43 ` Greg KH [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=20161113094332.GA20134@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=zxm927@163.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.