mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nick Kurshev <nickols_k@mail.ru>
To: linux-kernel@vger.kernel.org
Subject: Re: /dev/port BUG and possible workaround
Date: Wed, 22 May 2002 13:12:10 +0400	[thread overview]
Message-ID: <20020522131210.5bae244b.nickols_k@mail.ru> (raw)
In-Reply-To: <3CEB4E43.5020203@evision-ventures.com>

[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]

Hello, Martin!

On Wed, 22 May 2002 09:52:35 +0200 you wrote:

> Uz.ytkownik Nick Kurshev napisa?:
> 
> ...
> 
> > 800=inl(CFC)
> > 2. Wrong log with using of /dev/port:
> 
> ...
> 
> > But it seems that nobody uses this device. Then what is goal
> > of implementing of this device?
> 
> Basically the goal is that contrary to some silly /proc
> stuff which is "en vouge" nowadays you have the ability to
> controll port access by using normal user permission control
> semantics of unix file access permissions, by giving /dev/port
> a proper group and so on. This is legacy crap of course, since
But this device is unworking in general. It simply unusable for
programs which require 4-byte operations with ports.
As I wrote: outl() != 4*outb() same as inl() != 4*inb()
> the above goal can be reached by using a apache-suexec alike wrapper
> as well... even with more fine grained resolution of access controll.
> 
Maybe after fixing these flaws it will be usable but not for now.


Best regards! Nick

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2002-05-22  9:11 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-22  8:41 Nick Kurshev
2002-05-22  7:52 ` Martin Dalecki
2002-05-22  9:12   ` Nick Kurshev [this message]
2002-05-22 12:09   ` Padraig Brady

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=20020522131210.5bae244b.nickols_k@mail.ru \
    --to=nickols_k@mail.ru \
    --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

all inboxes | Powered by JetHome®