mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Olaf Dietsche <olaf+list.linux-kernel@olafdietsche.de>
To: Randy Dunlap <randy.dunlap@oracle.com>
Cc: linux-kernel@vger.kernel.org, Rod Cordova <rcordova@ethernet.org>
Subject: Re: [PATCH] 2.6.38: access permission filesystem 0.25
Date: Tue, 26 Apr 2011 13:22:47 +0200	[thread overview]
Message-ID: <87oc3tnto8.fsf@rat.lan> (raw)
In-Reply-To: <4DB47564.3020202@oracle.com>

Randy Dunlap <randy.dunlap@oracle.com> writes:

> On 04/11/11 13:47, Olaf Dietsche wrote:
>
> +config ACCESSFS_USER_PORTS
> +	tristate "User permission based IP ports"
> +	depends on ACCESS_FS && INET
> +	select NET_HOOKS
> +	default n
> +	help
> +	  If you say Y here, you will be able to control access to IP ports
> +	  based on user-/groupid. For this to work, you must say Y
> +	  to CONFIG_NET_HOOKS.
>
> The last sentence of help text is unneeded and could be confusing to a user
> since the "select NET_HOOKS" is already done above.

Yes, I'll change this.

> Have you built this lately?  There have been a few vfs changes recently.
> Building on 2.6.39-rc4, I get this:
[compile errors snipped]

No, I haven't. I've built this against 2.6.38 only, as the subject says.
As soon as the need arises (and laziness allows ;-), I will look into it.

Regards, Olaf

      reply	other threads:[~2011-04-26 11:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.64.1103291321440.32194@fatboy.ethernet.org>
2011-04-10 21:50 ` [PATCH] 2.6.38: access permission filesystem 0.24 Olaf Dietsche
2011-04-11  2:03   ` Randy Dunlap
2011-04-11 20:47     ` [PATCH] 2.6.38: access permission filesystem 0.25 Olaf Dietsche
2011-04-24 19:09       ` Randy Dunlap
2011-04-26 11:22         ` Olaf Dietsche [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=87oc3tnto8.fsf@rat.lan \
    --to=olaf+list.linux-kernel@olafdietsche.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=randy.dunlap@oracle.com \
    --cc=rcordova@ethernet.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

Powered by JetHome