From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Oren Laadan <orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
Cc: Linux Containers <containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org>
Subject: Re: [RFC] cr: pty: don't use required_id, change ptmx_open()
Date: Tue, 8 Sep 2009 14:51:31 -0500 [thread overview]
Message-ID: <20090908195131.GA23683@us.ibm.com> (raw)
In-Reply-To: <4AA69EEB.9040706-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
Quoting Oren Laadan (orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org):
> > + file = alloc_file(nd.path.mnt, ptmxdentry, FMODE_READ|FMODE_WRITE, &tty_fops);
> > + path_put(&nd.path);
> > + if (!file) {
> > + dput(ptmxdentry);
> > + return ERR_PTR(-EINVAL);
> > + }
> > +
> > + ret = security_dentry_open(file, current_cred());
> > + if (ret) {
> > + fput(file);
> > + return ERR_PTR(ret);
> > + }
> > + /* check write access perms to file */
>
> I bet the above can be done by reusing lookup and __dentry_open()
> functions from fs/open.c and fs/namei.c ...
With lookup_create()? Hmm, yeah - I think there are reasons I can't do
that, but I'll just try and see where it gets us.
> > +
> > + lock_kernel(); /* tty_open does it... */
> > + ret = open_create_pty(fdir, h->index, file);
> > + unlock_kernel();
> > + if (ret) {
> > + fput(file);
> > + return ERR_PTR(ret);
> > + }
> > + ckpt_debug("master file %p (obj %d)\n", file, h->file_objref);
> > +
> > + /*
> > + * Add file to objhash to ensure proper cleanup later
> > + * (it isn't referenced elsewhere). Use h->file_objref
> > + * which was explicitly during checkpoint for this.
> > + */
> > + ret = ckpt_obj_insert(ctx, file, h->file_objref, CKPT_OBJ_FILE);
> > + if (ret < 0) {
> > + fput(file);
> > + return ERR_PTR(ret);
> > + }
>
> Can do this in caller. So
>
> > +
> > + tty = file->private_data;
> > + fput(file); /* objhash took a ref */
> > +
> > + return tty;
> > +}
> > +
> > +struct tty_struct *pty_open_by_master(struct ckpt_ctx *ctx,
> > + struct ckpt_hdr_tty *h)
> > +{
> > + struct file *fdir;
> > + struct tty_struct *tty;
> > + /*
> > + * we need to pick a way to specify which devpts
> > + * mountpoint to use. For now, we'll just use
> > + * whatever /dev/ptmx points to
> > + */
> > + fdir = filp_open("/dev/pts", O_RDONLY, 0);
> > + if (IS_ERR(fdir))
> > + return ERR_PTR(PTR_ERR(fdir));
>
> Does this mean that to restore a subtree on a system without
> devpts-ns it won't work ? (no /dev/pts/ptmx)
Yes. I figured once we settle on devpts ns handling, we can
trivially special-case the DEVPTS_MULTIPLE_INSTANCES=n case
to use /dev/ptmx.
Since we're punting on devpts namespaces anyway I guess the
pty_open_by_master() can just open /dev/ptmx directly for
now.
Or, maybe we're better off handling the namespaces. Because
without doing that, we are hard-coding pathnames in the kernel
left and right, and that's Bad(tm).
thanks,
-serge
next prev parent reply other threads:[~2009-09-08 19:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-02 23:31 [RFC] cr: pty: don't use required_id, change ptmx_open() Serge E. Hallyn
[not found] ` <20090902233111.GA27125-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2009-09-08 18:14 ` Oren Laadan
[not found] ` <4AA69EEB.9040706-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.org>
2009-09-08 19:51 ` Serge E. Hallyn [this message]
2009-09-10 2:28 ` Serge E. Hallyn
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=20090908195131.GA23683@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=containers-qjLDD68F18O7TbgM5vRIOg@public.gmane.org \
--cc=orenl-RdfvBDnrOixBDgjK7y7TUQ@public.gmane.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 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.