All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Pete Zaitcev <zaitcev@redhat.com>
Cc: Martin Schwidefsky <schwidefsky@de.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] 2.5.27: s390 fixes.
Date: Mon, 22 Jul 2002 14:24:56 -0700	[thread overview]
Message-ID: <20020722212456.GA12291@kroah.com> (raw)
In-Reply-To: <20020722171438.A11295@devserv.devel.redhat.com>

On Mon, Jul 22, 2002 at 05:14:38PM -0400, Pete Zaitcev wrote:
> > Date: Mon, 22 Jul 2002 22:04:13 +0100
> > From: Christoph Hellwig <hch@infradead.org>
> 
> > > > * add sys_security system call
> > > 
> > > I do not see the body of the call in the attached patch.
> > 
> > Does need to.  Is yet another magic dispatcher that has randomly changing
> > behaviour depending on the linux crap^H^H^H^Hsecurity module loaded.
> 
> I just realized that it comes from the LSM. Sorry.
> 
> Why does it need to be added into the architecture and
> not kept together with the patch-2.5.27-lsm1.gz or such?
> I am afraid that precludes compilation of architectures
> without LSM applied.

Because the LSM framework is now in the kernel, including sys_security.

thanks,

greg k-h

  reply	other threads:[~2002-07-22 21:23 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.1027363500.9793.linux-kernel2news@redhat.com>
2002-07-22 21:00 ` [PATCH] 2.5.27: s390 fixes Pete Zaitcev
2002-07-22 21:04   ` Christoph Hellwig
2002-07-22 21:14     ` Pete Zaitcev
2002-07-22 21:24       ` Greg KH [this message]
2002-07-22 17:50 Martin Schwidefsky
2002-07-23 17:42 ` Arnd Bergmann
2002-07-23 17:47 ` Arnd Bergmann
2002-07-23 17:48 ` Arnd Bergmann
2002-07-23 17:49 ` Arnd Bergmann
2002-07-23 17:50 ` Arnd Bergmann
2002-07-23 17:53 ` Arnd Bergmann

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=20020722212456.GA12291@kroah.com \
    --to=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwidefsky@de.ibm.com \
    --cc=zaitcev@redhat.com \
    /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.