All of lore.kernel.org
 help / color / mirror / Atom feed
From: Shaya Potter <spotter@cs.columbia.edu>
To: "Albert D. Cahalan" <acahalan@cs.uml.edu>
Cc: David Wagner <daw@mozart.cs.berkeley.edu>, linux-kernel@vger.kernel.org
Subject: Re: more thoughts on a new jail() system call
Date: 19 Jul 2002 17:10:15 -0400	[thread overview]
Message-ID: <1027113048.2634.62.camel@zaphod> (raw)
In-Reply-To: <200207190306.g6J366956014@saturn.cs.uml.edu>

On Thu, 2002-07-18 at 23:06, Albert D. Cahalan wrote:
> >> sys_vhangup) NOT SURE -  Should be fine, right?
> >
> > Seems ok to me.
> 
> Have fun with devpts.

can you expand on why this might be a problem, as far I can tell the
syscall is in fs/open.c

it seems very simple to me

asmlinkage long sys_vhangup(void)
{
        if (capable(CAP_SYS_TTY_CONFIG)) {
                tty_vhangup(current->tty);
                return 0;
        }
        return -EPERM;
}

basically, we call tty_vhangup on the process's tty.

if tty_vhangup was the syscall, I could see this being a problem, but as
sys_vhangup can only operate on the what the task_struct has, how is it
a problem?

thanks,

shaya potter


  parent reply	other threads:[~2002-07-19 21:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-07-18  2:26 more thoughts on a new jail() system call Shaya Potter
2002-07-18  2:30 ` Shaya Potter
2002-07-19  0:21 ` David Wagner
2002-07-19  2:08   ` Thunder from the hill
2002-07-19  4:18     ` James Antill
2002-07-19  4:55       ` Thunder from the hill
2002-07-19  7:48         ` James Antill
2002-07-19  3:06   ` Albert D. Cahalan
2002-07-19  3:23     ` David Wagner
2002-07-19 16:35     ` Shaya Potter
2002-07-19 21:10     ` Shaya Potter [this message]
2002-07-19  7:46   ` Ville Herva
2002-07-19 16:24   ` Shaya Potter
2002-07-19 16:34     ` Shaya Potter
2002-07-19 22:48   ` Shaya Potter

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=1027113048.2634.62.camel@zaphod \
    --to=spotter@cs.columbia.edu \
    --cc=acahalan@cs.uml.edu \
    --cc=daw@mozart.cs.berkeley.edu \
    --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 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.