From: Vasiliy Kulikov <segooon@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: check capabilities in open()
Date: Sun, 25 Jul 2010 09:23:54 +0000 [thread overview]
Message-ID: <20100725092354.GA7728@albatros> (raw)
In-Reply-To: <20100725054511.GB9018@albatros>
On Sun, Jul 25, 2010 at 09:45 +0400, Vasiliy Kulikov wrote:
> Btw, the list of such drivers is much smaller, some of them just return
> -EPERM and open() fails, it is OK. I'll resend more precise list soon.
The list is tiny:
arch/x86/kernel/apm_32.c
drivers/char/agp/frontend.c
drivers/char/apm-emulation.c
Aslo comment from drivers/cahr/apm-emulation.c:
/*
* XXX - this is a tiny bit broken, when we consider BSD
* process accounting. If the device is opened by root, we
* instantly flag that we used superuser privs. Who knows,
* we might close the device immediately without doing a
* privileged operation -- cevans
*/
WARNING: multiple messages have this Message-ID (diff)
From: Vasiliy Kulikov <segooon@gmail.com>
To: Al Viro <viro@ZenIV.linux.org.uk>
Cc: kernel-janitors@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: check capabilities in open()
Date: Sun, 25 Jul 2010 13:23:54 +0400 [thread overview]
Message-ID: <20100725092354.GA7728@albatros> (raw)
In-Reply-To: <20100725054511.GB9018@albatros>
On Sun, Jul 25, 2010 at 09:45 +0400, Vasiliy Kulikov wrote:
> Btw, the list of such drivers is much smaller, some of them just return
> -EPERM and open() fails, it is OK. I'll resend more precise list soon.
The list is tiny:
arch/x86/kernel/apm_32.c
drivers/char/agp/frontend.c
drivers/char/apm-emulation.c
Aslo comment from drivers/cahr/apm-emulation.c:
/*
* XXX - this is a tiny bit broken, when we consider BSD
* process accounting. If the device is opened by root, we
* instantly flag that we used superuser privs. Who knows,
* we might close the device immediately without doing a
* privileged operation -- cevans
*/
next prev parent reply other threads:[~2010-07-25 9:23 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-24 16:07 check capabilities in open() Vasiliy Kulikov
2010-07-24 16:07 ` Vasiliy Kulikov
2010-07-24 18:23 ` Al Viro
2010-07-24 18:23 ` Al Viro
2010-07-25 5:45 ` Vasiliy Kulikov
2010-07-25 5:45 ` Vasiliy Kulikov
2010-07-25 9:23 ` Vasiliy Kulikov [this message]
2010-07-25 9:23 ` Vasiliy Kulikov
2010-07-26 11:23 ` Ted Ts'o
2010-07-26 11:23 ` Ted Ts'o
2010-07-26 16:52 ` Vasiliy Kulikov
2010-07-26 16:52 ` Vasiliy Kulikov
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=20100725092354.GA7728@albatros \
--to=segooon@gmail.com \
--cc=kernel-janitors@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@ZenIV.linux.org.uk \
/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.