All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <greg@kroah.com>
To: Christoph Hellwig <hch@infradead.org>,
	Olaf Dietsche <olaf.dietsche#list.linux-kernel@t-online.de>,
	linux-security-module@wirex.com, linux-kernel@vger.kernel.org
Subject: Re: [RFC] LSM fix for stupid "empty" functions
Date: Sun, 1 Dec 2002 10:26:44 -0800	[thread overview]
Message-ID: <20021201182644.GD8829@kroah.com> (raw)
In-Reply-To: <20021201172156.A17028@infradead.org>

On Sun, Dec 01, 2002 at 05:21:56PM +0000, Christoph Hellwig wrote:
> On Sun, Dec 01, 2002 at 10:12:27AM -0800, Greg KH wrote:
> > Does the kernel work if data structures are in ROM?  I would think that
> > lots of variables in the kernel would have this problem :)
> 
> The nommu ports support .text in rom.

But doesn't initialized variables live in .bss?  So we should be ok,
right?

thanks,

greg k-h

  reply	other threads:[~2002-12-01 17:18 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-12-01  8:30 [RFC] LSM fix for stupid "empty" functions Greg KH
2002-12-01  8:17 ` Crispin Cowan
2002-12-01 17:49   ` Greg KH
2002-12-01 16:59 ` Olaf Dietsche
2002-12-01 18:12   ` Greg KH
2002-12-01 17:21     ` Christoph Hellwig
2002-12-01 18:26       ` Greg KH [this message]
2002-12-03  2:37         ` Dragan Stancevic
2002-12-03 16:01           ` Greg KH
2002-12-03 15:14             ` Dragan Stancevic
2002-12-01 17:46     ` James Morris
2002-12-01 18:46       ` Olaf Dietsche
2002-12-01 20:05         ` Greg KH
2002-12-01 19:25       ` Greg KH
2002-12-02  2:00         ` James Morris
2002-12-02  6:57           ` Greg KH
2002-12-03  8:04             ` James Morris
2002-12-04  0:13 ` [RFC] LSM fix for stupid "empty" functions - take 2 Greg KH
2002-12-04  8:14   ` Chris Wright
2002-12-04 23:00     ` Greg KH
2002-12-04 23:44       ` Chris Wright
2002-12-05  0:09   ` James Morris
  -- strict thread matches above, loose matches on Subject: below --
2002-12-01 18:57 [RFC] LSM fix for stupid "empty" functions Adam J. Richter

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=20021201182644.GD8829@kroah.com \
    --to=greg@kroah.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-security-module@wirex.com \
    --cc=olaf.dietsche#list.linux-kernel@t-online.de \
    /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.