* Re: 2.6.11-rc3-mm2
@ 2005-02-10 20:51 Jack O'Quin
2005-02-11 0:04 ` 2.6.11-rc3-mm2 Matt Mackall
0 siblings, 1 reply; 45+ messages in thread
From: Jack O'Quin @ 2005-02-10 20:51 UTC (permalink / raw)
To: Andrew Morton
Cc: Christoph Hellwig, linux-kernel, Paul Davis, Con Kolivas,
rlrevell, Chris Wright, Ingo Molnar
[direct reply bounced, resending via gmail]
Andrew Morton <akpm@osdl.org> writes:
> Christoph Hellwig <hch@infradead.org> wrote:
> >
> > On Thu, Feb 10, 2005 at 02:35:08AM -0800, Andrew Morton wrote:
> > >
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm2/
> > >
> > >
> > > - Added the mlock and !SCHED_OTHER Linux Security Module for the audio guys.
> > > It seems that nothing else is going to come along and this is completely
> > > encapsulated.
> >
> > Even if we accept a module that grants capabilities to groups this
> > isn't fine yet because it only supports two specific capabilities
> > (and even those two in different ways!) instead of adding generic
> > support to bind capabilities to groups.
>
> I'm sure that got discussed somewhere in the 1000 emails which flew past
> last time. Jack?
[adding cc: for the main discussion participants]
Most people felt that a more general capabilities module would be nice
to have. But, no one offered any code, or volunteered to work on it.
I have no objection to that approach, but am not willing or able to do
it myself. My opinion is that expanding the scope of the LSM would
significantly increase its security risk. That job needs to be done
very carefully, by someone with a deep understanding of the kernel's
internal use of capabilities.
Perhaps, Christoph's suggestion could become part of a more general
module, which might replace the RT-LSM in the 2.8 timeframe. Our LSM
is a modest solution aimed at solving the immediate needs of audio
developers and users with minimal impact on kernel security or
correctness.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-10 20:51 2.6.11-rc3-mm2 Jack O'Quin
@ 2005-02-11 0:04 ` Matt Mackall
2005-02-11 0:47 ` 2.6.11-rc3-mm2 Chris Wright
0 siblings, 1 reply; 45+ messages in thread
From: Matt Mackall @ 2005-02-11 0:04 UTC (permalink / raw)
To: Jack O'Quin
Cc: Andrew Morton, Christoph Hellwig, linux-kernel, Paul Davis,
Con Kolivas, rlrevell, Chris Wright, Ingo Molnar
On Thu, Feb 10, 2005 at 02:51:44PM -0600, Jack O'Quin wrote:
> [direct reply bounced, resending via gmail]
>
> Andrew Morton <akpm@osdl.org> writes:
>
> > Christoph Hellwig <hch@infradead.org> wrote:
> > >
> > > On Thu, Feb 10, 2005 at 02:35:08AM -0800, Andrew Morton wrote:
> > > >
> > > >
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm2/
> > > >
> > > >
> > > > - Added the mlock and !SCHED_OTHER Linux Security Module for the audio guys.
> > > > It seems that nothing else is going to come along and this is completely
> > > > encapsulated.
> > >
> > > Even if we accept a module that grants capabilities to groups this
> > > isn't fine yet because it only supports two specific capabilities
> > > (and even those two in different ways!) instead of adding generic
> > > support to bind capabilities to groups.
> >
> > I'm sure that got discussed somewhere in the 1000 emails which flew past
> > last time. Jack?
>
> [adding cc: for the main discussion participants]
>
> Most people felt that a more general capabilities module would be nice
> to have. But, no one offered any code, or volunteered to work on it.
What happened to the RT rlimit code from Chris?
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 0:04 ` 2.6.11-rc3-mm2 Matt Mackall
@ 2005-02-11 0:47 ` Chris Wright
2005-02-11 2:09 ` 2.6.11-rc3-mm2 Matt Mackall
0 siblings, 1 reply; 45+ messages in thread
From: Chris Wright @ 2005-02-11 0:47 UTC (permalink / raw)
To: Matt Mackall
Cc: Jack O'Quin, Andrew Morton, Christoph Hellwig, linux-kernel,
Paul Davis, Con Kolivas, rlrevell, Chris Wright, Ingo Molnar
* Matt Mackall (mpm@selenic.com) wrote:
> What happened to the RT rlimit code from Chris?
I still have it, but I had the impression Ingo didn't like it as a long
term solution/hack (albeit small) to the scheduler. Whereas the rt-lsm
patch is wholly self-contained.
thanks,
-chris
--
Linux Security Modules http://lsm.immunix.org http://lsm.bkbits.net
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 0:47 ` 2.6.11-rc3-mm2 Chris Wright
@ 2005-02-11 2:09 ` Matt Mackall
2005-02-11 2:22 ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11 8:14 ` 2.6.11-rc3-mm2 Ingo Molnar
0 siblings, 2 replies; 45+ messages in thread
From: Matt Mackall @ 2005-02-11 2:09 UTC (permalink / raw)
To: Chris Wright
Cc: Jack O'Quin, Andrew Morton, Christoph Hellwig, linux-kernel,
Paul Davis, Con Kolivas, rlrevell, Ingo Molnar
On Thu, Feb 10, 2005 at 04:47:27PM -0800, Chris Wright wrote:
> * Matt Mackall (mpm@selenic.com) wrote:
> > What happened to the RT rlimit code from Chris?
>
> I still have it, but I had the impression Ingo didn't like it as a long
> term solution/hack (albeit small) to the scheduler. Whereas the rt-lsm
> patch is wholly self-contained.
I think it's important to recognize that we're trying to address an
issue that has a much wider potential audience than pro audio users,
and not very far off - what is high end audio performance today will be
expected desktop performance next year.
So I think it's critical that we find solution that's appropriate for
_every single box_, because realistically vendors are going to ship
with this "wholly self-contained" feature turned on by default next
year, at which point the "containment" will be nil and whatever warts
it has will be with us forever.
The rlimit stuff is not perfect, but it's a much better fit for the
UNIX model generally, which is a fairly big win. Having it in the
system unconditionally doesn't trigger the gag reflex in quite the
same way as the LSM approach.
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 2:09 ` 2.6.11-rc3-mm2 Matt Mackall
@ 2005-02-11 2:22 ` Nick Piggin
2005-02-11 3:26 ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11 8:14 ` 2.6.11-rc3-mm2 Ingo Molnar
1 sibling, 1 reply; 45+ messages in thread
From: Nick Piggin @ 2005-02-11 2:22 UTC (permalink / raw)
To: Matt Mackall
Cc: Chris Wright, Jack O'Quin, Andrew Morton, Christoph Hellwig,
linux-kernel, Paul Davis, Con Kolivas, rlrevell, Ingo Molnar
On Thu, 2005-02-10 at 18:09 -0800, Matt Mackall wrote:
> On Thu, Feb 10, 2005 at 04:47:27PM -0800, Chris Wright wrote:
> > * Matt Mackall (mpm@selenic.com) wrote:
> > > What happened to the RT rlimit code from Chris?
> >
> > I still have it, but I had the impression Ingo didn't like it as a long
> > term solution/hack (albeit small) to the scheduler. Whereas the rt-lsm
> > patch is wholly self-contained.
>
> I think it's important to recognize that we're trying to address an
> issue that has a much wider potential audience than pro audio users,
> and not very far off - what is high end audio performance today will be
> expected desktop performance next year.
>
> So I think it's critical that we find solution that's appropriate for
> _every single box_, because realistically vendors are going to ship
> with this "wholly self-contained" feature turned on by default next
> year, at which point the "containment" will be nil and whatever warts
> it has will be with us forever.
>
> The rlimit stuff is not perfect, but it's a much better fit for the
> UNIX model generally, which is a fairly big win. Having it in the
> system unconditionally doesn't trigger the gag reflex in quite the
> same way as the LSM approach.
>
Without considering the userspace aspect, RT rlimits is the best
implementation I have seen. All others either break RT scheduling
semantics, or don't allow any way for root to maintain control of
the system after giving out RT privileges.
http://mobile.yahoo.com.au - Yahoo! Mobile
- Check & compose your email via SMS on your Telstra or Vodafone mobile.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 2:22 ` 2.6.11-rc3-mm2 Nick Piggin
@ 2005-02-11 3:26 ` Peter Williams
2005-02-11 3:41 ` 2.6.11-rc3-mm2 Paul Davis
0 siblings, 1 reply; 45+ messages in thread
From: Peter Williams @ 2005-02-11 3:26 UTC (permalink / raw)
To: Nick Piggin
Cc: Matt Mackall, Chris Wright, Jack O'Quin, Andrew Morton,
Christoph Hellwig, linux-kernel, Paul Davis, Con Kolivas,
rlrevell, Ingo Molnar
Nick Piggin wrote:
> On Thu, 2005-02-10 at 18:09 -0800, Matt Mackall wrote:
>
>>On Thu, Feb 10, 2005 at 04:47:27PM -0800, Chris Wright wrote:
>>
>>>* Matt Mackall (mpm@selenic.com) wrote:
>>>
>>>>What happened to the RT rlimit code from Chris?
>>>
>>>I still have it, but I had the impression Ingo didn't like it as a long
>>>term solution/hack (albeit small) to the scheduler. Whereas the rt-lsm
>>>patch is wholly self-contained.
>>
>>I think it's important to recognize that we're trying to address an
>>issue that has a much wider potential audience than pro audio users,
>>and not very far off - what is high end audio performance today will be
>>expected desktop performance next year.
>>
>>So I think it's critical that we find solution that's appropriate for
>>_every single box_, because realistically vendors are going to ship
>>with this "wholly self-contained" feature turned on by default next
>>year, at which point the "containment" will be nil and whatever warts
>>it has will be with us forever.
>>
>>The rlimit stuff is not perfect, but it's a much better fit for the
>>UNIX model generally, which is a fairly big win. Having it in the
>>system unconditionally doesn't trigger the gag reflex in quite the
>>same way as the LSM approach.
>>
>
>
> Without considering the userspace aspect, RT rlimits is the best
> implementation I have seen. All others either break RT scheduling
> semantics, or don't allow any way for root to maintain control of
> the system after giving out RT privileges.
Personally, I think that the best approach to solving this problem is
from the privileges aspect. The ability to grant privileges to only set
RT policy is just an example of a general need for granting limited
privileges to a program and/or a user. So a solution that involved a
mechanism for granting a specified subset of root privileges to
specified users when running specified programs would have wider
application.
My limited understanding of SELinux (which may be mistaken) is that it
provides a basic framework for this level of privilege control and
perhaps the solution lies there.
Peter
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 3:26 ` 2.6.11-rc3-mm2 Peter Williams
@ 2005-02-11 3:41 ` Paul Davis
2005-02-11 5:04 ` 2.6.11-rc3-mm2 Nick Piggin
` (2 more replies)
0 siblings, 3 replies; 45+ messages in thread
From: Paul Davis @ 2005-02-11 3:41 UTC (permalink / raw)
To: Peter Williams
Cc: Nick Piggin, Matt Mackall, Chris Wright, Jack O'Quin,
Andrew Morton, Christoph Hellwig, linux-kernel, Con Kolivas,
rlrevell, Ingo Molnar
[ the best solution is .... ]
[ my preferred solution is ... ]
[ it would be better if ... ]
[ this is a kludge and it should be done instead like ... ]
did nobody read what andrew wrote and what JOQ pointed out?
after weeks of debating this, no other conceptual solution emerged
that did not have at least as many problems as the RT LSM module, and
all other proposed solutions were also more invasive of other aspects
of kernel design and operations than RT LSM is.
--p
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 3:41 ` 2.6.11-rc3-mm2 Paul Davis
@ 2005-02-11 5:04 ` Nick Piggin
2005-02-11 6:34 ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11 5:09 ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11 6:57 ` 2.6.11-rc3-mm2 Matt Mackall
2 siblings, 1 reply; 45+ messages in thread
From: Nick Piggin @ 2005-02-11 5:04 UTC (permalink / raw)
To: Paul Davis
Cc: Peter Williams, Matt Mackall, Chris Wright, Jack O'Quin,
Andrew Morton, Christoph Hellwig, linux-kernel, Con Kolivas,
rlrevell, Ingo Molnar
On Thu, 2005-02-10 at 22:41 -0500, Paul Davis wrote:
> [ the best solution is .... ]
>
> [ my preferred solution is ... ]
>
> [ it would be better if ... ]
>
> [ this is a kludge and it should be done instead like ... ]
>
> did nobody read what andrew wrote and what JOQ pointed out?
>
> after weeks of debating this, no other conceptual solution emerged
> that did not have at least as many problems as the RT LSM module, and
> all other proposed solutions were also more invasive of other aspects
> of kernel design and operations than RT LSM is.
>
Sure, it is quick and easy. Suits some. At least I do prefer
this to altering the semantics of realtime scheduling.
I can't say much about it because I'm not putting my hand up to
do anything. Just mentioning that rlimit would be better if not
for the userspace side of the equation. I think most were already
agreed on that point anyway though.
Nick
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 3:41 ` 2.6.11-rc3-mm2 Paul Davis
2005-02-11 5:04 ` 2.6.11-rc3-mm2 Nick Piggin
@ 2005-02-11 5:09 ` Peter Williams
2005-02-11 6:57 ` 2.6.11-rc3-mm2 Matt Mackall
2 siblings, 0 replies; 45+ messages in thread
From: Peter Williams @ 2005-02-11 5:09 UTC (permalink / raw)
To: Paul Davis
Cc: Nick Piggin, Matt Mackall, Chris Wright, Jack O'Quin,
Andrew Morton, Christoph Hellwig, linux-kernel, Con Kolivas,
rlrevell, Ingo Molnar
Paul Davis wrote:
> [ the best solution is .... ]
>
> [ my preferred solution is ... ]
>
> [ it would be better if ... ]
>
> [ this is a kludge and it should be done instead like ... ]
>
> did nobody read what andrew wrote and what JOQ pointed out?
>
> after weeks of debating this, no other conceptual solution emerged
> that did not have at least as many problems as the RT LSM module, and
> all other proposed solutions were also more invasive of other aspects
> of kernel design and operations than RT LSM is.
As I see it, what I said was in support of RT LSM (or at least the
approach that RT LSM is taking) so why are you attacking me. I'm on
your side :-)
Peter
PS I'm withdrawing the "unprivileged real time" feature from the
spa_no_frills and zaphod schedulers in the PlugSched patch as a result
of the discussions on SCHED_ISO and RT rlimits because the discussion
convinced me that it's the wrong way to go.
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 5:04 ` 2.6.11-rc3-mm2 Nick Piggin
@ 2005-02-11 6:34 ` Peter Williams
2005-02-11 6:42 ` 2.6.11-rc3-mm2 Nick Piggin
0 siblings, 1 reply; 45+ messages in thread
From: Peter Williams @ 2005-02-11 6:34 UTC (permalink / raw)
To: Nick Piggin
Cc: Paul Davis, Matt Mackall, Chris Wright, Jack O'Quin,
Andrew Morton, Christoph Hellwig, linux-kernel, Con Kolivas,
rlrevell, Ingo Molnar
Nick Piggin wrote:
> On Thu, 2005-02-10 at 22:41 -0500, Paul Davis wrote:
>
>> [ the best solution is .... ]
>>
>> [ my preferred solution is ... ]
>>
>> [ it would be better if ... ]
>>
>> [ this is a kludge and it should be done instead like ... ]
>>
>>did nobody read what andrew wrote and what JOQ pointed out?
>>
>>after weeks of debating this, no other conceptual solution emerged
>>that did not have at least as many problems as the RT LSM module, and
>>all other proposed solutions were also more invasive of other aspects
>>of kernel design and operations than RT LSM is.
>>
>
>
> Sure, it is quick and easy. Suits some. At least I do prefer
> this to altering the semantics of realtime scheduling.
>
> I can't say much about it because I'm not putting my hand up to
> do anything. Just mentioning that rlimit would be better if not
> for the userspace side of the equation. I think most were already
> agreed on that point anyway though.
I think that the rlimits are a good idea in themselves but not as a
solution to this problem. I.e. having a RT CPU rate rlimit should not
be a sufficient (or necessary for that matter) condition to change
policy to SCHED_OTHER or SCHED_RR but could still be used to limit the
possibility of lock out. (But I guess even that is a violation of RT
semantics?)
Peter
PS Zaphod's per task hard/soft CPU rate caps (which are the equivalent
of an rlimit on CPU usage rate) are only enforced for SCHED_NORMAL tasks
and should not (therefore) effect RT semantics.
--
Peter Williams pwil3058@bigpond.net.au
"Learning, n. The kind of ignorance distinguishing the studious."
-- Ambrose Bierce
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 6:34 ` 2.6.11-rc3-mm2 Peter Williams
@ 2005-02-11 6:42 ` Nick Piggin
0 siblings, 0 replies; 45+ messages in thread
From: Nick Piggin @ 2005-02-11 6:42 UTC (permalink / raw)
To: Peter Williams
Cc: Paul Davis, Matt Mackall, Chris Wright, Jack O'Quin,
Andrew Morton, Christoph Hellwig, linux-kernel, Con Kolivas,
rlrevell, Ingo Molnar
On Fri, 2005-02-11 at 17:34 +1100, Peter Williams wrote:
> Nick Piggin wrote:
> > I can't say much about it because I'm not putting my hand up to
> > do anything. Just mentioning that rlimit would be better if not
> > for the userspace side of the equation. I think most were already
> > agreed on that point anyway though.
>
> I think that the rlimits are a good idea in themselves but not as a
> solution to this problem. I.e. having a RT CPU rate rlimit should not
> be a sufficient (or necessary for that matter) condition to change
> policy to SCHED_OTHER or SCHED_RR but could still be used to limit the
> possibility of lock out.
Ah well that may be a good way to do it indeed. As I said, I
don't know much about privileges etc.
But I just want to be clear that I'm not trying to stop RT-LSM
going in (if only because I don't care one way or the other
about it).
> (But I guess even that is a violation of RT
> semantics?)
>
I'd have to re-read the standard, but it may not be. For example,
a compliant system advertises the minimum and maximum priority
levels available - you may be able to adjust these based on what
the rlimit is set to. On the other hand, yes it may violate the
stanards.
Nick
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 3:41 ` 2.6.11-rc3-mm2 Paul Davis
2005-02-11 5:04 ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11 5:09 ` 2.6.11-rc3-mm2 Peter Williams
@ 2005-02-11 6:57 ` Matt Mackall
2005-02-11 7:54 ` 2.6.11-rc3-mm2 Ingo Molnar
2 siblings, 1 reply; 45+ messages in thread
From: Matt Mackall @ 2005-02-11 6:57 UTC (permalink / raw)
To: Paul Davis
Cc: Peter Williams, Nick Piggin, Chris Wright, Jack O'Quin,
Andrew Morton, Christoph Hellwig, linux-kernel, Con Kolivas,
rlrevell, Ingo Molnar
On Thu, Feb 10, 2005 at 10:41:28PM -0500, Paul Davis wrote:
> [ the best solution is .... ]
>
> [ my preferred solution is ... ]
>
> [ it would be better if ... ]
>
> [ this is a kludge and it should be done instead like ... ]
>
> did nobody read what andrew wrote and what JOQ pointed out?
>
> after weeks of debating this, no other conceptual solution emerged
> that did not have at least as many problems as the RT LSM module, and
> all other proposed solutions were also more invasive of other aspects
> of kernel design and operations than RT LSM is.
Eh? Chris Wright's original rlimits patch was very straightforward
(unlike some of the other rlimit-like patches that followed).
I haven't heard the downsides of it yet.
simple rlimits:
logical extension of standard, flexible interface
fine-grained per-process access to nice levels and priorities
managed with standard tools
fairly broad possible applications
clean enough to be added unconditionally
already doing mlock this way!
RT LSM:
new, narrow magic group interface (module parameters!)
boolean granularity of access to all RT levels and maybe mlock
potential interesting interaction with other LSMs
not orthogonal to mlock
not appropriate for every box out there
requires lsm and (sysfs or modprobe)
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 6:57 ` 2.6.11-rc3-mm2 Matt Mackall
@ 2005-02-11 7:54 ` Ingo Molnar
2005-02-11 8:25 ` 2.6.11-rc3-mm2 Matt Mackall
0 siblings, 1 reply; 45+ messages in thread
From: Ingo Molnar @ 2005-02-11 7:54 UTC (permalink / raw)
To: Matt Mackall
Cc: Paul Davis, Peter Williams, Nick Piggin, Chris Wright,
Jack O'Quin, Andrew Morton, Christoph Hellwig, linux-kernel,
Con Kolivas, rlrevell
* Matt Mackall <mpm@selenic.com> wrote:
> Eh? Chris Wright's original rlimits patch was very straightforward
> [...]
the problem is that it didnt solve the problem (unprivileged user can
lock up the system) in any way. So after it became visible that all the
existing 'dont allow users to lock up' solutions are too invasive, we
went to recommend the solution that introduces the least architectural
problems: RT-LSM.
Ingo
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 2:09 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 2:22 ` 2.6.11-rc3-mm2 Nick Piggin
@ 2005-02-11 8:14 ` Ingo Molnar
2005-02-11 8:22 ` 2.6.11-rc3-mm2 Christoph Hellwig
` (2 more replies)
1 sibling, 3 replies; 45+ messages in thread
From: Ingo Molnar @ 2005-02-11 8:14 UTC (permalink / raw)
To: Matt Mackall
Cc: Chris Wright, Jack O'Quin, Andrew Morton, Christoph Hellwig,
linux-kernel, Paul Davis, Con Kolivas, rlrevell
* Matt Mackall <mpm@selenic.com> wrote:
> > > What happened to the RT rlimit code from Chris?
> >
> > I still have it, but I had the impression Ingo didn't like it as a long
> > term solution/hack (albeit small) to the scheduler. Whereas the rt-lsm
> > patch is wholly self-contained.
>
> I think it's important to recognize that we're trying to address an
> issue that has a much wider potential audience than pro audio users,
> and not very far off - what is high end audio performance today will
> be expected desktop performance next year.
i disagree that desktop performance tomorrow will necessarily have to
utilize SCHED_FIFO. Today's desktop audio applications perform quite
good at SCHED_NORMAL priorities [with the 2.6.11 kernel that has more
interactivity/latency fixes such as PREEMPT_BKL].
I agree (and hope) that tomorrow's "stock" desktop will be based on
today's pro audio architectures, but tomorrows CPUs will be much faster
and tomorrows desktop apps dont want to spend 30%+ CPU time on creating
audio.
the pro applications will always want to have a 100% guarantee (it
really sucks to generate a nasty audio click during a live performance)
and want to utilize as much CPU time for audio as needed. They are also
clearly the most complex creators of audio so they go far above the
normal (and reasonable) CPU-use/latency expectations and tradeoffs of
the stock scheduler.
> So I think it's critical that we find solution that's appropriate for
> _every single box_, because realistically vendors are going to ship
> with this "wholly self-contained" feature turned on by default next
> year, at which point the "containment" will be nil and whatever warts
> it has will be with us forever.
an "RT priorities rlimit" is still not adequate as a desktop solution,
because it still allows the box to be locked up. Also, if it turns out
to be a mistake then it's already codified into the ABI, while RT-LSM is
much less 'persistent' and could be replaced much easier. RT-LSM is also
more flexible and more practical. (an rlimit needs changes across a
number of userspace components, delaying its adoptation.)
> The rlimit stuff is not perfect, but it's a much better fit for the
> UNIX model generally, which is a fairly big win. [...]
a 'locked up box' is as far away from the UNIX model as it gets.
perhaps, if the need arises, we can add the RT-throttling sysctl (which
still wont give RT priorities to unprivileged users and would serve as a
way to throttle privileged RT tasks), which could thus make the RT-LSM
solution pretty safe. Right now Jack has its own watchdog thread which
should solve most of the lockup situations. Lets not overdesign the
solution, especially when we dont yet know how the problem really looks
like.
or an even simpler solution for the lockup problem would be a
kernel-based RT watchdog. In fact 2.6.11-rc3-mm2 already includes such a
watchdog (written by yours truly):
http://kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm2/broken-out/detect-soft-lockups.patch
right now softlockup-detect runs at SCHED_FIFO prio 99 and only prints a
warning - but it could easily run at SCHED_FIFO prio 1 [to detect
lockups generated by all RT tasks] and it could actively try to renice
(or kill) tasks that run for too long. So very likely there will be an
easy upstream mechanism for any problem that could arise out of RT-LSM.
Ingo
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 8:14 ` 2.6.11-rc3-mm2 Ingo Molnar
@ 2005-02-11 8:22 ` Christoph Hellwig
2005-02-11 8:41 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-14 5:21 ` 2.6.11-rc3-mm2 Werner Almesberger
2 siblings, 0 replies; 45+ messages in thread
From: Christoph Hellwig @ 2005-02-11 8:22 UTC (permalink / raw)
To: Ingo Molnar
Cc: Matt Mackall, Chris Wright, Jack O'Quin, Andrew Morton,
Christoph Hellwig, linux-kernel, Paul Davis, Con Kolivas,
rlrevell
On Fri, Feb 11, 2005 at 09:14:22AM +0100, Ingo Molnar wrote:
> an "RT priorities rlimit" is still not adequate as a desktop solution,
> because it still allows the box to be locked up. Also, if it turns out
> to be a mistake then it's already codified into the ABI, while RT-LSM is
> much less 'persistent' and could be replaced much easier. RT-LSM is also
> more flexible and more practical. (an rlimit needs changes across a
> number of userspace components, delaying its adoptation.)
Putting it into the tree means a gurantee we'll keep it going. It'd
probably much better if Jack just keepts it separatly. Especially as
his lack of even making it generic shows that he's unwilling to invest
work into it that doesn't benfit him personally.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 7:54 ` 2.6.11-rc3-mm2 Ingo Molnar
@ 2005-02-11 8:25 ` Matt Mackall
2005-02-11 8:48 ` 2.6.11-rc3-mm2 Ingo Molnar
` (2 more replies)
0 siblings, 3 replies; 45+ messages in thread
From: Matt Mackall @ 2005-02-11 8:25 UTC (permalink / raw)
To: Ingo Molnar
Cc: Paul Davis, Peter Williams, Nick Piggin, Chris Wright,
Jack O'Quin, Andrew Morton, Christoph Hellwig, linux-kernel,
Con Kolivas, rlrevell
On Fri, Feb 11, 2005 at 08:54:17AM +0100, Ingo Molnar wrote:
>
> * Matt Mackall <mpm@selenic.com> wrote:
>
> > Eh? Chris Wright's original rlimits patch was very straightforward
> > [...]
>
> the problem is that it didnt solve the problem (unprivileged user can
> lock up the system) in any way.
There are two separate but related problems:
a) need a way to give non-root access to SCHED_FIFO without other
privileges
b) would like a way to have RT-like capabilities without risk of DoS
The original rlimits patch solves (a), which is the pressing concern.
The existence of a satisfactory solution to related problem (b) has
yet to be demonstrated. And even if a solution for (b) is found that
is satisfactory for, say, high end audio users, it may not necessarily
be sufficient for everyone who might have wanted SCHED_FIFO for
non-root processes. So we still need a solution for (a).
> So after it became visible that all the
> existing 'dont allow users to lock up' solutions are too invasive, we
> went to recommend the solution that introduces the least architectural
> problems: RT-LSM.
RT-LSM introduces architectural problems in the form of bogus API. And
I claim that if RT-LSM becomes part of the mainline kernel, it -will-
become a default feature on the desktop in short order. The fact that
it's implemented as an LSM is meaningless if Redhat and SuSE ship it
on by default.
So the comparison boils down to putting a magic gid in a sysfs
file/module parameter or setting an rlimit with standard tools (PAM,
etc). I'm really boggled that anyone could prefer the former,
especially since we had almost this exact debate over what became the
mlock rlimit!
Here's Chris' patch for reference:
http://groups-beta.google.com/group/linux.kernel/msg/6408569e13ed6e80
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 8:14 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 8:22 ` 2.6.11-rc3-mm2 Christoph Hellwig
@ 2005-02-11 8:41 ` Matt Mackall
2005-02-11 8:59 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 17:45 ` 2.6.11-rc3-mm2 Paul Davis
2005-02-14 5:21 ` 2.6.11-rc3-mm2 Werner Almesberger
2 siblings, 2 replies; 45+ messages in thread
From: Matt Mackall @ 2005-02-11 8:41 UTC (permalink / raw)
To: Ingo Molnar
Cc: Chris Wright, Jack O'Quin, Andrew Morton, Christoph Hellwig,
linux-kernel, Paul Davis, Con Kolivas, rlrevell
On Fri, Feb 11, 2005 at 09:14:22AM +0100, Ingo Molnar wrote:
>
> > I think it's important to recognize that we're trying to address an
> > issue that has a much wider potential audience than pro audio users,
> > and not very far off - what is high end audio performance today will
> > be expected desktop performance next year.
>
> i disagree that desktop performance tomorrow will necessarily have to
> utilize SCHED_FIFO. Today's desktop audio applications perform quite
> good at SCHED_NORMAL priorities [with the 2.6.11 kernel that has more
> interactivity/latency fixes such as PREEMPT_BKL].
Desktop performance tomorrow will want realtime audio AND video.
Think simultaneous record and playback of multiple high-definition
video streams. There's a demand for this; my company already sells it.
> the pro applications will always want to have a 100% guarantee (it
> really sucks to generate a nasty audio click during a live performance)
> and want to utilize as much CPU time for audio as needed. They are also
> clearly the most complex creators of audio so they go far above the
> normal (and reasonable) CPU-use/latency expectations and tradeoffs of
> the stock scheduler.
The pro will want to do his work on a stock desktop system. More
importantly, the hobbyist will want to do exactly what the pro is
doing on the same system.
> > So I think it's critical that we find solution that's appropriate for
> > _every single box_, because realistically vendors are going to ship
> > with this "wholly self-contained" feature turned on by default next
> > year, at which point the "containment" will be nil and whatever warts
> > it has will be with us forever.
>
> an "RT priorities rlimit" is still not adequate as a desktop solution,
> because it still allows the box to be locked up. Also, if it turns out
> to be a mistake then it's already codified into the ABI, while RT-LSM is
> much less 'persistent' and could be replaced much easier. RT-LSM is also
> more flexible and more practical. (an rlimit needs changes across a
> number of userspace components, delaying its adoptation.)
I'm very suspicious about being able to rip out RT-LSM once it's
introduced. See devfs. And I think the adoption barrier thing is a red
herring as well: the current users are by and large compiling their
own RT-tuned kernels.
> > The rlimit stuff is not perfect, but it's a much better fit for the
> > UNIX model generally, which is a fairly big win. [...]
>
> a 'locked up box' is as far away from the UNIX model as it gets.
Rlimits are already the favored tool for dealing with the classic UNIX DoS:
the fork bomb. Turn off process limits, tada, locked up box.
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 8:25 ` 2.6.11-rc3-mm2 Matt Mackall
@ 2005-02-11 8:48 ` Ingo Molnar
2005-02-11 8:58 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 9:04 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 17:49 ` 2.6.11-rc3-mm2 Paul Davis
2 siblings, 1 reply; 45+ messages in thread
From: Ingo Molnar @ 2005-02-11 8:48 UTC (permalink / raw)
To: Matt Mackall
Cc: Paul Davis, Peter Williams, Nick Piggin, Chris Wright,
Jack O'Quin, Andrew Morton, Christoph Hellwig, linux-kernel,
Con Kolivas, rlrevell
* Matt Mackall <mpm@selenic.com> wrote:
> Here's Chris' patch for reference:
>
> http://groups-beta.google.com/group/linux.kernel/msg/6408569e13ed6e80
how does this patch solve the separation of 'negative nice values' and
'RT priority rlimits'? In one piece of code it handles the rlimit value
as a 0-39 nice value, in another place it handles it as a limit for a
1-100 RT priority range. The two ranges overlap and have nothing to do
with each other. [*]
anyway, as long as it doesnt touch the scheduler runtime code (and it
doesnt), both types of solutions are fine to me - it's basically the
security-subsystem people's call.
if the patch solves the negative-nice-value and the RT-priority issues
at once, then it indeed looks more flexible (and more generic) than the
LSM solution. [**]
Ingo
[*] one acceptable way to 'merge' the two priority ranges would be to
introduce a unified priority range of 0-139: 0-39 would be for nice
values while 40-139 would be for RT priorities 1-99. NOTE: due to
rlimit semantics (users can always lower them without any security
checks), value 39 _must_ denote nice -20 and value 0 must denote
nice +19. I.e. it must strictly in increasing priority order.
[**] in fact, the 'Gnome problem' wrt. suid/gid binaries would be solved
via the rlimit too.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 8:48 ` 2.6.11-rc3-mm2 Ingo Molnar
@ 2005-02-11 8:58 ` Matt Mackall
2005-02-11 9:01 ` 2.6.11-rc3-mm2 Ingo Molnar
0 siblings, 1 reply; 45+ messages in thread
From: Matt Mackall @ 2005-02-11 8:58 UTC (permalink / raw)
To: Ingo Molnar
Cc: Paul Davis, Peter Williams, Nick Piggin, Chris Wright,
Jack O'Quin, Andrew Morton, Christoph Hellwig, linux-kernel,
Con Kolivas, rlrevell
On Fri, Feb 11, 2005 at 09:48:43AM +0100, Ingo Molnar wrote:
>
> * Matt Mackall <mpm@selenic.com> wrote:
>
> > Here's Chris' patch for reference:
> >
> > http://groups-beta.google.com/group/linux.kernel/msg/6408569e13ed6e80
>
> how does this patch solve the separation of 'negative nice values' and
> 'RT priority rlimits'? In one piece of code it handles the rlimit value
> as a 0-39 nice value, in another place it handles it as a limit for a
> 1-100 RT priority range. The two ranges overlap and have nothing to do
> with each other. [*]
Read more closely: there are two independent limits in the patch,
RLIMIT_NICE and RLIMIT_RTPRIO. This lets us grant elevated nice
without SCHED_FIFO.
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 8:41 ` 2.6.11-rc3-mm2 Matt Mackall
@ 2005-02-11 8:59 ` Ingo Molnar
2005-02-11 9:40 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:45 ` 2.6.11-rc3-mm2 Paul Davis
1 sibling, 1 reply; 45+ messages in thread
From: Ingo Molnar @ 2005-02-11 8:59 UTC (permalink / raw)
To: Matt Mackall
Cc: Chris Wright, Jack O'Quin, Andrew Morton, Christoph Hellwig,
linux-kernel, Paul Davis, Con Kolivas, rlrevell
* Matt Mackall <mpm@selenic.com> wrote:
> > i disagree that desktop performance tomorrow will necessarily have to
> > utilize SCHED_FIFO. Today's desktop audio applications perform quite
> > good at SCHED_NORMAL priorities [with the 2.6.11 kernel that has more
> > interactivity/latency fixes such as PREEMPT_BKL].
>
> Desktop performance tomorrow will want realtime audio AND video.
> Think simultaneous record and playback of multiple high-definition
> video streams. There's a demand for this; my company already sells it.
Tomorrow's hardware will have enough buffering as today's hardware has
for simpler tasks. Repeat after me: it likely _wont_ _need_ SCHED_FIFO.
Running tomorrow's hardware on today's boxes indeed pushes the system to
its limits, but torrows hardware will be well-balanced just as much as
today's is - if nothing else then due to kernel drivers providing a
buffering guarantee.
think of SCHED_FIFO on the desktop as an ugly wart, a hammer, that
destroys the careful balance of priorities of SCHED_OTHER tasks. Yes, it
can be useful if you _need_ a scheduling guarantee due to physical
constraints, and it can be useful if the hardware (or the kernel) cannot
buffer enough, but otherwise, it only causes problems.
> I'm very suspicious about being able to rip out RT-LSM once it's
> introduced. [...]
yeah, i somewhat share that view. (despite all the promises from the
audio folks - if they are just half as agressive resisting removal as
they were pushing integration then it will never be removed ;-)
but i'm not sure how rlimits will contain the whole problem - can
rlimits be restricted to a single app (jackd)? The most canonical use of
rlimits is per-user (per-group), so the rlimit could end up _widening_
the effects of the hack ...
> > > The rlimit stuff is not perfect, but it's a much better fit for the
> > > UNIX model generally, which is a fairly big win. [...]
> >
> > a 'locked up box' is as far away from the UNIX model as it gets.
>
> Rlimits are already the favored tool for dealing with the classic UNIX
> DoS: the fork bomb. Turn off process limits, tada, locked up box.
the big difference is that process limits are finegrained and it has a
single value (unlimited) that allows the DoS - while the RT-rlimits have
_one_ value that is safe, all the other values are unsafe!
Ingo
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 8:58 ` 2.6.11-rc3-mm2 Matt Mackall
@ 2005-02-11 9:01 ` Ingo Molnar
0 siblings, 0 replies; 45+ messages in thread
From: Ingo Molnar @ 2005-02-11 9:01 UTC (permalink / raw)
To: Matt Mackall
Cc: Paul Davis, Peter Williams, Nick Piggin, Chris Wright,
Jack O'Quin, Andrew Morton, Christoph Hellwig, linux-kernel,
Con Kolivas, rlrevell
* Matt Mackall <mpm@selenic.com> wrote:
> Read more closely: there are two independent limits in the patch,
> RLIMIT_NICE and RLIMIT_RTPRIO. This lets us grant elevated nice
> without SCHED_FIFO.
ok, indeed.
Ingo
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 8:25 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 8:48 ` 2.6.11-rc3-mm2 Ingo Molnar
@ 2005-02-11 9:04 ` Ingo Molnar
2005-02-11 9:27 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:49 ` 2.6.11-rc3-mm2 Paul Davis
2 siblings, 1 reply; 45+ messages in thread
From: Ingo Molnar @ 2005-02-11 9:04 UTC (permalink / raw)
To: Matt Mackall
Cc: Paul Davis, Peter Williams, Nick Piggin, Chris Wright,
Jack O'Quin, Andrew Morton, Christoph Hellwig, linux-kernel,
Con Kolivas, rlrevell
* Matt Mackall <mpm@selenic.com> wrote:
> So the comparison boils down to putting a magic gid in a sysfs
> file/module parameter or setting an rlimit with standard tools (PAM,
> etc). I'm really boggled that anyone could prefer the former,
> especially since we had almost this exact debate over what became the
> mlock rlimit!
the big difference to mlock is that for mlock there _is_ a _limit_. For
RT scheduling the priority is _NOT_ a _limit_. Okay? So you give the
false pretense of this being some kind of resource 'limit', while in
fact allowing SCHED_FIFO prio 1 alone enables unprivileged users to lock
up the system.
so i could agree with RLIMIT_NICE (which _is_ a limit), but
RLIMIT_RTPRIO sends the wrong message. The proper rlimit would be
RLIMIT_RT_CPU (the patch i did).
Ingo
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 9:04 ` 2.6.11-rc3-mm2 Ingo Molnar
@ 2005-02-11 9:27 ` Matt Mackall
0 siblings, 0 replies; 45+ messages in thread
From: Matt Mackall @ 2005-02-11 9:27 UTC (permalink / raw)
To: Ingo Molnar
Cc: Paul Davis, Peter Williams, Nick Piggin, Chris Wright,
Jack O'Quin, Andrew Morton, Christoph Hellwig, linux-kernel,
Con Kolivas, rlrevell
On Fri, Feb 11, 2005 at 10:04:19AM +0100, Ingo Molnar wrote:
>
> * Matt Mackall <mpm@selenic.com> wrote:
>
> > So the comparison boils down to putting a magic gid in a sysfs
> > file/module parameter or setting an rlimit with standard tools (PAM,
> > etc). I'm really boggled that anyone could prefer the former,
> > especially since we had almost this exact debate over what became the
> > mlock rlimit!
>
> the big difference to mlock is that for mlock there _is_ a _limit_. For
> RT scheduling the priority is _NOT_ a _limit_. Okay? So you give the
> false pretense of this being some kind of resource 'limit', while in
> fact allowing SCHED_FIFO prio 1 alone enables unprivileged users to lock
> up the system.
>
> so i could agree with RLIMIT_NICE (which _is_ a limit), but
> RLIMIT_RTPRIO sends the wrong message. The proper rlimit would be
> RLIMIT_RT_CPU (the patch i did).
It's not a perfect fit, I'll readily agree.
But consider this: with RLIMIT_RTPRIO, I can restrict a user to the
lowest N RT priorities. Then at N+1, I have an RT watchdog taking care
of runaways, tickled by a SCHED_NORMAL task. So it can still be looked
at as a meaningful limit, just a bit different from the others.
The RT LSM gives full CAP_SYS_NICE out, so there's no way to guarantee
that the watchdog has higher priority.
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 8:59 ` 2.6.11-rc3-mm2 Ingo Molnar
@ 2005-02-11 9:40 ` Matt Mackall
2005-02-11 9:53 ` 2.6.11-rc3-mm2 Ingo Molnar
0 siblings, 1 reply; 45+ messages in thread
From: Matt Mackall @ 2005-02-11 9:40 UTC (permalink / raw)
To: Ingo Molnar
Cc: Chris Wright, Jack O'Quin, Andrew Morton, Christoph Hellwig,
linux-kernel, Paul Davis, Con Kolivas, rlrevell
On Fri, Feb 11, 2005 at 09:59:42AM +0100, Ingo Molnar wrote:
>
> think of SCHED_FIFO on the desktop as an ugly wart, a hammer, that
> destroys the careful balance of priorities of SCHED_OTHER tasks. Yes, it
> can be useful if you _need_ a scheduling guarantee due to physical
> constraints, and it can be useful if the hardware (or the kernel) cannot
> buffer enough, but otherwise, it only causes problems.
Agreed. I think something short of full SCHED_FIFO will make most
desktop folks happy. But a) we still have to figure out exactly how to
do that and b) we still have to make everyone else happy. The embedded
folks (me included) would prefer to not run our realtime bits as root
too..
> but i'm not sure how rlimits will contain the whole problem - can
> rlimits be restricted to a single app (jackd)?
Yes. There's also the whole soft limit thing.
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 9:40 ` 2.6.11-rc3-mm2 Matt Mackall
@ 2005-02-11 9:53 ` Ingo Molnar
2005-02-11 17:37 ` 2.6.11-rc3-mm2 Matt Mackall
0 siblings, 1 reply; 45+ messages in thread
From: Ingo Molnar @ 2005-02-11 9:53 UTC (permalink / raw)
To: Matt Mackall
Cc: Chris Wright, Jack O'Quin, Andrew Morton, Christoph Hellwig,
linux-kernel, Paul Davis, Con Kolivas, rlrevell
* Matt Mackall <mpm@selenic.com> wrote:
> On Fri, Feb 11, 2005 at 09:59:42AM +0100, Ingo Molnar wrote:
> >
> > think of SCHED_FIFO on the desktop as an ugly wart, a hammer, that
> > destroys the careful balance of priorities of SCHED_OTHER tasks. Yes, it
> > can be useful if you _need_ a scheduling guarantee due to physical
> > constraints, and it can be useful if the hardware (or the kernel) cannot
> > buffer enough, but otherwise, it only causes problems.
>
> Agreed. I think something short of full SCHED_FIFO will make most
> desktop folks happy. [...]
ah, but it's not the desktop folks who have to be happy but users :-)
Really, if you ask any app designer then obviously 'the more CPU time we
get for sure, the better our app behaves'. So in that sense SCHED_OTHER
is a fair playground: if you behave nicely you'll have higher priority
and shorter latencies.
(there are things like SCHED_ISO but how good of a solution they are is
not yet clear.)
> [...] But a) we still have to figure out exactly how to do that and b)
> we still have to make everyone else happy. The embedded folks (me
> included) would prefer to not run our realtime bits as root too..
you dont have to - you can drop root after startup.
> > but i'm not sure how rlimits will contain the whole problem - can
> > rlimits be restricted to a single app (jackd)?
>
> Yes. There's also the whole soft limit thing.
i'm curious, how does this 'per-app' rlimit thing work? If a user has
jackd installed and runs it from X unprivileged, how does it get the
elevated rlimit? (while the rest of his desktop still runs with a safe
rlimit.) SELinux/RT-LSM could do this, but i'm not sure about how
rlimits give this to you.
Ingo
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 9:53 ` 2.6.11-rc3-mm2 Ingo Molnar
@ 2005-02-11 17:37 ` Matt Mackall
2005-02-11 17:49 ` 2.6.11-rc3-mm2 Ingo Molnar
0 siblings, 1 reply; 45+ messages in thread
From: Matt Mackall @ 2005-02-11 17:37 UTC (permalink / raw)
To: Ingo Molnar
Cc: Chris Wright, Jack O'Quin, Andrew Morton, Christoph Hellwig,
linux-kernel, Paul Davis, Con Kolivas, rlrevell
On Fri, Feb 11, 2005 at 10:53:27AM +0100, Ingo Molnar wrote:
>
> * Matt Mackall <mpm@selenic.com> wrote:
>
> > On Fri, Feb 11, 2005 at 09:59:42AM +0100, Ingo Molnar wrote:
> > >
> > > think of SCHED_FIFO on the desktop as an ugly wart, a hammer, that
> > > destroys the careful balance of priorities of SCHED_OTHER tasks. Yes, it
> > > can be useful if you _need_ a scheduling guarantee due to physical
> > > constraints, and it can be useful if the hardware (or the kernel) cannot
> > > buffer enough, but otherwise, it only causes problems.
> >
> > Agreed. I think something short of full SCHED_FIFO will make most
> > desktop folks happy. [...]
>
> ah, but it's not the desktop folks who have to be happy but users :-)
> Really, if you ask any app designer then obviously 'the more CPU time we
> get for sure, the better our app behaves'. So in that sense SCHED_OTHER
> is a fair playground: if you behave nicely you'll have higher priority
> and shorter latencies.
>
> (there are things like SCHED_ISO but how good of a solution they are is
> not yet clear.)
>
> > [...] But a) we still have to figure out exactly how to do that and b)
> > we still have to make everyone else happy. The embedded folks (me
> > included) would prefer to not run our realtime bits as root too..
>
> you dont have to - you can drop root after startup.
>
> > > but i'm not sure how rlimits will contain the whole problem - can
> > > rlimits be restricted to a single app (jackd)?
> >
> > Yes. There's also the whole soft limit thing.
>
> i'm curious, how does this 'per-app' rlimit thing work? If a user has
> jackd installed and runs it from X unprivileged, how does it get the
> elevated rlimit?
It needs a setuid launcher. It would be nice to be able to elevate the
rlimits of running processes but the API doesn't exist yet.
>From the POV of accidental elevation to RT, soft limits are
sufficient. But we can't stop a user from exploiting an app they own
with RT privileges from elevating other apps via ptrace+exec or
whatever. Nor with RT-LSM.
> (while the rest of his desktop still runs with a safe
> rlimit.) SELinux/RT-LSM could do this, but i'm not sure about how
> rlimits give this to you.
How does it get done with RT-LSM? Setgid binaries? It only
discriminates on a group granularity. Or are you saying "and SELinux"
rather than "or SELinux"?
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 8:41 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 8:59 ` 2.6.11-rc3-mm2 Ingo Molnar
@ 2005-02-11 17:45 ` Paul Davis
1 sibling, 0 replies; 45+ messages in thread
From: Paul Davis @ 2005-02-11 17:45 UTC (permalink / raw)
To: Matt Mackall
Cc: Ingo Molnar, Chris Wright, Jack O'Quin, Andrew Morton,
Christoph Hellwig, linux-kernel, Con Kolivas, rlrevell
>introduced. See devfs. And I think the adoption barrier thing is a red
>herring as well: the current users are by and large compiling their
>own RT-tuned kernels.
not true. most people are using kernels built for specialized distros
or addons, such as CCRMA, Demudi, Ubuntu, or dyne:bolic.
--p
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 8:25 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 8:48 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 9:04 ` 2.6.11-rc3-mm2 Ingo Molnar
@ 2005-02-11 17:49 ` Paul Davis
2005-02-11 19:42 ` 2.6.11-rc3-mm2 Matt Mackall
2 siblings, 1 reply; 45+ messages in thread
From: Paul Davis @ 2005-02-11 17:49 UTC (permalink / raw)
To: Matt Mackall
Cc: Ingo Molnar, Peter Williams, Nick Piggin, Chris Wright,
Jack O'Quin, Andrew Morton, Christoph Hellwig, linux-kernel,
Con Kolivas, rlrevell
>RT-LSM introduces architectural problems in the form of bogus API. And
that may be true of LSM, but not RT-LSM in particular. RT-LSM doesn't
introduce *any* API whatsoever - it simply allows software to call
various existing APIs (mostly from POSIX) and have them not fail as
result of not being root and/or not running on a capabilities-enabled
kernel without the required caps.
No audio apps "use" RT-LSM in any way - it just lets them do things
they otherwise could not do. And all the alternatives to RT-LSM have
this feature as well - controlling rlimits won't be done by the audio
apps, but by some part of the security infrastructure.
>it's implemented as an LSM is meaningless if Redhat and SuSE ship it
>on by default.
We haven't encouraged anyone to ship anything with it on by default:
the idea is for the module to be present and usable, not turned on.
--p
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 17:37 ` 2.6.11-rc3-mm2 Matt Mackall
@ 2005-02-11 17:49 ` Ingo Molnar
2005-02-11 20:10 ` 2.6.11-rc3-mm2 Matt Mackall
0 siblings, 1 reply; 45+ messages in thread
From: Ingo Molnar @ 2005-02-11 17:49 UTC (permalink / raw)
To: Matt Mackall
Cc: Chris Wright, Jack O'Quin, Andrew Morton, Christoph Hellwig,
linux-kernel, Paul Davis, Con Kolivas, rlrevell
* Matt Mackall <mpm@selenic.com> wrote:
> > > Yes. There's also the whole soft limit thing.
> >
> > i'm curious, how does this 'per-app' rlimit thing work? If a user has
> > jackd installed and runs it from X unprivileged, how does it get the
> > elevated rlimit?
>
> It needs a setuid launcher. It would be nice to be able to elevate the
> rlimits of running processes but the API doesn't exist yet.
With a setuid launcher you need _zero_ kernel help to get SCHED_FIFO: if
you have a launcher then already today it can just give SCHED_FIFO to
jackd and be done with it!
Ingo
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 17:49 ` 2.6.11-rc3-mm2 Paul Davis
@ 2005-02-11 19:42 ` Matt Mackall
2005-02-11 19:57 ` 2.6.11-rc3-mm2 Lee Revell
0 siblings, 1 reply; 45+ messages in thread
From: Matt Mackall @ 2005-02-11 19:42 UTC (permalink / raw)
To: Paul Davis
Cc: Ingo Molnar, Peter Williams, Nick Piggin, Chris Wright,
Jack O'Quin, Andrew Morton, Christoph Hellwig, linux-kernel,
Con Kolivas, rlrevell
On Fri, Feb 11, 2005 at 12:49:04PM -0500, Paul Davis wrote:
> >RT-LSM introduces architectural problems in the form of bogus API. And
>
> that may be true of LSM, but not RT-LSM in particular. RT-LSM doesn't
> introduce *any* API whatsoever - it simply allows software to call
> various existing APIs (mostly from POSIX) and have them not fail as
> result of not being root and/or not running on a capabilities-enabled
> kernel without the required caps.
The API is the parameters to modprobe or sysfs.
> >it's implemented as an LSM is meaningless if Redhat and SuSE ship it
> >on by default.
>
> We haven't encouraged anyone to ship anything with it on by default:
> the idea is for the module to be present and usable, not turned on.
On as in turned on for build in the kernel config and shipped. But I
expect people will eventually actually ship it _on_ with a group
called 'rt' and possibly even put the primary user in there on install
unless you start slapping some big fat warnings on it. (I just noticed
the new Debian installer is putting the primary user in audio, cdrom,
video, etc.)
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 19:42 ` 2.6.11-rc3-mm2 Matt Mackall
@ 2005-02-11 19:57 ` Lee Revell
0 siblings, 0 replies; 45+ messages in thread
From: Lee Revell @ 2005-02-11 19:57 UTC (permalink / raw)
To: Matt Mackall
Cc: Paul Davis, Ingo Molnar, Peter Williams, Nick Piggin,
Chris Wright, Jack O'Quin, Andrew Morton, Christoph Hellwig,
linux-kernel, Con Kolivas
On Fri, 2005-02-11 at 11:42 -0800, Matt Mackall wrote:
> On Fri, Feb 11, 2005 at 12:49:04PM -0500, Paul Davis wrote:
> > >RT-LSM introduces architectural problems in the form of bogus API. And
> >
> > that may be true of LSM, but not RT-LSM in particular. RT-LSM doesn't
> > introduce *any* API whatsoever - it simply allows software to call
> > various existing APIs (mostly from POSIX) and have them not fail as
> > result of not being root and/or not running on a capabilities-enabled
> > kernel without the required caps.
>
> The API is the parameters to modprobe or sysfs.
>
I think you are talking about the API for root to administer it vs. the
(lack of) API for apps to use the RT capabilities. I think Paul's point
is that we can transparently replace it with something better (IMO the
RT rlimit is better) in the future, and the apps don't have to know
about it at all. Comparing it to devfs/udev is bogus because those are
way, way more complicated.
> > >it's implemented as an LSM is meaningless if Redhat and SuSE ship it
> > >on by default.
> >
> > We haven't encouraged anyone to ship anything with it on by default:
> > the idea is for the module to be present and usable, not turned on.
>
> On as in turned on for build in the kernel config and shipped. But I
> expect people will eventually actually ship it _on_ with a group
> called 'rt' and possibly even put the primary user in there on install
> unless you start slapping some big fat warnings on it. (I just noticed
> the new Debian installer is putting the primary user in audio, cdrom,
> video, etc.)
>
Sorry, if the distros are so dumb they need a big fat warning to know
that this is not a safe thing to enable by default, at least on anything
you would ever consider a multiuser system, then they get what they
deserve. If they have half a brain they will use the setgid approach
that Ingo suggested, and only enable this for apps like JACK and
cdrecord that have been farily well audited and can be trusted to use
this feature (for example JACK has the internal watchdog to keep a bad
client from locking the system). Really it only makes sense for a
distro to enable this if the user selects the "low latency desktop" or
"multimedia desktop" or whatever install option and makes clear that
this profile is NOT suitable for a multiuser system.
Lee
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 17:49 ` 2.6.11-rc3-mm2 Ingo Molnar
@ 2005-02-11 20:10 ` Matt Mackall
0 siblings, 0 replies; 45+ messages in thread
From: Matt Mackall @ 2005-02-11 20:10 UTC (permalink / raw)
To: Ingo Molnar
Cc: Chris Wright, Jack O'Quin, Andrew Morton, Christoph Hellwig,
linux-kernel, Paul Davis, Con Kolivas, rlrevell
On Fri, Feb 11, 2005 at 06:49:05PM +0100, Ingo Molnar wrote:
>
> * Matt Mackall <mpm@selenic.com> wrote:
>
> > > > Yes. There's also the whole soft limit thing.
> > >
> > > i'm curious, how does this 'per-app' rlimit thing work? If a user has
> > > jackd installed and runs it from X unprivileged, how does it get the
> > > elevated rlimit?
> >
> > It needs a setuid launcher. It would be nice to be able to elevate the
> > rlimits of running processes but the API doesn't exist yet.
>
> With a setuid launcher you need _zero_ kernel help to get SCHED_FIFO: if
> you have a launcher then already today it can just give SCHED_FIFO to
> jackd and be done with it!
I'm sure you know all this already but I'll spell it out so we're all
clear:
a) rlimits are tracked per-process so they're fundamentally
per-process
b) there are hard and soft limits, with soft always <= hard
c) only root can raise hard rlimits, but normal users can lower them
d) if a user owns a process, he can gain the privileges of that process
by various means, so in the strict sense per-process privileges are
meaningless - all privileges are per-uid
e) so we either need to segregate all privileged processes into
separate uid domains
f) or we're assuming non-malicious users and soft limits are
sufficient.
Now I suspect we don't want to insist people do (e) (though I'd
certainly encourage them to try).
Don't forget that the rlimits approach allows us to reserve the
highest priorities for root. I'm pretty sure an effective watchdog
policy can thus be implemented in userspace, which RT-LSM can't really
offer.
--
Mathematics is the supreme nostalgia of our time.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 8:14 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 8:22 ` 2.6.11-rc3-mm2 Christoph Hellwig
2005-02-11 8:41 ` 2.6.11-rc3-mm2 Matt Mackall
@ 2005-02-14 5:21 ` Werner Almesberger
2 siblings, 0 replies; 45+ messages in thread
From: Werner Almesberger @ 2005-02-14 5:21 UTC (permalink / raw)
To: Ingo Molnar
Cc: Matt Mackall, Chris Wright, Jack O'Quin, Andrew Morton,
Christoph Hellwig, linux-kernel, Paul Davis, Con Kolivas,
rlrevell
Ingo Molnar wrote:
> the pro applications will always want to have a 100% guarantee (it
> really sucks to generate a nasty audio click during a live performance)
... and the "generic kernels" distributions use will follow just
as swiftly, as soon as the feature appears stable enough. It even
makes sense: no need to switch kernels if "pro audio" applications
(or whatever else may end up wanting this) are added to the mix,
and fewer configurations to test.
You can run, but you cannot hide :-)
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-10 10:35 2.6.11-rc3-mm2 Andrew Morton
` (4 preceding siblings ...)
2005-02-11 16:29 ` 2.6.11-rc3-mm2 Yuval Tanny
@ 2005-02-14 13:22 ` Stefano Rivoir
5 siblings, 0 replies; 45+ messages in thread
From: Stefano Rivoir @ 2005-02-14 13:22 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
Alle 11:35, giovedì 10 febbraio 2005, Andrew Morton ha scritto:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.
>6.11-rc3-mm2/
I was trying to use the skge module for my Intel 3c940 card, in place of the
(working) sk98lin.
It gives the following:
Feb 14 14:16:35 nbsteu kernel: kobject_register failed for skge (-17)
Feb 14 14:16:35 nbsteu kernel: [kobject_register+81/96]
kobject_register+0x51/0x60
Feb 14 14:16:35 nbsteu kernel: [bus_add_driver+82/192]
bus_add_driver+0x52/0xc0
Feb 14 14:16:35 nbsteu kernel: [driver_register+40/48]
driver_register+0x28/0x30
Feb 14 14:16:35 nbsteu kernel: [pci_register_driver+94/128]
pci_register_driver+0x5e/0x80
Feb 14 14:16:35 nbsteu kernel: [sys_init_module+313/480]
sys_init_module+0x139/0x1e0
Feb 14 14:16:35 nbsteu kernel: [sysenter_past_esp+82/117]
sysenter_past_esp+0x52/0x75
Attached, .config and lspci -v
--
Stefano Rivoir
[-- Attachment #2: lspci-v --]
[-- Type: text/plain, Size: 5605 bytes --]
0000:00:00.0 Host bridge: Silicon Integrated Systems [SiS] SiS 645xx (rev 03)
Subsystem: Asustek Computer, Inc.: Unknown device 1738
Flags: bus master, medium devsel, latency 32
Memory at e8000000 (32-bit, non-prefetchable) [size=64M]
Capabilities: [c0] AGP version 2.0
0000:00:01.0 PCI bridge: Silicon Integrated Systems [SiS] Virtual PCI-to-PCI bridge (AGP) (prog-if 00 [Normal decode])
Flags: bus master, fast devsel, latency 0
Bus: primary=00, secondary=01, subordinate=01, sec-latency=0
I/O behind bridge: 0000d000-0000dfff
Memory behind bridge: e7800000-e7ffffff
Prefetchable memory behind bridge: eff00000-febfffff
0000:00:02.0 ISA bridge: Silicon Integrated Systems [SiS] SiS963 [MuTIOL Media IO] (rev 14)
Flags: bus master, medium devsel, latency 0
0000:00:02.1 SMBus: Silicon Integrated Systems [SiS]: Unknown device 0016
Flags: medium devsel
I/O ports at e800 [size=32]
0000:00:02.3 FireWire (IEEE 1394): Silicon Integrated Systems [SiS] FireWire Controller (prog-if 10 [OHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 1737
Flags: bus master, medium devsel, latency 32, IRQ 11
Memory at e7000000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [64] Power Management version 2
0000:00:02.5 IDE interface: Silicon Integrated Systems [SiS] 5513 [IDE] (prog-if 80 [Master])
Subsystem: Asustek Computer, Inc.: Unknown device 1738
Flags: bus master, medium devsel, latency 32
I/O ports at b800 [size=16]
Capabilities: [58] Power Management version 2
0000:00:02.6 Modem: Silicon Integrated Systems [SiS] AC'97 Modem Controller (rev a0) (prog-if 00 [Generic])
Subsystem: Asustek Computer, Inc.: Unknown device 1736
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at b400 [size=256]
I/O ports at b000 [size=128]
Capabilities: [48] Power Management version 2
0000:00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS] Sound Controller (rev a0)
Subsystem: Asustek Computer, Inc.: Unknown device 1733
Flags: bus master, medium devsel, latency 32, IRQ 11
I/O ports at a800 [size=256]
I/O ports at a400 [size=128]
Capabilities: [48] Power Management version 2
0000:00:03.0 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 1739
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at e6800000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2
0000:00:03.1 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 1739
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at e6000000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2
0000:00:03.2 USB Controller: Silicon Integrated Systems [SiS] USB 1.0 Controller (rev 0f) (prog-if 10 [OHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 1739
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at e5800000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [dc] Power Management version 2
0000:00:03.3 USB Controller: Silicon Integrated Systems [SiS] USB 2.0 Controller (prog-if 20 [EHCI])
Subsystem: Asustek Computer, Inc.: Unknown device 173a
Flags: bus master, medium devsel, latency 32, IRQ 5
Memory at e5000000 (32-bit, non-prefetchable) [size=4K]
Capabilities: [50] Power Management version 2
0000:00:0a.0 CardBus bridge: ENE Technology Inc CB720 Cardbus Controller (rev 01)
Subsystem: Asustek Computer, Inc.: Unknown device 1734
Flags: bus master, medium devsel, latency 168, IRQ 11
Memory at 20000000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=02, subordinate=05, sec-latency=176
Memory window 0: 20400000-207ff000 (prefetchable)
Memory window 1: 20800000-20bff000
I/O window 0: 00004000-000040ff
I/O window 1: 00004400-000044ff
16-bit legacy interface ports at 0001
0000:00:0a.1 CardBus bridge: ENE Technology Inc CB720 Cardbus Controller (rev 01)
Subsystem: Asustek Computer, Inc.: Unknown device 1734
Flags: bus master, medium devsel, latency 168, IRQ 11
Memory at 20001000 (32-bit, non-prefetchable) [size=4K]
Bus: primary=00, secondary=06, subordinate=09, sec-latency=176
Memory window 0: 20c00000-20fff000 (prefetchable)
Memory window 1: 21000000-213ff000
I/O window 0: 00004800-000048ff
I/O window 1: 00004c00-00004cff
16-bit legacy interface ports at 0001
0000:00:0a.2 FLASH memory: ENE Technology Inc CB710 Memory Card Reader Controller
Subsystem: Asustek Computer, Inc.: Unknown device 173b
Flags: medium devsel, IRQ 11
I/O ports at 9800 [size=128]
Capabilities: [a0] Power Management version 2
0000:00:0d.0 Ethernet controller: 3Com Corporation 3c940 10/100/1000Base-T [Marvell] (rev 12)
Subsystem: Asustek Computer, Inc.: Unknown device 173c
Flags: bus master, 66MHz, medium devsel, latency 32, IRQ 11
Memory at e4000000 (32-bit, non-prefetchable) [size=16K]
I/O ports at 9400 [size=256]
Capabilities: [48] Power Management version 2
Capabilities: [50] Vital Product Data
0000:01:00.0 VGA compatible controller: ATI Technologies Inc Radeon R250 Lf [Radeon Mobility 9000 M9] (rev 01) (prog-if 00 [VGA])
Subsystem: Asustek Computer, Inc.: Unknown device 1732
Flags: bus master, stepping, 66MHz, medium devsel, latency 64, IRQ 11
Memory at f0000000 (32-bit, prefetchable) [size=128M]
I/O ports at d800 [size=256]
Memory at e7800000 (32-bit, non-prefetchable) [size=64K]
Expansion ROM at effe0000 [disabled] [size=128K]
Capabilities: [58] AGP version 2.0
Capabilities: [50] Power Management version 2
[-- Attachment #3: .config --]
[-- Type: text/plain, Size: 29610 bytes --]
#
# Automatically generated make config: don't edit
# Linux kernel version: 2.6.11-rc3-mm2
# Fri Feb 11 08:56:56 2005
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
# CONFIG_CLEAN_COMPILE is not set
CONFIG_BROKEN=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCK_KERNEL=y
#
# General setup
#
CONFIG_LOCALVERSION=""
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_POSIX_MQUEUE=y
CONFIG_BSD_PROCESS_ACCT=y
# CONFIG_BSD_PROCESS_ACCT_V3 is not set
CONFIG_SYSCTL=y
# CONFIG_AUDIT is not set
CONFIG_HOTPLUG=y
CONFIG_KOBJECT_UEVENT=y
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
# CONFIG_KALLSYMS_ALL is not set
# CONFIG_KALLSYMS_EXTRA_PASS is not set
CONFIG_BASE_FULL=y
CONFIG_BASE_SMALL=0
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_SHMEM=y
CONFIG_CC_ALIGN_FUNCTIONS=0
CONFIG_CC_ALIGN_LABELS=0
CONFIG_CC_ALIGN_LOOPS=0
CONFIG_CC_ALIGN_JUMPS=0
# CONFIG_TINY_SHMEM is not set
#
# Loadable module support
#
CONFIG_MODULES=y
CONFIG_MODULE_UNLOAD=y
# CONFIG_MODULE_FORCE_UNLOAD is not set
CONFIG_OBSOLETE_MODPARM=y
# CONFIG_MODVERSIONS is not set
# CONFIG_MODULE_SRCVERSION_ALL is not set
CONFIG_KMOD=y
#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
# CONFIG_MPENTIUMIII is not set
# CONFIG_MPENTIUMM is not set
CONFIG_MPENTIUM4=y
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MEFFICEON is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=7
CONFIG_RWSEM_XCHGADD_ALGORITHM=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_WP_WORKS_OK=y
CONFIG_X86_INVLPG=y
CONFIG_X86_BSWAP=y
CONFIG_X86_POPAD_OK=y
CONFIG_X86_GOOD_APIC=y
CONFIG_X86_INTEL_USERCOPY=y
CONFIG_X86_USE_PPRO_CHECKSUM=y
# CONFIG_HPET_TIMER is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
CONFIG_PREEMPT_BKL=y
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
# CONFIG_X86_MCE_NONFATAL is not set
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
#
# Firmware Drivers
#
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
# CONFIG_EFI is not set
CONFIG_HAVE_DEC_LOCK=y
CONFIG_REGPARM=y
#
# Performance-monitoring counters support
#
# CONFIG_PERFCTR is not set
CONFIG_PHYSICAL_START=0x100000
# CONFIG_KEXEC is not set
#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set
#
# ACPI (Advanced Configuration and Power Interface) Support
#
CONFIG_ACPI=y
CONFIG_ACPI_BOOT=y
CONFIG_ACPI_INTERPRETER=y
CONFIG_ACPI_AC=m
CONFIG_ACPI_BATTERY=m
CONFIG_ACPI_BUTTON=m
CONFIG_ACPI_VIDEO=m
CONFIG_ACPI_FAN=m
CONFIG_ACPI_PROCESSOR=m
CONFIG_ACPI_THERMAL=m
CONFIG_ACPI_ASUS=m
# CONFIG_ACPI_IBM is not set
# CONFIG_ACPI_TOSHIBA is not set
# CONFIG_ACPI_CUSTOM_DSDT is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
CONFIG_ACPI_EC=y
CONFIG_ACPI_POWER=y
CONFIG_ACPI_PCI=y
CONFIG_ACPI_SYSTEM=y
# CONFIG_X86_PM_TIMER is not set
CONFIG_ACPI_CONTAINER=m
#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set
#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
# CONFIG_PCIEPORTBUS is not set
# CONFIG_PCI_LEGACY_PROC is not set
CONFIG_PCI_NAMES=y
# CONFIG_ISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
#
# PCCARD (PCMCIA/CardBus) support
#
CONFIG_PCCARD=m
# CONFIG_PCMCIA_DEBUG is not set
CONFIG_PCMCIA=m
CONFIG_CARDBUS=y
#
# PC-card bridges
#
CONFIG_YENTA=m
# CONFIG_PD6729 is not set
# CONFIG_I82092 is not set
# CONFIG_TCIC is not set
CONFIG_PCCARD_NONSTATIC=m
#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set
#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_AOUT=m
CONFIG_BINFMT_MISC=m
#
# Device Drivers
#
#
# Generic Driver Options
#
# CONFIG_STANDALONE is not set
# CONFIG_PREVENT_FIRMWARE_BUILD is not set
# CONFIG_FW_LOADER is not set
# CONFIG_DEBUG_DRIVER is not set
#
# Connector - unified userspace <-> kernelspace linker
#
# CONFIG_CONNECTOR is not set
#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set
#
# Parallel port support
#
CONFIG_PARPORT=m
# CONFIG_PARPORT_PC is not set
# CONFIG_PARPORT_GSC is not set
# CONFIG_PARPORT_1284 is not set
#
# Plug and Play support
#
CONFIG_PNP=y
# CONFIG_PNP_DEBUG is not set
#
# Protocols
#
CONFIG_PNPACPI=y
#
# Block devices
#
CONFIG_BLK_DEV_FD=m
# CONFIG_PARIDE is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
# CONFIG_BLK_DEV_COW_COMMON is not set
CONFIG_BLK_DEV_LOOP=m
# CONFIG_BLK_DEV_CRYPTOLOOP is not set
CONFIG_BLK_DEV_NBD=m
# CONFIG_BLK_DEV_SX8 is not set
# CONFIG_BLK_DEV_UB is not set
# CONFIG_BLK_DEV_RAM is not set
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_INITRAMFS_SOURCE=""
# CONFIG_LBD is not set
CONFIG_CDROM_PKTCDVD=y
CONFIG_CDROM_PKTCDVD_BUFFERS=8
# CONFIG_CDROM_PKTCDVD_WCACHE is not set
#
# IO Schedulers
#
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_ATA_OVER_ETH is not set
#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_IDE_SATA is not set
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_BLK_DEV_IDECS is not set
CONFIG_BLK_DEV_IDECD=m
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_BLK_DEV_IDESCSI is not set
# CONFIG_IDE_TASK_IOCTL is not set
#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPNP=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
# CONFIG_BLK_DEV_RZ1000 is not set
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_ATIIXP is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
# CONFIG_BLK_DEV_PIIX is not set
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
CONFIG_BLK_DEV_SIS5513=y
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_ARM is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_BLK_DEV_HD is not set
#
# SCSI device support
#
CONFIG_SCSI=m
CONFIG_SCSI_PROC_FS=y
#
# SCSI support type (disk, tape, CD-ROM)
#
CONFIG_BLK_DEV_SD=m
# CONFIG_CHR_DEV_ST is not set
# CONFIG_CHR_DEV_OSST is not set
# CONFIG_BLK_DEV_SR is not set
CONFIG_CHR_DEV_SG=m
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
#
CONFIG_SCSI_MULTI_LUN=y
# CONFIG_SCSI_CONSTANTS is not set
# CONFIG_SCSI_LOGGING is not set
#
# SCSI Transport Attributes
#
# CONFIG_SCSI_SPI_ATTRS is not set
# CONFIG_SCSI_FC_ATTRS is not set
# CONFIG_SCSI_ISCSI_ATTRS is not set
#
# SCSI low-level drivers
#
# CONFIG_BLK_DEV_3W_XXXX_RAID is not set
# CONFIG_SCSI_3W_9XXX is not set
# CONFIG_SCSI_ARCMSR is not set
# CONFIG_SCSI_ACARD is not set
# CONFIG_SCSI_AACRAID is not set
# CONFIG_SCSI_AIC7XXX is not set
# CONFIG_SCSI_AIC7XXX_OLD is not set
# CONFIG_SCSI_AIC79XX is not set
# CONFIG_SCSI_DPT_I2O is not set
# CONFIG_SCSI_ADVANSYS is not set
# CONFIG_MEGARAID_NEWGEN is not set
# CONFIG_MEGARAID_LEGACY is not set
# CONFIG_SCSI_SATA is not set
# CONFIG_SCSI_BUSLOGIC is not set
# CONFIG_SCSI_CPQFCTS is not set
# CONFIG_SCSI_DMX3191D is not set
# CONFIG_SCSI_EATA is not set
# CONFIG_SCSI_EATA_PIO is not set
# CONFIG_SCSI_FUTURE_DOMAIN is not set
# CONFIG_SCSI_GDTH is not set
# CONFIG_SCSI_IPS is not set
# CONFIG_SCSI_INITIO is not set
# CONFIG_SCSI_INIA100 is not set
# CONFIG_SCSI_PPA is not set
# CONFIG_SCSI_IMM is not set
# CONFIG_SCSI_SYM53C8XX_2 is not set
# CONFIG_SCSI_IPR is not set
# CONFIG_SCSI_PCI2000 is not set
# CONFIG_SCSI_PCI2220I is not set
# CONFIG_SCSI_QLOGIC_ISP is not set
# CONFIG_SCSI_QLOGIC_FC is not set
# CONFIG_SCSI_QLOGIC_1280 is not set
CONFIG_SCSI_QLA2XXX=m
# CONFIG_SCSI_QLA21XX is not set
# CONFIG_SCSI_QLA22XX is not set
# CONFIG_SCSI_QLA2300 is not set
# CONFIG_SCSI_QLA2322 is not set
# CONFIG_SCSI_QLA6312 is not set
# CONFIG_SCSI_DC395x is not set
# CONFIG_SCSI_DC390T is not set
# CONFIG_SCSI_NSP32 is not set
# CONFIG_SCSI_DEBUG is not set
#
# PCMCIA SCSI adapter support
#
# CONFIG_PCMCIA_AHA152X is not set
# CONFIG_PCMCIA_FDOMAIN is not set
# CONFIG_PCMCIA_NINJA_SCSI is not set
# CONFIG_PCMCIA_QLOGIC is not set
# CONFIG_PCMCIA_SYM53C500 is not set
#
# Multi-device support (RAID and LVM)
#
# CONFIG_MD is not set
#
# Fusion MPT device support
#
# CONFIG_FUSION is not set
#
# IEEE 1394 (FireWire) support
#
CONFIG_IEEE1394=m
#
# Subsystem Options
#
# CONFIG_IEEE1394_VERBOSEDEBUG is not set
# CONFIG_IEEE1394_OUI_DB is not set
# CONFIG_IEEE1394_EXTRA_CONFIG_ROMS is not set
#
# Device Drivers
#
#
# Texas Instruments PCILynx requires I2C
#
CONFIG_IEEE1394_OHCI1394=m
#
# Protocol Drivers
#
# CONFIG_IEEE1394_VIDEO1394 is not set
CONFIG_IEEE1394_SBP2=m
# CONFIG_IEEE1394_SBP2_PHYS_DMA is not set
# CONFIG_IEEE1394_ETH1394 is not set
# CONFIG_IEEE1394_DV1394 is not set
# CONFIG_IEEE1394_RAWIO is not set
# CONFIG_IEEE1394_CMP is not set
#
# I2O device support
#
# CONFIG_I2O is not set
#
# Networking support
#
CONFIG_NET=y
#
# Networking options
#
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
# CONFIG_NET_KEY is not set
CONFIG_INET=y
# CONFIG_IP_MULTICAST is not set
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_ARPD is not set
CONFIG_SYN_COOKIES=y
# CONFIG_INET_AH is not set
# CONFIG_INET_ESP is not set
# CONFIG_INET_IPCOMP is not set
# CONFIG_INET_TUNNEL is not set
# CONFIG_IP_TCPDIAG is not set
# CONFIG_IP_TCPDIAG_IPV6 is not set
#
# IP: Virtual Server Configuration
#
# CONFIG_IP_VS is not set
# CONFIG_IPV6 is not set
CONFIG_NETFILTER=y
# CONFIG_NETFILTER_DEBUG is not set
#
# IP: Netfilter Configuration
#
CONFIG_IP_NF_CONNTRACK=m
# CONFIG_IP_NF_CT_ACCT is not set
# CONFIG_IP_NF_CONNTRACK_MARK is not set
# CONFIG_IP_NF_CT_PROTO_SCTP is not set
CONFIG_IP_NF_FTP=m
CONFIG_IP_NF_IRC=m
# CONFIG_IP_NF_TFTP is not set
# CONFIG_IP_NF_AMANDA is not set
# CONFIG_IP_NF_QUEUE is not set
CONFIG_IP_NF_IPTABLES=m
CONFIG_IP_NF_MATCH_LIMIT=m
# CONFIG_IP_NF_MATCH_IPRANGE is not set
CONFIG_IP_NF_MATCH_MAC=m
# CONFIG_IP_NF_MATCH_PKTTYPE is not set
CONFIG_IP_NF_MATCH_MARK=m
CONFIG_IP_NF_MATCH_MULTIPORT=m
# CONFIG_IP_NF_MATCH_TOS is not set
# CONFIG_IP_NF_MATCH_RECENT is not set
# CONFIG_IP_NF_MATCH_ECN is not set
# CONFIG_IP_NF_MATCH_DSCP is not set
# CONFIG_IP_NF_MATCH_AH_ESP is not set
# CONFIG_IP_NF_MATCH_LENGTH is not set
# CONFIG_IP_NF_MATCH_TTL is not set
# CONFIG_IP_NF_MATCH_TCPMSS is not set
# CONFIG_IP_NF_MATCH_HELPER is not set
CONFIG_IP_NF_MATCH_STATE=m
# CONFIG_IP_NF_MATCH_CONNTRACK is not set
# CONFIG_IP_NF_MATCH_OWNER is not set
# CONFIG_IP_NF_MATCH_ADDRTYPE is not set
# CONFIG_IP_NF_MATCH_REALM is not set
# CONFIG_IP_NF_MATCH_SCTP is not set
# CONFIG_IP_NF_MATCH_COMMENT is not set
# CONFIG_IP_NF_MATCH_HASHLIMIT is not set
CONFIG_IP_NF_FILTER=m
CONFIG_IP_NF_TARGET_REJECT=m
CONFIG_IP_NF_TARGET_LOG=m
# CONFIG_IP_NF_TARGET_ULOG is not set
# CONFIG_IP_NF_TARGET_TCPMSS is not set
CONFIG_IP_NF_NAT=m
CONFIG_IP_NF_NAT_NEEDED=y
CONFIG_IP_NF_TARGET_MASQUERADE=m
CONFIG_IP_NF_TARGET_REDIRECT=m
# CONFIG_IP_NF_TARGET_NETMAP is not set
# CONFIG_IP_NF_TARGET_SAME is not set
# CONFIG_IP_NF_NAT_SNMP_BASIC is not set
CONFIG_IP_NF_NAT_IRC=m
CONFIG_IP_NF_NAT_FTP=m
CONFIG_IP_NF_MANGLE=m
CONFIG_IP_NF_TARGET_TOS=m
# CONFIG_IP_NF_TARGET_ECN is not set
# CONFIG_IP_NF_TARGET_DSCP is not set
# CONFIG_IP_NF_TARGET_MARK is not set
# CONFIG_IP_NF_TARGET_CLASSIFY is not set
# CONFIG_IP_NF_RAW is not set
# CONFIG_IP_NF_ARPTABLES is not set
#
# SCTP Configuration (EXPERIMENTAL)
#
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_BRIDGE is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_DECNET is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set
# CONFIG_NET_CLS_ROUTE is not set
#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
# CONFIG_KGDBOE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
# CONFIG_NET_POLL_CONTROLLER is not set
# CONFIG_HAMRADIO is not set
# CONFIG_IRDA is not set
# CONFIG_BT is not set
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set
# CONFIG_NET_SB1000 is not set
#
# ARCnet devices
#
# CONFIG_ARCNET is not set
#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
CONFIG_MII=m
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
# CONFIG_NET_VENDOR_3COM is not set
#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_HP100 is not set
CONFIG_NET_PCI=y
# CONFIG_PCNET32 is not set
# CONFIG_AMD8111_ETH is not set
# CONFIG_ADAPTEC_STARFIRE is not set
# CONFIG_B44 is not set
# CONFIG_FORCEDETH is not set
# CONFIG_DGRS is not set
CONFIG_EEPRO100=m
# CONFIG_E100 is not set
# CONFIG_FEALNX is not set
# CONFIG_NATSEMI is not set
CONFIG_NE2K_PCI=m
CONFIG_8139CP=m
CONFIG_8139TOO=m
# CONFIG_8139TOO_PIO is not set
# CONFIG_8139TOO_TUNE_TWISTER is not set
# CONFIG_8139TOO_8129 is not set
# CONFIG_8139_OLD_RX_RESET is not set
# CONFIG_SIS900 is not set
# CONFIG_EPIC100 is not set
# CONFIG_SUNDANCE is not set
# CONFIG_TLAN is not set
# CONFIG_VIA_RHINE is not set
#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
CONFIG_SKGE=m
CONFIG_SK98LIN=m
# CONFIG_VIA_VELOCITY is not set
# CONFIG_TIGON3 is not set
#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_S2IO is not set
#
# Token Ring devices
#
# CONFIG_TR is not set
#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set
#
# PCMCIA network device support
#
# CONFIG_NET_PCMCIA is not set
#
# Wan interfaces
#
# CONFIG_WAN is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PLIP is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set
# CONFIG_NET_FC is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set
#
# ISDN subsystem
#
# CONFIG_ISDN is not set
#
# Telephony Support
#
# CONFIG_PHONE is not set
#
# Input device support
#
CONFIG_INPUT=y
#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_JOYDEV=y
# CONFIG_INPUT_TSDEV is not set
CONFIG_INPUT_EVDEV=m
# CONFIG_INPUT_EVBUG is not set
#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_LKKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_VSXXXAA is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
# CONFIG_INPUT_UINPUT is not set
#
# Hardware I/O ports
#
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PARKBD is not set
# CONFIG_SERIO_PCIPS2 is not set
CONFIG_SERIO_LIBPS2=y
# CONFIG_SERIO_RAW is not set
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set
#
# Serial drivers
#
CONFIG_SERIAL_8250=m
# CONFIG_SERIAL_8250_CS is not set
# CONFIG_SERIAL_8250_ACPI is not set
CONFIG_SERIAL_8250_NR_UARTS=4
# CONFIG_SERIAL_8250_EXTENDED is not set
#
# Non-8250 serial port support
#
CONFIG_SERIAL_CORE=m
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
CONFIG_PRINTER=m
# CONFIG_LP_CONSOLE is not set
# CONFIG_PPDEV is not set
# CONFIG_TIPAR is not set
#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set
#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
CONFIG_HW_RANDOM=m
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set
#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=m
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
# CONFIG_AGP_INTEL is not set
# CONFIG_AGP_NVIDIA is not set
CONFIG_AGP_SIS=m
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
# CONFIG_AGP_EFFICEON is not set
CONFIG_DRM=m
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
CONFIG_DRM_RADEON=m
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_DRM_VIA is not set
#
# PCMCIA character devices
#
# CONFIG_SYNCLINK_CS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HPET is not set
# CONFIG_HANGCHECK_TIMER is not set
#
# I2C support
#
# CONFIG_I2C is not set
#
# Dallas's 1-wire bus
#
# CONFIG_W1 is not set
#
# SuperIO subsystem support
#
#
# Misc devices
#
# CONFIG_IBM_ASM is not set
#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set
#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set
#
# Graphics support
#
CONFIG_FB=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
# CONFIG_FB_CIRRUS is not set
# CONFIG_FB_PM2 is not set
# CONFIG_FB_CYBER2000 is not set
# CONFIG_FB_ASILIANT is not set
# CONFIG_FB_IMSTT is not set
# CONFIG_FB_VGA16 is not set
# CONFIG_FB_VESA is not set
CONFIG_VIDEO_SELECT=y
# CONFIG_FB_HGA is not set
# CONFIG_FB_RIVA is not set
# CONFIG_FB_I810 is not set
# CONFIG_FB_INTEL is not set
# CONFIG_FB_MATROX is not set
# CONFIG_FB_RADEON_OLD is not set
CONFIG_FB_RADEON=y
# CONFIG_FB_RADEON_I2C is not set
# CONFIG_FB_RADEON_DEBUG is not set
# CONFIG_FB_ATY128 is not set
# CONFIG_FB_ATY is not set
# CONFIG_FB_SAVAGE is not set
# CONFIG_FB_SIS is not set
# CONFIG_FB_NEOMAGIC is not set
# CONFIG_FB_KYRO is not set
# CONFIG_FB_3DFX is not set
# CONFIG_FB_VOODOO1 is not set
# CONFIG_FB_TRIDENT is not set
# CONFIG_FB_PM3 is not set
# CONFIG_FB_VIRTUAL is not set
#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_FRAMEBUFFER_CONSOLE=y
CONFIG_FONTS=y
# CONFIG_FONT_8x8 is not set
CONFIG_FONT_8x16=y
CONFIG_FONT_6x11=y
CONFIG_FONT_PEARL_8x8=y
CONFIG_FONT_ACORN_8x8=y
CONFIG_FONT_MINI_4x6=y
CONFIG_FONT_SUN8x16=y
CONFIG_FONT_SUN12x22=y
#
# Logo configuration
#
# CONFIG_LOGO is not set
# CONFIG_BACKLIGHT_LCD_SUPPORT is not set
#
# Sound
#
CONFIG_SOUND=m
#
# Advanced Linux Sound Architecture
#
CONFIG_SND=m
CONFIG_SND_TIMER=m
CONFIG_SND_PCM=m
CONFIG_SND_RAWMIDI=m
CONFIG_SND_SEQUENCER=m
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=m
CONFIG_SND_PCM_OSS=m
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set
#
# Generic devices
#
CONFIG_SND_MPU401_UART=m
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
CONFIG_SND_SERIAL_U16550=m
CONFIG_SND_MPU401=m
#
# PCI devices
#
CONFIG_SND_AC97_CODEC=m
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_ATIIXP is not set
# CONFIG_SND_ATIIXP_MODEM is not set
# CONFIG_SND_AU8810 is not set
# CONFIG_SND_AU8820 is not set
# CONFIG_SND_AU8830 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_EMU10K1X is not set
# CONFIG_SND_CA0106 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_MIXART is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=m
CONFIG_SND_INTEL8X0M=m
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VIA82XX_MODEM is not set
# CONFIG_SND_VX222 is not set
# CONFIG_SND_HDA_INTEL is not set
#
# USB devices
#
# CONFIG_SND_USB_AUDIO is not set
# CONFIG_SND_USB_USX2Y is not set
#
# PCMCIA devices
#
#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set
#
# USB support
#
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_USB=y
# CONFIG_USB_DEBUG is not set
#
# Miscellaneous USB options
#
CONFIG_USB_DEVICEFS=y
# CONFIG_USB_BANDWIDTH is not set
# CONFIG_USB_DYNAMIC_MINORS is not set
# CONFIG_USB_OTG is not set
#
# USB Host Controller Drivers
#
CONFIG_USB_EHCI_HCD=m
# CONFIG_USB_EHCI_SPLIT_ISO is not set
CONFIG_USB_EHCI_ROOT_HUB_TT=y
CONFIG_USB_OHCI_HCD=m
# CONFIG_USB_OHCI_BIG_ENDIAN is not set
CONFIG_USB_OHCI_LITTLE_ENDIAN=y
# CONFIG_USB_UHCI_HCD is not set
# CONFIG_USB_SL811_HCD is not set
#
# USB Device Class drivers
#
# CONFIG_USB_AUDIO is not set
# CONFIG_USB_BLUETOOTH_TTY is not set
# CONFIG_USB_MIDI is not set
# CONFIG_USB_ACM is not set
CONFIG_USB_PRINTER=m
#
# NOTE: USB_STORAGE enables SCSI, and 'SCSI disk support' may also be needed; see USB_STORAGE Help for more information
#
CONFIG_USB_STORAGE=m
# CONFIG_USB_STORAGE_DEBUG is not set
# CONFIG_USB_STORAGE_RW_DETECT is not set
# CONFIG_USB_STORAGE_DATAFAB is not set
# CONFIG_USB_STORAGE_FREECOM is not set
# CONFIG_USB_STORAGE_ISD200 is not set
# CONFIG_USB_STORAGE_DPCM is not set
CONFIG_USB_STORAGE_USBAT=y
# CONFIG_USB_STORAGE_SDDR09 is not set
# CONFIG_USB_STORAGE_SDDR55 is not set
# CONFIG_USB_STORAGE_JUMPSHOT is not set
#
# USB Input Devices
#
CONFIG_USB_HID=m
CONFIG_USB_HIDINPUT=y
# CONFIG_HID_FF is not set
CONFIG_USB_HIDDEV=y
#
# USB HID Boot Protocol drivers
#
# CONFIG_USB_KBD is not set
# CONFIG_USB_MOUSE is not set
# CONFIG_USB_AIPTEK is not set
# CONFIG_USB_WACOM is not set
# CONFIG_USB_KBTAB is not set
# CONFIG_USB_POWERMATE is not set
# CONFIG_USB_MTOUCH is not set
# CONFIG_USB_EGALAX is not set
# CONFIG_USB_XPAD is not set
# CONFIG_USB_ATI_REMOTE is not set
#
# USB Imaging devices
#
# CONFIG_USB_MDC800 is not set
# CONFIG_USB_MICROTEK is not set
# CONFIG_USB_HPUSBSCSI is not set
#
# USB Multimedia devices
#
# CONFIG_USB_DABUSB is not set
#
# Video4Linux support is needed for USB Multimedia device support
#
#
# USB Network Adapters
#
# CONFIG_USB_CATC is not set
# CONFIG_USB_KAWETH is not set
# CONFIG_USB_PEGASUS is not set
# CONFIG_USB_RTL8150 is not set
# CONFIG_USB_USBNET is not set
# CONFIG_USB_MON is not set
#
# USB port drivers
#
# CONFIG_USB_USS720 is not set
#
# USB Serial Converter support
#
# CONFIG_USB_SERIAL is not set
#
# USB Miscellaneous drivers
#
# CONFIG_USB_EMI62 is not set
# CONFIG_USB_EMI26 is not set
# CONFIG_USB_AUERSWALD is not set
# CONFIG_USB_RIO500 is not set
# CONFIG_USB_LEGOTOWER is not set
# CONFIG_USB_LCD is not set
# CONFIG_USB_LED is not set
# CONFIG_USB_CYTHERM is not set
# CONFIG_USB_PHIDGETKIT is not set
# CONFIG_USB_PHIDGETSERVO is not set
# CONFIG_USB_IDMOUSE is not set
# CONFIG_USB_SISUSBVGA is not set
# CONFIG_USB_TEST is not set
#
# USB ATM/DSL drivers
#
#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set
#
# MMC/SD Card support
#
# CONFIG_MMC is not set
#
# InfiniBand support
#
# CONFIG_INFINIBAND is not set
#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISER4_FS is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_FS_POSIX_ACL is not set
#
# XFS support
#
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
CONFIG_DNOTIFY=y
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set
#
# Caches
#
# CONFIG_FSCACHE is not set
# CONFIG_FUSE_FS is not set
#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=m
CONFIG_JOLIET=y
CONFIG_ZISOFS=y
CONFIG_ZISOFS_FS=m
CONFIG_UDF_FS=m
CONFIG_UDF_NLS=y
#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=m
CONFIG_MSDOS_FS=m
CONFIG_VFAT_FS=m
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=m
# CONFIG_NTFS_DEBUG is not set
CONFIG_NTFS_RW=y
#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
# CONFIG_TMPFS is not set
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y
#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_HFSPLUS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set
#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set
#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y
#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=m
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
# CONFIG_NLS_ASCII is not set
CONFIG_NLS_ISO8859_1=m
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
CONFIG_NLS_ISO8859_15=m
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set
#
# Profiling support
#
# CONFIG_PROFILING is not set
#
# Kernel hacking
#
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_LOG_BUF_SHIFT=15
CONFIG_DETECT_SOFTLOCKUP=y
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
# CONFIG_DEBUG_PREEMPT is not set
# CONFIG_DEBUG_SPINLOCK is not set
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_DEBUG_KOBJECT is not set
CONFIG_DEBUG_BUGVERBOSE=y
# CONFIG_DEBUG_INFO is not set
# CONFIG_PAGE_OWNER is not set
# CONFIG_DEBUG_FS is not set
# CONFIG_FRAME_POINTER is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_STACKOVERFLOW is not set
# CONFIG_KPROBES is not set
# CONFIG_DEBUG_STACK_USAGE is not set
# CONFIG_DEBUG_PAGEALLOC is not set
# CONFIG_4KSTACKS is not set
# CONFIG_KGDB is not set
#
# Security options
#
# CONFIG_KEYS is not set
# CONFIG_SECURITY is not set
#
# Cryptographic options
#
# CONFIG_CRYPTO is not set
#
# Hardware crypto devices
#
#
# Library routines
#
# CONFIG_CRC_CCITT is not set
CONFIG_CRC32=y
# CONFIG_LIBCRC32C is not set
CONFIG_ZLIB_INFLATE=m
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-10 13:35 ` 2.6.11-rc3-mm2 Christoph Hellwig
2005-02-10 20:01 ` 2.6.11-rc3-mm2 Andrew Morton
@ 2005-02-12 22:43 ` Olaf Dietsche
1 sibling, 0 replies; 45+ messages in thread
From: Olaf Dietsche @ 2005-02-12 22:43 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: Andrew Morton, linux-kernel
Christoph Hellwig <hch@infradead.org> writes:
> On Thu, Feb 10, 2005 at 02:35:08AM -0800, Andrew Morton wrote:
>>
>> - Added the mlock and !SCHED_OTHER Linux Security Module for the audio guys.
>> It seems that nothing else is going to come along and this is completely
>> encapsulated.
>
> Even if we accept a module that grants capabilities to groups this isn't fine
> yet because it only supports two specific capabilities (and even those two in
> different ways!) instead of adding generic support to bind capabilities to
> groups.
Unless I misunderstood the code, this one is available for
quite some time: <http://www.olafdietsche.de/linux/accessfs/>
or a newer, self-contained version <http://lkml.org/lkml/2005/1/11/221>
Or you could use a real solution - filesystem capabilities:
<http://www.olafdietsche.de/linux/capability/> and if you don't like
this one :-), there's also an alternative existing here:
<http://www.stanford.edu/~luto/linux-fscap/>
Regards, Olaf.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-11 16:29 ` 2.6.11-rc3-mm2 Yuval Tanny
@ 2005-02-12 14:53 ` Henning Rohde
0 siblings, 0 replies; 45+ messages in thread
From: Henning Rohde @ 2005-02-12 14:53 UTC (permalink / raw)
To: linux-kernel
Hi,
Yuval Tanny wrote:
> Andrew Morton wrote:
>>cachefs-filesystem.patch
>> CacheFS filesystem
> ...
as you mention cachefs - know what's the status of supporting nfs?
Or is the project as dead as the mailing-list?
Is there any whole-in-one patch relative to vanilla-sources,
at best including nfs-support?
Thanks in advance,
Henning Rohde
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-10 10:35 2.6.11-rc3-mm2 Andrew Morton
` (3 preceding siblings ...)
2005-02-10 23:17 ` 2.6.11-rc3-mm2 Adrian Bunk
@ 2005-02-11 16:29 ` Yuval Tanny
2005-02-12 14:53 ` 2.6.11-rc3-mm2 Henning Rohde
2005-02-14 13:22 ` 2.6.11-rc3-mm2 Stefano Rivoir
5 siblings, 1 reply; 45+ messages in thread
From: Yuval Tanny @ 2005-02-11 16:29 UTC (permalink / raw)
To: Andrew Morton, David Howells; +Cc: linux-kernel
In fs/Kconfig,
See "Documentation/filesystems/fscache.txt for more information." and
"See Documentation/filesystems/cachefs.txt for more information."
Should be changed to:
"See Documentation/filesystems/caching/fscache.txt for more
information." and "See Documentation/filesystems/caching/cachefs.txt for
more information."
Thanks,
Yuval
Andrew Morton wrote:
>cachefs-filesystem.patch
> CacheFS filesystem
>
>
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-10 23:02 ` 2.6.11-rc3-mm2 Andrew Morton
@ 2005-02-10 23:31 ` Benjamin Herrenschmidt
0 siblings, 0 replies; 45+ messages in thread
From: Benjamin Herrenschmidt @ 2005-02-10 23:31 UTC (permalink / raw)
To: Andrew Morton; +Cc: Linux Kernel list
> > Without the aty128fb and radeonfb updates, current 2.6.11 is a
> > regression on pmac as it breaks sleep support on previously working
> > laptops.
>
> Is that worse than the risk of the large patch?
Well, it used to work upstream fine for some time now... The large patch
isn't risky imho, at least in the latest version I sent you. The bulk of
the changes are just code to re-initialize new chip that isn't executed
at all on earlier models. The main radeonfb code changes very little. I
haven't had a failure report with the latest patch yet.
> > If you don't intend to get at least
> > try_to_acquire_console_sem() and aty128fb fix in, in which case i can
> > send you a minimal radeonfb patch, then I'll have to make another patch
> > for 2.6.11 that reverts some of the arch changes to re-enable sleep on
> > those machines.
>
> Ho hum. PM and fbdev are regularly broken anyway. Please always identify
> the patches by name - it helps avoid mistakes.
Ahem ... not that badly broken on releases, I've been careful enough
that at least, powerbook sleep worked fine for some time now.
> These?
>
> add-try_acquire_console_sem.patch
> update-aty128fb-sleep-wakeup-code-for-new-powermac-changes.patch
Those 2 first at least yes
> radeonfb-update.patch
> radeonfb-build-fix.patch
And either the above, or I can do a minimal patch on radeonfb just
restoring sleep on earlier models (adding the pmac_feature call to
notify the arch code that we can wakeup the chip) if you don't want to
merge the bigger update.
Ben.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-10 10:35 2.6.11-rc3-mm2 Andrew Morton
` (2 preceding siblings ...)
2005-02-10 22:42 ` 2.6.11-rc3-mm2 Benjamin Herrenschmidt
@ 2005-02-10 23:17 ` Adrian Bunk
2005-02-11 16:29 ` 2.6.11-rc3-mm2 Yuval Tanny
2005-02-14 13:22 ` 2.6.11-rc3-mm2 Stefano Rivoir
5 siblings, 0 replies; 45+ messages in thread
From: Adrian Bunk @ 2005-02-10 23:17 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Thu, Feb 10, 2005 at 02:35:08AM -0800, Andrew Morton wrote:
>...
> - Various other stuff. If anyone has a patch in here which they think
> should be in 2.6.11, please let me know. I'm intending to merge the
> following into 2.6.11:
>
> alpha-add-missing-dma_mapping_error.patch
> fix-compat-shmget-overflow.patch
> fix-shmget-for-ppc64-s390-64-sparc64.patch
> binfmt_elf-clearing-bss-may-fail.patch
> qlogic-warning-fixes.patch
> oprofile-exittext-referenced-in-inittext.patch
> force-read-implies-exec-for-all-32bit-processes-in-x86-64.patch
> oprofile-arm-xscale1-pmu-support-fix.patch
>...
As described in the patch description, I'd like to see
mark-the-mcd-cdrom-driver-as-broken.patch in 2.6.11 .
cu
Adrian
--
"Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
"Only a promise," Lao Er said.
Pearl S. Buck - Dragon Seed
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-10 22:42 ` 2.6.11-rc3-mm2 Benjamin Herrenschmidt
@ 2005-02-10 23:02 ` Andrew Morton
2005-02-10 23:31 ` 2.6.11-rc3-mm2 Benjamin Herrenschmidt
0 siblings, 1 reply; 45+ messages in thread
From: Andrew Morton @ 2005-02-10 23:02 UTC (permalink / raw)
To: Benjamin Herrenschmidt; +Cc: linux-kernel
Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>
> On Thu, 2005-02-10 at 02:35 -0800, Andrew Morton wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm2/
> >
> >
> > - Added the mlock and !SCHED_OTHER Linux Security Module for the audio guys.
> > It seems that nothing else is going to come along and this is completely
> > encapsulated.
> >
> > - Various other stuff. If anyone has a patch in here which they think
> > should be in 2.6.11, please let me know. I'm intending to merge the
> > following into 2.6.11:
> >
> > alpha-add-missing-dma_mapping_error.patch
> > fix-compat-shmget-overflow.patch
> > fix-shmget-for-ppc64-s390-64-sparc64.patch
> > binfmt_elf-clearing-bss-may-fail.patch
> > qlogic-warning-fixes.patch
> > oprofile-exittext-referenced-in-inittext.patch
> > force-read-implies-exec-for-all-32bit-processes-in-x86-64.patch
> > oprofile-arm-xscale1-pmu-support-fix.patch
>
> Without the aty128fb and radeonfb updates, current 2.6.11 is a
> regression on pmac as it breaks sleep support on previously working
> laptops.
Is that worse than the risk of the large patch?
> If you don't intend to get at least
> try_to_acquire_console_sem() and aty128fb fix in, in which case i can
> send you a minimal radeonfb patch, then I'll have to make another patch
> for 2.6.11 that reverts some of the arch changes to re-enable sleep on
> those machines.
Ho hum. PM and fbdev are regularly broken anyway. Please always identify
the patches by name - it helps avoid mistakes.
These?
add-try_acquire_console_sem.patch
update-aty128fb-sleep-wakeup-code-for-new-powermac-changes.patch
radeonfb-update.patch
radeonfb-build-fix.patch
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-10 10:35 2.6.11-rc3-mm2 Andrew Morton
2005-02-10 13:35 ` 2.6.11-rc3-mm2 Christoph Hellwig
2005-02-10 22:13 ` 2.6.11-rc3-mm2 Corey Minyard
@ 2005-02-10 22:42 ` Benjamin Herrenschmidt
2005-02-10 23:02 ` 2.6.11-rc3-mm2 Andrew Morton
2005-02-10 23:17 ` 2.6.11-rc3-mm2 Adrian Bunk
` (2 subsequent siblings)
5 siblings, 1 reply; 45+ messages in thread
From: Benjamin Herrenschmidt @ 2005-02-10 22:42 UTC (permalink / raw)
To: Andrew Morton; +Cc: Linux Kernel list
On Thu, 2005-02-10 at 02:35 -0800, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm2/
>
>
> - Added the mlock and !SCHED_OTHER Linux Security Module for the audio guys.
> It seems that nothing else is going to come along and this is completely
> encapsulated.
>
> - Various other stuff. If anyone has a patch in here which they think
> should be in 2.6.11, please let me know. I'm intending to merge the
> following into 2.6.11:
>
> alpha-add-missing-dma_mapping_error.patch
> fix-compat-shmget-overflow.patch
> fix-shmget-for-ppc64-s390-64-sparc64.patch
> binfmt_elf-clearing-bss-may-fail.patch
> qlogic-warning-fixes.patch
> oprofile-exittext-referenced-in-inittext.patch
> force-read-implies-exec-for-all-32bit-processes-in-x86-64.patch
> oprofile-arm-xscale1-pmu-support-fix.patch
Without the aty128fb and radeonfb updates, current 2.6.11 is a
regression on pmac as it breaks sleep support on previously working
laptops. If you don't intend to get at least
try_to_acquire_console_sem() and aty128fb fix in, in which case i can
send you a minimal radeonfb patch, then I'll have to make another patch
for 2.6.11 that reverts some of the arch changes to re-enable sleep on
those machines.
Ben.
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-10 10:35 2.6.11-rc3-mm2 Andrew Morton
2005-02-10 13:35 ` 2.6.11-rc3-mm2 Christoph Hellwig
@ 2005-02-10 22:13 ` Corey Minyard
2005-02-10 22:42 ` 2.6.11-rc3-mm2 Benjamin Herrenschmidt
` (3 subsequent siblings)
5 siblings, 0 replies; 45+ messages in thread
From: Corey Minyard @ 2005-02-10 22:13 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
Andrew Morton wrote:
>ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm2/
>
>
>- Added the mlock and !SCHED_OTHER Linux Security Module for the audio guys.
> It seems that nothing else is going to come along and this is completely
> encapsulated.
>
>- Various other stuff. If anyone has a patch in here which they think
> should be in 2.6.11, please let me know. I'm intending to merge the
> following into 2.6.11:
>
> alpha-add-missing-dma_mapping_error.patch
> fix-compat-shmget-overflow.patch
> fix-shmget-for-ppc64-s390-64-sparc64.patch
> binfmt_elf-clearing-bss-may-fail.patch
> qlogic-warning-fixes.patch
> oprofile-exittext-referenced-in-inittext.patch
> force-read-implies-exec-for-all-32bit-processes-in-x86-64.patch
> oprofile-arm-xscale1-pmu-support-fix.patch
>
>
>
>
The following one should probably go in:
>+update-to-ipmi-driver-to-support-old-dmi-spec.patch
>
>
Systems with old data will not work correctly without it. There seems
to be a few of them out there.
-Corey
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-10 13:35 ` 2.6.11-rc3-mm2 Christoph Hellwig
@ 2005-02-10 20:01 ` Andrew Morton
2005-02-12 22:43 ` 2.6.11-rc3-mm2 Olaf Dietsche
1 sibling, 0 replies; 45+ messages in thread
From: Andrew Morton @ 2005-02-10 20:01 UTC (permalink / raw)
To: Christoph Hellwig; +Cc: linux-kernel, Jack O'Quin
Christoph Hellwig <hch@infradead.org> wrote:
>
> On Thu, Feb 10, 2005 at 02:35:08AM -0800, Andrew Morton wrote:
> >
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm2/
> >
> >
> > - Added the mlock and !SCHED_OTHER Linux Security Module for the audio guys.
> > It seems that nothing else is going to come along and this is completely
> > encapsulated.
>
> Even if we accept a module that grants capabilities to groups this isn't fine
> yet because it only supports two specific capabilities (and even those two in
> different ways!) instead of adding generic support to bind capabilities to
> groups.
I'm sure that got discussed somewhere in the 1000 emails which flew past
last time. Jack?
^ permalink raw reply [flat|nested] 45+ messages in thread
* Re: 2.6.11-rc3-mm2
2005-02-10 10:35 2.6.11-rc3-mm2 Andrew Morton
@ 2005-02-10 13:35 ` Christoph Hellwig
2005-02-10 20:01 ` 2.6.11-rc3-mm2 Andrew Morton
2005-02-12 22:43 ` 2.6.11-rc3-mm2 Olaf Dietsche
2005-02-10 22:13 ` 2.6.11-rc3-mm2 Corey Minyard
` (4 subsequent siblings)
5 siblings, 2 replies; 45+ messages in thread
From: Christoph Hellwig @ 2005-02-10 13:35 UTC (permalink / raw)
To: Andrew Morton; +Cc: linux-kernel
On Thu, Feb 10, 2005 at 02:35:08AM -0800, Andrew Morton wrote:
>
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm2/
>
>
> - Added the mlock and !SCHED_OTHER Linux Security Module for the audio guys.
> It seems that nothing else is going to come along and this is completely
> encapsulated.
Even if we accept a module that grants capabilities to groups this isn't fine
yet because it only supports two specific capabilities (and even those two in
different ways!) instead of adding generic support to bind capabilities to
groups.
More comments on the actual code:
+#include <linux/module.h>
+#include <linux/security.h>
+
+#define RT_LSM "Realtime LSM " /* syslog module name prefix */
+#define RT_ERR "Realtime: " /* syslog error message prefix */
+#include <linux/vermagic.h>
+MODULE_INFO(vermagic,VERMAGIC_STRING);
This doesn't belong into a module.
+#define MY_NAME __stringify(KBUILD_MODNAME)
Please use normal prefix. A module shouldn't behave differently depending on
what name you compile it as.
^ permalink raw reply [flat|nested] 45+ messages in thread
* 2.6.11-rc3-mm2
@ 2005-02-10 10:35 Andrew Morton
2005-02-10 13:35 ` 2.6.11-rc3-mm2 Christoph Hellwig
` (5 more replies)
0 siblings, 6 replies; 45+ messages in thread
From: Andrew Morton @ 2005-02-10 10:35 UTC (permalink / raw)
To: linux-kernel
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc3/2.6.11-rc3-mm2/
- Added the mlock and !SCHED_OTHER Linux Security Module for the audio guys.
It seems that nothing else is going to come along and this is completely
encapsulated.
- Various other stuff. If anyone has a patch in here which they think
should be in 2.6.11, please let me know. I'm intending to merge the
following into 2.6.11:
alpha-add-missing-dma_mapping_error.patch
fix-compat-shmget-overflow.patch
fix-shmget-for-ppc64-s390-64-sparc64.patch
binfmt_elf-clearing-bss-may-fail.patch
qlogic-warning-fixes.patch
oprofile-exittext-referenced-in-inittext.patch
force-read-implies-exec-for-all-32bit-processes-in-x86-64.patch
oprofile-arm-xscale1-pmu-support-fix.patch
Changes since 2.6.11-rc3-mm1:
linus.patch
bk-agpgart.patch
bk-alsa.patch
bk-arm.patch
bk-cifs.patch
bk-cpufreq.patch
bk-drm-via.patch
bk-i2c.patch
bk-ieee1394.patch
bk-input.patch
bk-dtor-input.patch
bk-jfs.patch
bk-kbuild.patch
bk-kconfig.patch
bk-netdev.patch
bk-ntfs.patch
bk-scsi.patch
bk-scsi-rc-fixes.patch
bk-serial.patch
bk-usb.patch
bk-watchdog.patch
bk-xfs.patch
External bk trees.
-fix-an-error-in-proc-slabinfo-print.patch
-ibmveth-inlining-failure.patch
-fix-devfs-name-for-the-hvcs-driver.patch
-uml-compile-fixes.patch
-include-jiffies-fix-usecs_to_jiffies-jiffies_to_usecs-math.patch
-credits-update.patch
-nfsd-needs-exportfs.patch
-input-make-mousedevc-report-all-events-to-user-space-immediately.patch
-input-enable-hardware-tapping-for-alps-touchpads.patch
-input-fix-pointer-jumps-to-corner-of-screen-problem-on-alps-glidepoint-touchpads.patch
-input-add-support-for-synaptics-touchpad-scroll-wheels.patch
-driver-model-fix-types-in-usb.patch
-kswapd-throttling-fix.patch
-task_size-is-variable.patch
-use-mm_vm_size-in-exit_mmap.patch
-ppc64-correct-return-code-in-syscall-auditing.patch
-ppc64-show-1-for-physical_id-of-non-present-cpus.patch
-ppc64-replace-last-usage-of-vio-dma-mapping-routines.patch
-speedstep-libc-fix-frequency-multiplier-for-pentium4.patch
-x86_64-parse-noexec=.patch
-force-feedback-support-for-uinput.patch
-pcmcia-dc-initialisation-fix.patch
-scsi-megaraid_mmc-make-some-code-static.patch
-add-map_populate-sys_remap_file_pages-support-to-xfs.patch
-acpi-call-acpi_leave_sleep_state-before-resuming-devices.patch
-small-partitions-msdos-cleanups.patch
-scsi-sim710c-make-some-code-static.patch
Merged
+alpha-add-missing-dma_mapping_error.patch
Alpha build fix
+fix-compat-shmget-overflow.patch
+fix-shmget-for-ppc64-s390-64-sparc64.patch
Various compat code sign extension fixes
+binfmt_elf-clearing-bss-may-fail.patch
Fix the weird elf loading failure
+qlogic-warning-fixes.patch
smp_processor_id() warnings
+oprofile-exittext-referenced-in-inittext.patch
oprofile section fix
+force-read-implies-exec-for-all-32bit-processes-in-x86-64.patch
Partly fix up the x86_64 noexec mapping problem.
+oprofile-arm-xscale1-pmu-support-fix.patch
oprofile fix
+nfsd--sgi-921857-find-broken-with-nohide-on-nfsv3.patch
+nfsd--exportfs-reduce-stack-usage.patch
+nfsd--svcrpc-add-a-per-flavor-set_client-method.patch
+nfsd--svcrpc-rename-pg_authenticate.patch
+nfsd--svcrpc-move-export-table-checks-to-a-per-program-pg_add_client-method.patch
+nfsd--nfs4-use-new-pg_set_client-method-to-simplify-nfs4-callback-authentication.patch
+nfsd--lockd-dont-try-to-match-callback-requests-against-export-table.patch
+nfsd--nfsd-remove-pg_authenticate-field.patch
+nfsd--global-static-cleanups-for-nfsd.patch
+nfsd--change-nfsd-reply-cache-to-use-listh-lists.patch
nfsd update
+acpi-fix-containers-notify-handler-to-handle-proper-cases-properly.patch
+acpi_power_off-bug-fix.patch
ACPI fixes
+update-to-ipmi-driver-to-support-old-dmi-spec.patch
+add-the-ipmi-smbus-driver-fix-fix.patch
IPMI fixes
+ohci1394-dma_pool_destroy-while-in_atomic-irqs_disabled.patch
1394 fix
+sbp2-fix-hang-on-unload.patch
Another 1394 fix
+serio-warning-fix.patch
+twidjoy-build-fix.patch
input code fixes
+compat-ioctl-for-submiting-urb.patch
+compat-ioctl-for-submiting-urb-fix.patch
Add compatibility emulation for the USB URB-direct-submission code.
+swapspace-layout-improvements-fix.patch
Fix swapspace-layout-improvements.patch
+fix-small-vmalloc-per-allocation-limit.patch
Make monster vmalloc()s work
+randomisation-global-sysctl-fix.patch
Fix randomisation-global-sysctl.patch
+fix-compilation-of-uml-after-the-stack-randomization-patches.patch
Fix randomisation-infrastructure.patch
+invalidate-range-of-pages-after-direct-io-write-fix-fix.patch
+write-and-wait-on-range-before-direct-io-read.patch
+only-unmap-what-intersects-a-direct_io-op.patch
Various optimisations for page unmapping, mainly related to direct-IO.
+net-s2io-replace-schedule_timeout-with-msleep.patch
cleanup
+ppc-ppc64-abstract-cpu_feature-checks.patch
+ppc32-dont-create-tmp_gas_check.patch
+ppc32-fix-mv64x60-register-relocation-bug-in-bootwrapper.patch
ppc32 updates
+ppc64-remove-unneeded-includes-from-pseries_nvramc.patch
+ppc64-collect-and-export-low-level-cpu-usage-statistics.patch
+ppc64-defconfig-updates.patch
+ppc64-distribute-export_symbols.patch
+ppc64-disable-hmt-for-rs64-cpus.patch
+use-vmlinux-during-make-install-on-ppc64.patch
+ppc64-functions-to-reserve-performance-monitor-hardware.patch
ppc64 updates
+mips-add-tanbac-tb0219-base-board-driver.patch
mips board driver
+refactor-i386-memory-setup.patch
+consolidate-set_max_mapnr_init-implementations.patch
+remove-free_all_bootmem-define.patch
x86 mm cleanups
+out-of-line-x86-put_user-implementation.patch
move x86 put_user() out of line.
+x86_64-hugetlb-fix.patch
hugepage fix
+swsusp-do-not-use-higher-order-memory-allocations-on-suspend-fix.patch
+swsusp-do-not-use-higher-order-memory-allocations-on-suspend-fix-fix.patch
Fix swsusp-do-not-use-higher-order-memory-allocations-on-suspend.patch
+fix-partial-sysrq-setting.patch
Fix a -mm-only sysrq patch
+touch_softlockup_watchdog.patch
+fix-softlockup-warning-in-swsuspend-resume.patch
Enhancements to detect-soft-lockups.patch
+add-struct-request-end_io-callback-fix.patch
Fix add-struct-request-end_io-callback.patch
+add-compiler-gcc4h.patch
cleanup
+rt-lsm.patch
realtime+mlock LSM
+convert-proc-driver-rtc-to-seq_file.patch
RTC driver /proc seqfile conversion
+drivers-char-lpc-race-fix.patch
Fix obscure line printer driver race
+clean-up-and-unify-asm-resourceh-files.patch
Code cleanup
-base-small-shrink-major_names-hash.patch
This broke stuff
+sort-fix.patch
Make the new sort function place things in sorted order.
-inotify.patch
-inotify-fix_find_inode.patch
I think my version is old, and it oopses.
+pcmcia-add-support-ti-pci4510-cardbus-bridge.patch
+pcmcia-update-vrc4171_card.patch
PCMCIA device updates
+nfsv4-deamon-always-supports-acls.patch
NFS ACL Kconfig fix
+add-do_proc_doulonglongvec_minmax-to-sysctl-functions.patch
+add-sysctl-interface-to-sched_domain-parameters.patch
We found the cause of the weird ia64 oops (extable sorting was wrong), so
bring these back.
+crashdump-routines-for-copying-dump-pages-fixes.patch
+crashdump-linear-raw-format-dump-file-access-coding-style.patch
crashdump coding cleanups
+radeonfb-fix-spurious-error-return-in-fbio_radeon_set_mirror.patch
+w100fb-make-blanking-function-interrupt-safe.patch
+kyrofb-copy__user-return-value-checks-added-to-kyro-fb.patch
+skeletonfb-documentation-fixes.patch
+intelfb-add-partial-support-915g-chipset.patch
+sisfb_compat_ioctl-warning-fix.patch
+sis-warning-fix.patch
+tridentfb-warning-fix.patch
fbdev updates and fixes
-raid5-overlapping-read-hack.patch
This got fixed for real
+md-fix-multipath-assembly-bug.patch
+md-raid-kconfig-cleanups-remove-experimental-tag-from-raid-6.patch
MD updates
+device-mapper-store-name-directly-against-device.patch
+device-mapper-record-restore-bio-state.patch
+device-mapper-export-map_info.patch
DM updates
+update-documentation-filesystems-locking.patch
Update the VFS locking doc for quotas
+hpet-setup-comment-fix.patch
+fs-ncpfs-ncplib_kernelc-make-a-function-static.patch
+kill-iphase5526.patch
+fs-nfs-make-some-code-static.patch
+i386-x86_64-acpi-sleepc-kill-unused-acpi_save_state_disk.patch
+smpbootc-cleanups.patch
+i386-kernel-i387c-misc-cleanups.patch
+i386-x86_64-i8259c-make-mask_and_ack_8259a-static.patch
+scsi-sym53c416c-make-a-function-static.patch
+scsi-ultrastorc-make-a-variable-static.patch
+tridentfbc-make-some-code-static.patch
+kernel-intermodulec-make-inter_module_get-static.patch
Various nanofixes
number of patches in -mm: 585
number of changesets in external trees: 634
number of patches in -mm only: 564
total patches: 1198
All 585 patches:
linus.patch
alpha-add-missing-dma_mapping_error.patch
alpha: add missing dma_mapping_error
fix-compat-shmget-overflow.patch
Fix compat shmget overflow
fix-shmget-for-ppc64-s390-64-sparc64.patch
Fix shmget for ppc64, s390-64 & sparc64.
binfmt_elf-clearing-bss-may-fail.patch
binfmt_elf: clearing bss may fail
qlogic-warning-fixes.patch
more qlogic smp_processor_id() warning fixes
oprofile-exittext-referenced-in-inittext.patch
OProfile: exit.text referenced in init.text
force-read-implies-exec-for-all-32bit-processes-in-x86-64.patch
Force read implies exec for all 32bit processes in x86-64
oprofile-arm-xscale1-pmu-support-fix.patch
OProfile: ARM/XScale1 PMU support fix
nfsd--sgi-921857-find-broken-with-nohide-on-nfsv3.patch
SGI 921857: find broken with nohide on NFSv3
nfsd--exportfs-reduce-stack-usage.patch
nfsd: exportfs: reduce stack usage
nfsd--svcrpc-add-a-per-flavor-set_client-method.patch
nfsd: svcrpc: add a per-flavor set_client method
nfsd--svcrpc-rename-pg_authenticate.patch
nfsd: svcrpc: rename pg_authenticate
nfsd--svcrpc-move-export-table-checks-to-a-per-program-pg_add_client-method.patch
nfsd: svcrpc: move export table checks to a per-program pg_add_client method
nfsd--nfs4-use-new-pg_set_client-method-to-simplify-nfs4-callback-authentication.patch
nfsd: nfs4: use new pg_set_client method to simplify nfs4 callback authentication
nfsd--lockd-dont-try-to-match-callback-requests-against-export-table.patch
nfsd: lockd: don't try to match callback requests against export table
nfsd--nfsd-remove-pg_authenticate-field.patch
nfsd: nfsd: remove pg_authenticate field
nfsd--global-static-cleanups-for-nfsd.patch
nfsd: global/static cleanups for nfsd
nfsd--change-nfsd-reply-cache-to-use-listh-lists.patch
nfsd: change nfsd reply cache to use list.h lists
ia64-config_apci_numa-fix.patch
ia64 CONFIG_APCI_NUMA fix
ia64-acpi-build-fix.patch
ia64 acpi build fix
add-try_acquire_console_sem.patch
Add try_acquire_console_sem
update-aty128fb-sleep-wakeup-code-for-new-powermac-changes.patch
update aty128fb sleep/wakeup code for new powermac changes
radeonfb-update.patch
radeonfb update
radeonfb-build-fix.patch
radeonfb-build-fix
acpi-sleep-while-atomic-during-s3-resume-from-ram.patch
acpi: sleep-while-atomic during S3 resume from ram
acpi-report-errors-in-fanc.patch
ACPI: report errors in fan.c
acpi-flush-tlb-when-pagetable-changed.patch
acpi: flush TLB when pagetable changed
fix-an-issue-in-acpi-processor-and-container-drivers-related-with-kobject_hotplug.patch
Fix an issue in ACPI processor and container drivers related with kobject_hotplug()
acpi-fix-containers-notify-handler-to-handle-proper-cases-properly.patch
acpi: fix container's notify handler to handle proper cases properly
acpi_power_off-bug-fix.patch
acpi_power_off bug fix
bk-agpgart.patch
bk-alsa.patch
fix-32-bit-calls-to-snd_pcm_channel_info.patch
Fix 32-bit calls to snd_pcm_channel_info()
bk-arm.patch
bk-cifs.patch
bk-cpufreq.patch
cpufreq-core-reduce-warning-messages.patch
cpufreq-core: reduce warning messages
bk-drm-via.patch
bk-i2c.patch
changes-to-the-i2c-driver-to-support-a-non-blocking-interface.patch
Changes to the I2C driver to support a non-blocking interface
minor-ipmi-enhancements.patch
Minor IPMI enhancements
update-to-ipmi-driver-to-support-old-dmi-spec.patch
Update to IPMI driver to support old DMI spec
modify-the-i801-i2c-driver-to-use-the-non-blocking-interface.patch
Modify the i801 I2C driver to use the non-blocking interface.
add-the-ipmi-smbus-driver.patch
Add the IPMI SMBus driver
add-the-ipmi-smbus-driver-fix.patch
ipmi-build-fix-42
add-the-ipmi-smbus-driver-fix-fix.patch
add-the-ipmi-smbus-driver-fix fix
bk-ieee1394.patch
ohci1394-dma_pool_destroy-while-in_atomic-irqs_disabled.patch
ohci1394: dma_pool_destroy while in_atomic() && irqs_disabled()
ohci1394-dma_pool_destroy-while-in_atomic-irqs_disabled-tidy
ohci1394-dma_pool_destroy-while-in_atomic-irqs_disabled-simplification
sbp2-fix-hang-on-unload.patch
sbp2: fix hang on unload
bk-input.patch
bk-dtor-input.patch
serio-warning-fix.patch
serio warning fix
twidjoy-build-fix.patch
twidjoy-build-fix
bk-jfs.patch
bk-kbuild.patch
bk-kconfig.patch
bk-netdev.patch
bk-ntfs.patch
bk-scsi.patch
bk-scsi-rc-fixes.patch
bk-serial.patch
bk-usb.patch
compat-ioctl-for-submiting-urb.patch
compat ioctl for submiting URB
compat-ioctl-for-submiting-urb-fix.patch
compat-ioctl-for-submiting-urb-fix
bk-watchdog.patch
bk-xfs.patch
mm.patch
add -mmN to EXTRAVERSION
vm-pageout-throttling.patch
vm: pageout throttling
orphaned-pagecache-memleak-fix.patch
orphaned pagecache memleak fix
swapspace-layout-improvements.patch
swapspace-layout-improvements
swapspace-layout-improvements-fix.patch
/proc/swaps negative Used
simpler-topdown-mmap-layout-allocator.patch
simpler topdown mmap layout allocator
vmscan-reclaim-swap_cluster_max-pages-in-a-single-pass.patch
vmscan: reclaim SWAP_CLUSTER_MAX pages in a single pass
fix-mincore-cornercases-overflow-caused-by-large-len.patch
Fix mincore cornercases: overflow caused by large "len"
fix-small-vmalloc-per-allocation-limit.patch
Fix small vmalloc per allocation limit
randomisation-global-sysctl.patch
Randomisation: global sysctl
randomisation-global-sysctl-fix.patch
randomisation-global-sysctl-fix
randomisation-infrastructure.patch
Randomisation: infrastructure
fix-compilation-of-uml-after-the-stack-randomization-patches.patch
Fix compilation of UML after the stack-randomization patches
randomisation-add-pf_randomize.patch
Randomisation: add PF_RANDOMIZE
randomisation-stack-randomisation.patch
Randomisation: stack randomisation
randomisation-mmap-randomisation.patch
Randomisation: mmap randomisation
randomisation-enable-by-default.patch
Randomisation: enable by default
randomisation-addr_no_randomize-personality.patch
Randomisation: add ADDR_NO_RANDOMIZE personality
randomisation-top-of-stack-randomization.patch
Randomisation: top-of-stack randomization
move-accounting-function-calls-out-of-critical-vm-code-pathspatch.patch
Move accounting function calls out of critical vm code paths
invalidate-range-of-pages-after-direct-io-write.patch
invalidate range of pages after direct IO write
invalidate-range-of-pages-after-direct-io-write-fix.patch
invalidate-range-of-pages-after-direct-io-write-fix
invalidate-range-of-pages-after-direct-io-write-fix-fix.patch
invalidate-range-of-pages-after-direct-io-write-fix-fix
write-and-wait-on-range-before-direct-io-read.patch
write and wait on range before direct io read
only-unmap-what-intersects-a-direct_io-op.patch
only unmap what intersects a direct_IO op
make-tree_lock-an-rwlock.patch
make mapping->tree_lock an rwlock
must-fix.patch
must fix lists update
must fix list update
mustfix update
must-fix update
mustfix lists
b44-bounce-buffer-fix.patch
b44 bounce buffering fix
net-s2io-replace-schedule_timeout-with-msleep.patch
net/s2io: replace schedule_timeout() with msleep()
ppc-ppc64-abstract-cpu_feature-checks.patch
PPC/PPC64: Abstract cpu_feature checks.
ppc32-dont-create-tmp_gas_check.patch
ppc32: Don't create .tmp_gas_check
ppc32-fix-mv64x60-register-relocation-bug-in-bootwrapper.patch
ppc32: fix mv64x60 register relocation bug in bootwrapper
ppc64-remove-unneeded-includes-from-pseries_nvramc.patch
remove unneeded includes from pSeries_nvram.c
ppc64-collect-and-export-low-level-cpu-usage-statistics.patch
ppc64: collect and export low-level cpu usage statistics
ppc64-move-systemcfg-out-of-heads.patch
ppc64: Move systemcfg out of head.S
ppc64-defconfig-updates.patch
ppc64: defconfig updates
ppc64-distribute-export_symbols.patch
ppc64: distribute EXPORT_SYMBOLs
ppc64-implement-a-vdso-and-use-it-for-signal-trampoline.patch
ppc64: Implement a vDSO and use it for signal trampoline
ppc64-generic-hotplug-cpu-support.patch
ppc64: generic hotplug cpu support
ppc64-disable-hmt-for-rs64-cpus.patch
ppc64: disable HMT for RS64 cpus
use-vmlinux-during-make-install-on-ppc64.patch
ppc64: use vmlinux during make install on ppc64
ppc64-functions-to-reserve-performance-monitor-hardware.patch
ppc64: functions to reserve performance monitor hardware
ppc64-reloc_hide.patch
agpgart-allow-multiple-backends-to-be-initialized.patch
agpgart: allow multiple backends to be initialized
agpgart-allow-multiple-backends-to-be-initialized fix
agpgart: add bridge assignment missed in agp_allocate_memory
x86_64 agp failure fix
agpgart-allow-multiple-backends-to-be-initialized-fix.patch
agpgart-allow-multiple-backends-to-be-initialized-fix
agpgart-add-agp_find_bridge-function.patch
agpgart: add agp_find_bridge function
agpgart-allow-drivers-to-allocate-memory-local-to.patch
agpgart: allow drivers to allocate memory local to the bridge
drm-add-support-for-new-multiple-agp-bridge-agpgart-api.patch
drm: add support for new multiple agp bridge agpgart api
fb-add-support-for-new-multiple-agp-bridge-agpgart-api.patch
fb: add support for new multiple agp bridge agpgart api
agpgart-add-bridge-parameter-to-driver-functions.patch
agpgart: add bridge parameter to driver functions
mips-add-tanbac-tb0219-base-board-driver.patch
mips: add TANBAC TB0219 base board driver
allow-hot-add-enabled-i386-numa-box-to-boot.patch
Allow hot-add enabled i386 NUMA box to boot
refactor-i386-memory-setup.patch
x86: refactor memory setup
consolidate-set_max_mapnr_init-implementations.patch
x86: consolidate set_max_mapnr_init() implementations
remove-free_all_bootmem-define.patch
x86: remove-free_all_bootmem() #define
out-of-line-x86-put_user-implementation.patch
out-of-line x86 "put_user()" implementation
x86_64-hugetlb-fix.patch
x86_64: hugetlb fix
xen-vmm-4-add-ptep_establish_new-to-make-va-available.patch
Xen VMM #4: add ptep_establish_new to make va available
xen-vmm-4-return-code-for-arch_free_page.patch
Xen VMM #4: return code for arch_free_page
xen-vmm-4-return-code-for-arch_free_page-fix.patch
Get rid of arch_free_page() warning
xen-vmm-4-runtime-disable-of-vt-console.patch
Xen VMM #4: runtime disable of VT console
xen-vmm-4-has_arch_dev_mem.patch
Xen VMM #4: HAS_ARCH_DEV_MEM
xen-vmm-4-split-free_irq-into-teardown_irq.patch
Xen VMM #4: split free_irq into teardown_irq
swsusp-do-not-use-higher-order-memory-allocations-on-suspend.patch
swsusp: do not use higher order memory allocations on suspend
swsusp-do-not-use-higher-order-memory-allocations-on-suspend-fix.patch
swsusp-do-not-use-higher-order-memory-allocations-on-suspend fix
swsusp-do-not-use-higher-order-memory-allocations-on-suspend-fix-fix.patch
swsusp-do-not-use-higher-order-memory-allocations-on-suspend fix fix
make-sysrq-f-call-oom_kill.patch
make sysrq-F call oom_kill()
allow-admin-to-enable-only-some-of-the-magic-sysrq-functions.patch
Allow admin to enable only some of the Magic-Sysrq functions
fix-partial-sysrq-setting.patch
Fix partial sysrq setting
sort-out-pci_rom_address_enable-vs-ioresource_rom_enable.patch
Sort out PCI_ROM_ADDRESS_ENABLE vs IORESOURCE_ROM_ENABLE
irqpoll.patch
irqpoll
poll-mini-optimisations.patch
poll: mini optimisations
mtrr-size-and-base-debug.patch
mtrr size-and-base debugging
cleanup-vc-array-access.patch
cleanup vc array access
remove-console_macrosh.patch
remove console_macros.h
merge-vt_struct-into-vc_data.patch
merge vt_struct into vc_data
merge-vt_struct-into-vc_data-fix.patch
merge-vt_struct-into-vc_data fix
jbd-journal-overflow-fix-2.patch
jbd: journal overflow fix #2
jbd-fix-against-journal-overflow.patch
JBD: reduce stack and number of journal descriptors
jbd-fix-against-journal-overflow-tidies.patch
jbd-fix-against-journal-overflow-tidies
jbd-log-space-management-optimization.patch
JBD: log space management optimization
factor-out-phase-6-of-journal_commit_transaction.patch
Factor out phase 6 of journal_commit_transaction
ext3-cleanup-1.patch
ext3 cleanup 1
ext3-free-block-accounting-fix.patch
ext3: free block accounting fix
ext3_test_root-speedup.patch
ext3_test_root() speedup
i4l-new-hfc_usb-driver-version.patch
i4l: new hfc_usb driver version
i4l-hfc-4s-and-hfc-8s-driver.patch
i4l: HFC-4S and HFC-8S driver
fix-race-between-the-nmi-code-and-the-cmos-clock.patch
Fix race between the NMI code and the CMOS clock
cant-unmount-bad-inode.patch
Can't unmount bad inode
iounmap-debugging.patch
iounmap debugging
fix-put_user-under-mmap_sem-in-sys_get_mempolicy.patch
fix put_user under mmap_sem in sys_get_mempolicy()
oss-support-for-ac97-low-power-codecs.patch
OSS Support for AC97 low power codecs
fix-kallsyms-insmod-rmmod-race.patch
Fix kallsyms/insmod/rmmod race
fix-kallsyms-insmod-rmmod-race-fix.patch
fix-kallsyms-insmod-rmmod-race fix
fix-kallsyms-insmod-rmmod-race-fix-fix.patch
fix-kallsyms-insmod-rmmod-race-fix-fix
d_drop-should-use-per-dentry-lock.patch
d_drop should use per dentry lock
detect-soft-lockups.patch
detect soft lockups
touch_softlockup_watchdog.patch
touch_softlockup_watchdog()
fix-softlockup-warning-in-swsuspend-resume.patch
fix softlockup warning in swsuspend resume
serialize-access-to-ide-devices.patch
serialize access to ide devices
add-struct-request-end_io-callback.patch
Add struct request end_io callback
add-struct-request-end_io-callback-fix.patch
add-struct-request-end_io-callback fix
rework-core-barrier-support.patch
rework core barrier support
scsi_io_completion-sense-copy.patch
scsi_io_completion sense copy
blk_execute_rq-oops-on-fast-completion.patch
blk_execute_rq() oops on fast completion
nls_cp936c-is-not-synchronized-with-ms-translation-table.patch
nls_cp936.c is not synchronized with M$'s translation table
annotate-proc-pid-maps-with--markers.patch
annotate /proc/<PID>/maps with [heap]/[stack]/[vdso] markers
serial-add-nec-vr4100-series-serial-support.patch
serial: add NEC VR4100 series serial support
sys_setpriority-euid-semantics-fix.patch
sys_setpriority() euid semantics fix
add-tcsbrkp-to-compat_ioctlh.patch
add TCSBRKP to compat_ioctl.h
areca-raid-linux-scsi-driver.patch
ARECA RAID Linux scsi driver
add-local-bio-pool-support-and-modify-dm.patch
add local bio pool support and modify dm
add-local-bio-pool-support-and-modify-dm-uninline-zero_fill_bio.patch
uninline-zero_fill_bio
minor-conceptual-fix-for-proc-kcore-header-size.patch
minor conceptual fix for /proc/kcore header size
floppy-add-sysfs-symlink.patch
floppy.c: add sysfs symlink
add-compiler-gcc4h.patch
add compiler-gcc4.h
rt-lsm.patch
RT-LSM
convert-proc-driver-rtc-to-seq_file.patch
convert /proc/driver/rtc to seq_file.
drivers-char-lpc-race-fix.patch
drivers/char/lp.c race fix
clean-up-and-unify-asm-resourceh-files.patch
clean up and unify asm-*/resource.h files
base-small-introduce-the-config_base_small-flag.patch
base-small: introduce the CONFIG_BASE_SMALL flag
base-small-shrink-chrdevs-hash.patch
base-small: shrink chrdevs hash
base-small-shrink-pid-tables.patch
base-small: shrink PID tables
base-small-shrink-uid-hash.patch
base-small: shrink UID hash
base-small-shrink-futex-queues.patch
base-small: shrink futex queues
base-small-shrink-timer-hashes.patch
base-small: shrink timer hashes
base-small-shrink-console-buffer.patch
base-small: shrink console buffer
lib-sort-heapsort-implementation-of-sort.patch
lib/sort: Heapsort implementation of sort()
sort-fix.patch
sort fix
sort-export.patch
sort export
sort-build-fix.patch
sort build fix
lib-sort-turn-off-self-test.patch
lib/sort: turn off self-test
lib-sort-replace-qsort-in-xfs.patch
lib/sort: Replace qsort in XFS
lib-sort-replace-insertion-sort-in-exception-tables.patch
lib/sort: Replace insertion sort in exception tables
lib-sort-replace-insertion-sort-in-ia64-exception-tables.patch
lib/sort: Replace insertion sort in IA64 exception tables
lib-sort-use-generic-sort-on-x86_64.patch
lib/sort: Use generic sort on x86_64
random-pt2-cleanup-waitqueue-logic-fix-missed-wakeup.patch
random: cleanup waitqueue logic, fix missed wakeup
random-pt2-kill-pool-clearing.patch
random: kill pool clearing
random-pt2-combine-legacy-ioctls.patch
random: combine legacy ioctls
random-pt2-re-init-all-pools-on-zero.patch
random: re-init all pools on zero
random-pt2-simplify-initialization.patch
random: simplify initialization
random-pt2-kill-memsets-of-static-data.patch
random: kill memsets of static data
random-pt2-kill-dead-extract_state-struct.patch
random: kill dead extract_state struct
random-pt2-kill-22-compat-waitqueue-defs.patch
random: kill 2.2 compat waitqueue defs
random-pt2-kill-redundant-rotate_left-definitions.patch
random: kill redundant rotate_left definitions
random-pt2-kill-redundant-rotate_left-definitions-fix.patch
rol32 thinko
random-pt2-kill-misnamed-log2.patch
random: kill misnamed log2
random-pt3-more-meaningful-pool-names.patch
random: More meaningful pool names
random-pt3-static-allocation-of-pools.patch
random: Static allocation of pools
random-pt3-static-sysctl-bits.patch
random: Static sysctl bits
random-pt3-catastrophic-reseed-checks.patch
random: Catastrophic reseed checks
random-pt3-entropy-reservation-accounting.patch
random: Entropy reservation accounting
random-pt3-reservation-flag-in-pool-struct.patch
random: Reservation flag in pool struct
random-pt3-reseed-pointer-in-pool-struct.patch
random: Reseed pointer in pool struct
random-pt3-break-up-extract_user.patch
random: Break up extract_user
random-pt3-remove-dead-md5-copy.patch
random: Remove dead MD5 copy
random-pt3-simplify-hash-folding.patch
random: Simplify hash folding
random-pt3-clean-up-hash-buffering.patch
random: Clean up hash buffering
random-pt3-remove-entropy-batching.patch
random: Remove entropy batching
random-pt4-create-new-rol32-ror32-bitops.patch
random: Create new rol32/ror32 bitops
random-pt4-use-them-throughout-the-tree.patch
random: Use them throughout the tree
random-pt4-kill-the-sha-variants.patch
random: Kill the SHA variants
random-pt4-cleanup-sha-interface.patch
random: Cleanup SHA interface
random-pt4-move-sha-code-to-lib.patch
random: Move SHA code to lib/
random-pt4-replace-sha-with-faster-version.patch
random: Replace SHA with faster version
random-pt4-replace-sha-with-faster-version-fix.patch
random-pt4-replace-sha-with-faster-version-fix
random-pt4-replace-sha-with-faster-version-fix-fix.patch
SHA1 clarify kerneldoc
random-pt4-replace-sha-with-faster-version-fix-fix-fix.patch
random-pt4-cleanup-sha-interface fix
random-pt4-update-cryptolib-to-use-sha-fro-lib.patch
random: Update cryptolib to use SHA fro lib
random-pt4-move-halfmd4-to-lib.patch
random: Move halfmd4 to lib
random-pt4-kill-duplicate-halfmd4-in-ext3-htree.patch
random: Kill duplicate halfmd4 in ext3 htree
random-pt4-kill-duplicate-halfmd4-in-ext3-htree-fix.patch
random-pt4-kill-duplicate-halfmd4-in-ext3-htree-fix
random-pt4-simplify-and-shrink-syncookie-code.patch
random: Simplify and shrink syncookie code
random-pt4-move-syncookies-to-net.patch
random: Move syncookies to net/
speedup-proc-pid-maps.patch
Speed up /proc/pid/maps
speedup-proc-pid-maps-fix.patch
Speed up /proc/pid/maps fix
speedup-proc-pid-maps-fix-fix.patch
speedup-proc-pid-maps fix fix
speedup-proc-pid-maps-fix-fix-fix.patch
speedup /proc/<pid>/maps(4th version)
fix-loss-of-records-on-size-4096-in-proc-pid-maps.patch
fix loss of records on size > 4096 in proc/<pid>/maps
speedup-proc-pid-maps-fix-fix-fix-fix.patch
speedup-proc-pid-maps-fix-fix-fix fix
posix-timers-tidy-up-clock-interfaces-and-consolidate-dispatch-logic.patch
posix-timers: tidy up clock interfaces and consolidate dispatch logic
posix-timers-high-resolution-cpu-clocks-for-posix-clock_-syscalls.patch
posix-timers: high-resolution CPU clocks for POSIX clock_* syscalls
posix-timers-tidy-up-clock-interfaces-and-consolidate-dispatch-logic-cleanup.patch
posix-timers: tidy up clock interfaces and consolidate dispatch logic cleanup
posix-timers-fix-posix-timers-signals-lock-order.patch
posix-timers: fix posix-timers signals lock order
posix-timers-cpu-clock-support-for-posix-timers.patch
posix-timers: CPU clock support for POSIX timers
posix-timers-cpu-clock-support-for-posix-timers-fix.patch
posix-timers: CPU clock support for POSIX timers (fix)
panic-in-check_process_timers.patch
PANIC in check_process_timers()
make-itimer_real-per-process.patch
make ITIMER_REAL per-process
make-itimer_prof-itimer_virtual-per-process.patch
make ITIMER_PROF, ITIMER_VIRTUAL per-process
make-rlimit_cpu-sigxcpu-per-process.patch
make RLIMIT_CPU/SIGXCPU per-process
pcmcia-add-support-ti-pci4510-cardbus-bridge.patch
pcmcia: Add support TI PCI4510 CardBus bridge
pcmcia-update-vrc4171_card.patch
pcmcia: update vrc4171_card
nfs-fix_vfsflock.patch
VFS: Fix structure initialization in locks_remove_flock()
nfs-flock.patch
NFS: Add emulation of BSD flock() in terms of POSIX locks on the server
nfsacl-return-enosys-for-rpc-programs-that-are-unavailable.patch
nfsacl: return -ENOSYS for RPC programs that are unavailable
nfsacl-add-missing-eopnotsupp-=-nfs3err_notsupp-mapping-in-nfsd.patch
nfsacl: add missing -EOPNOTSUPP => NFS3ERR_NOTSUPP mapping in nfsd
nfsacl-allow-multiple-programs-to-listen-on-the-same-port.patch
nfsacl: allow multiple programs to listen on the same port
nfsacl-allow-multiple-programs-to-share-the-same-transport.patch
nfsacl: allow multiple programs to share the same transport
nfsacl-lazy-rpc-receive-buffer-allocation.patch
nfsacl: lazy RPC receive buffer allocation
nfsacl-encode-and-decode-arbitrary-xdr-arrays.patch
nfsacl: encode and decode arbitrary XDR arrays
nfsacl-encode-and-decode-arbitrary-xdr-arrays-fix.patch
nfsacl-encode-and-decode-arbitrary-xdr-arrays-fix
nfsacl-add-noacl-nfs-mount-option.patch
nfsacl: add noacl nfs mount option
nfsacl-infrastructure-and-server-side-of-nfsacl.patch
nfsacl: infrastructure and server side of nfsacl
nfsv4-deamon-always-supports-acls.patch
NFSv4 deamon always supports acls
lib-sort-replace-qsort-in-nfs-acl-code.patch
lib/sort: Replace qsort in NFS ACL code
nfsacl-infrastructure-and-server-side-of-nfsacl-fix.patch
nfsacl-infrastructure-and-server-side-of-nfsacl fix
nfsacl-solaris-nfsacl-workaround.patch
nfsacl: solaris nfsacl workaround
nfsacl-client-side-of-nfsacl.patch
nfsacl: client side of nfsacl
nfsacl-client-side-of-nfsacl-fix.patch
nfsacl: Must not initialize inode->i_op to NULL
nfsacl-acl-umask-handling-workaround-in-nfs-client.patch
nfsacl: aCL umask handling workaround in nfs client
nfsacl-acl-umask-handling-workaround-in-nfs-client-fix.patch
ACL umask handling workaround in nfs client fix
nfsacl-cache-acls-on-the-nfs-client-side.patch
nfsacl: cache acls on the nfs client side
nfs-acl-build-fix-posix-acl-config-tidy.patch
NFS ACL build fix, POSIX ACL config tidy
kgdb-ga.patch
kgdb stub for ia32 (George Anzinger's one)
kgdbL warning fix
kgdb buffer overflow fix
kgdbL warning fix
kgdb: CONFIG_DEBUG_INFO fix
x86_64 fixes
correct kgdb.txt Documentation link (against 2.6.1-rc1-mm2)
kgdb: fix for recent gcc
kgdb warning fixes
THREAD_SIZE fixes for kgdb
Fix stack overflow test for non-8k stacks
kgdb-ga.patch fix for i386 single-step into sysenter
fix TRAP_BAD_SYSCALL_EXITS on i386
add TRAP_BAD_SYSCALL_EXITS config for i386
kgdb-is-incompatible-with-kprobes
kgdb-ga-build-fix
kgdb-ga-fixes
kgdb: kill off highmem_start_page
kgdboe-netpoll.patch
kgdb-over-ethernet via netpoll
kgdboe: fix configuration of MAC address
kgdb-x86_64-support.patch
kgdb-x86_64-support.patch for 2.6.2-rc1-mm3
kgdb-x86_64-warning-fixes
kgdb-x86_64-fix
kgdb-x86_64-serial-fix
kprobes exception notifier fix
dev-mem-restriction-patch.patch
/dev/mem restriction patch
dev-mem-restriction-patch-allow-reads.patch
dev-mem-restriction-patch: allow reads
journal_add_journal_head-debug.patch
journal_add_journal_head-debug
list_del-debug.patch
list_del debug check
page-owner-tracking-leak-detector.patch
Page owner tracking leak detector
make-page_owner-handle-non-contiguous-page-ranges.patch
make page_owner handle non-contiguous page ranges
unplug-can-sleep.patch
unplug functions can sleep
firestream-warnings.patch
firestream warnings
perfctr-core.patch
perfctr: core
perfctr: remove bogus perfctr_sample_thread() calls
perfctr-i386.patch
perfctr: i386
perfctr-x86-core-updates.patch
perfctr x86 core updates
perfctr-x86-driver-updates.patch
perfctr x86 driver updates
perfctr-x86-driver-cleanup.patch
perfctr: x86 driver cleanup
perfctr-prescott-fix.patch
Prescott fix for perfctr
perfctr-x86-update-2.patch
perfctr x86 update 2
perfctr-x86_64.patch
perfctr: x86_64
perfctr-x86_64-core-updates.patch
perfctr x86_64 core updates
perfctr-ppc.patch
perfctr: PowerPC
perfctr-ppc32-driver-update.patch
perfctr: ppc32 driver update
perfctr-ppc32-mmcr0-handling-fixes.patch
perfctr ppc32 MMCR0 handling fixes
perfctr-ppc32-update.patch
perfctr ppc32 update
perfctr-ppc32-update-2.patch
perfctr ppc32 update
perfctr-virtualised-counters.patch
perfctr: virtualised counters
perfctr-remap_page_range-fix.patch
virtual-perfctr-illegal-sleep.patch
virtual perfctr illegal sleep
make-perfctr_virtual-default-in-kconfig-match-recommendation.patch
Make PERFCTR_VIRTUAL default in Kconfig match recommendation in help text
perfctr-ifdef-cleanup.patch
perfctr ifdef cleanup
perfctr-update-2-6-kconfig-related-updates.patch
perfctr: Kconfig-related updates
perfctr-virtual-updates.patch
perfctr virtual updates
perfctr-virtual-cleanup.patch
perfctr: virtual cleanup
perfctr-ppc32-preliminary-interrupt-support.patch
perfctr ppc32 preliminary interrupt support
perfctr-update-5-6-reduce-stack-usage.patch
perfctr: reduce stack usage
perfctr-interrupt-support-kconfig-fix.patch
perfctr interrupt_support Kconfig fix
perfctr-low-level-documentation.patch
perfctr low-level documentation
perfctr-inheritance-1-3-driver-updates.patch
perfctr inheritance: driver updates
perfctr-inheritance-2-3-kernel-updates.patch
perfctr inheritance: kernel updates
perfctr-inheritance-3-3-documentation-updates.patch
perfctr inheritance: documentation updates
perfctr-inheritance-locking-fix.patch
perfctr inheritance locking fix
perfctr-api-changes-first-step.patch
perfctr API changes: first step
perfctr-virtual-update.patch
perfctr virtual update
perfctr-x86-64-ia32-emulation-fix.patch
perfctr x86-64 ia32 emulation fix
perfctr-sysfs-update-1-4-core.patch
perfctr sysfs update: core
perfctr-sysfs-update.patch
Perfctr sysfs update
perfctr-sysfs-update-2-4-x86.patch
perfctr sysfs update: x86
perfctr-sysfs-update-3-4-x86-64.patch
perfctr sysfs update: x86-64
perfctr: syscall numbers in x86-64 ia32-emulation
perfctr x86_64 native syscall numbers fix
perfctr-sysfs-update-4-4-ppc32.patch
perfctr sysfs update: ppc32
add-do_proc_doulonglongvec_minmax-to-sysctl-functions.patch
Add do_proc_doulonglongvec_minmax to sysctl functions
add-do_proc_doulonglongvec_minmax-to-sysctl-functions-fix
add-do_proc_doulonglongvec_minmax-to-sysctl-functions fix 2
add-sysctl-interface-to-sched_domain-parameters.patch
Add sysctl interface to sched_domain parameters
allow-modular-ide-pnp.patch
allow modular ide-pnp
allow-x86_64-to-reenable-interrupts-on-contention.patch
Allow x86_64 to reenable interrupts on contention
i386-cpu-hotplug-updated-for-mm.patch
i386 CPU hotplug updated for -mm
ppc64-fix-cpu-hotplug.patch
ppc64: fix hotplug cpu
disable-atykb-warning.patch
disable atykb "too many keys pressed" warning
export-file_ra_state_init-again.patch
Export file_ra_state_init() again
cachefs-filesystem.patch
CacheFS filesystem
numa-policies-for-file-mappings-mpol_mf_move-cachefs.patch
numa-policies-for-file-mappings-mpol_mf_move for cachefs
cachefs-release-search-records-lest-they-return-to-haunt-us.patch
CacheFS: release search records lest they return to haunt us
fix-64-bit-problems-in-cachefs.patch
Fix 64-bit problems in cachefs
cachefs-fixed-typos-that-cause-wrong-pointer-to-be-kunmapped.patch
cachefs: fixed typos that cause wrong pointer to be kunmapped
cachefs-return-the-right-error-upon-invalid-mount.patch
CacheFS: return the right error upon invalid mount
fix-cachefs-barrier-handling-and-other-kernel-discrepancies.patch
Fix CacheFS barrier handling and other kernel discrepancies
remove-error-from-linux-cachefsh.patch
Remove #error from linux/cachefs.h
cachefs-warning-fix-2.patch
cachefs warning fix 2
cachefs-linkage-fix-2.patch
cachefs linkage fix
cachefs-build-fix.patch
cachefs build fix
cachefs-documentation.patch
CacheFS documentation
add-page-becoming-writable-notification.patch
Add page becoming writable notification
add-page-becoming-writable-notification-fix.patch
do_wp_page_mk_pte_writable() fix
add-page-becoming-writable-notification-build-fix.patch
add-page-becoming-writable-notification build fix
provide-a-filesystem-specific-syncable-page-bit.patch
Provide a filesystem-specific sync'able page bit
provide-a-filesystem-specific-syncable-page-bit-fix.patch
provide-a-filesystem-specific-syncable-page-bit-fix
provide-a-filesystem-specific-syncable-page-bit-fix-2.patch
provide-a-filesystem-specific-syncable-page-bit-fix-2
make-afs-use-cachefs.patch
Make AFS use CacheFS
afs-cachefs-dependency-fix.patch
afs-cachefs-dependency-fix
split-general-cache-manager-from-cachefs.patch
Split general cache manager from CacheFS
turn-cachefs-into-a-cache-backend.patch
Turn CacheFS into a cache backend
rework-the-cachefs-documentation-to-reflect-fs-cache-split.patch
Rework the CacheFS documentation to reflect FS-Cache split
update-afs-client-to-reflect-cachefs-split.patch
Update AFS client to reflect CacheFS split
x86-rename-apic_mode_exint.patch
kexec: x86: rename APIC_MODE_EXINT
x86-local-apic-fix.patch
kexec: x86: local apic fix
x86_64-e820-64bit.patch
kexec: x86_64: e820 64bit fix
x86-i8259-shutdown.patch
kexec: x86: i8259 shutdown: disable interrupts
x86_64-i8259-shutdown.patch
kexec: x86_64: add i8259 shutdown method
x86-apic-virtwire-on-shutdown.patch
kexec: x86: resture apic virtual wire mode on shutdown
x86_64-apic-virtwire-on-shutdown.patch
kexec: x86_64: restore apic virtual wire mode on shutdown
vmlinux-fix-physical-addrs.patch
kexec: vmlinux: fix physical addresses
x86-vmlinux-fix-physical-addrs.patch
kexec: x86: vmlinux: fix physical addresses
x86_64-vmlinux-fix-physical-addrs.patch
kexec: x86_64: vmlinux: fix physical addresses
x86_64-entry64.patch
kexec: x86_64: add 64-bit entry
x86-config-kernel-start.patch
kexec: x86: add CONFIG_PYSICAL_START
x86_64-config-kernel-start.patch
kexec: x86_64: add CONFIG_PHYSICAL_START
kexec-kexec-generic.patch
kexec: add kexec syscalls
kexec-kexec-generic-kexec-use-unsigned-bitfield.patch
kexec: use unsigned bitfield
x86-machine_shutdown.patch
kexec: x86: factor out apic shutdown code
x86-kexec.patch
kexec: x86 kexec core
x86-crashkernel.patch
crashdump: x86 crashkernel option
x86_64-machine_shutdown.patch
kexec: x86_64: factor out apic shutdown code
x86_64-kexec.patch
kexec: x86_64 kexec implementation
x86_64-crashkernel.patch
crashdump: x86_64: crashkernel option
kexec-ppc-support.patch
kexec: kexec ppc support
x86-crash_shutdown-nmi-shootdown.patch
crashdump: x86: add NMI handler to capture other CPUs
x86-crash_shutdown-snapshot-registers.patch
kexec: x86: snapshot registers during crash shutdown
x86-crash_shutdown-apic-shutdown.patch
kexec: x86 shutdown APICs during crash_shutdown
crashdump-documentation.patch
crashdump: documentation
crashdump-memory-preserving-reboot-using-kexec.patch
crashdump: memory preserving reboot using kexec
crashdump-routines-for-copying-dump-pages.patch
crashdump: routines for copying dump pages
crashdump-routines-for-copying-dump-pages-fixes.patch
crashdump-routines-for-copying-dump-pages-fixes
crashdump-elf-format-dump-file-access.patch
crashdump: elf format dump file access
crashdump-linear-raw-format-dump-file-access.patch
crashdump: linear raw format dump file access
crashdump-linear-raw-format-dump-file-access-coding-style.patch
crashdump-linear-raw-format-dump-file-access-coding-style
new-bitmap-list-format-for-cpusets.patch
new bitmap list format (for cpusets)
cpusets-big-numa-cpu-and-memory-placement.patch
cpusets - big numa cpu and memory placement
cpusets-config_cpusets-depends-on-smp.patch
Cpusets: CONFIG_CPUSETS depends on SMP
cpusets-move-cpusets-above-embedded.patch
move CPUSETS above EMBEDDED
cpusets-fix-cpuset_get_dentry.patch
cpusets : fix cpuset_get_dentry()
cpusets-fix-race-in-cpuset_add_file.patch
cpusets: fix race in cpuset_add_file()
cpusets-remove-more-casts.patch
cpusets: remove more casts
cpusets-make-config_cpusets-the-default-in-sn2_defconfig.patch
cpusets: make CONFIG_CPUSETS the default in sn2_defconfig
cpusets-document-proc-status-allowed-fields.patch
cpusets: document proc status allowed fields
cpusets-dont-export-proc_cpuset_operations.patch
Cpusets - Dont export proc_cpuset_operations
cpusets-display-allowed-masks-in-proc-status.patch
cpusets: display allowed masks in proc status
cpusets-simplify-cpus_allowed-setting-in-attach.patch
cpusets: simplify cpus_allowed setting in attach
cpusets-remove-useless-validation-check.patch
cpusets: remove useless validation check
cpusets-tasks-file-simplify-format-fixes.patch
Cpusets tasks file: simplify format, fixes
lib-sort-replace-open-coded-opids2-bubblesort-in-cpusets.patch
lib/sort: Replace open-coded O(pids**2) bubblesort in cpusets
cpusets-simplify-memory-generation.patch
Cpusets: simplify memory generation
cpusets-interoperate-with-hotplug-online-maps.patch
cpusets: interoperate with hotplug online maps
cpusets-alternative-fix-for-possible-race-in.patch
cpusets: alternative fix for possible race in cpuset_tasks_read()
cpusets-remove-casts.patch
cpusets: remove void* typecasts
reiser4-sb_sync_inodes.patch
reiser4: vfs: add super_operations.sync_inodes()
reiser4-allow-drop_inode-implementation.patch
reiser4: export vfs inode.c symbols
reiser4-truncate_inode_pages_range.patch
reiser4: vfs: add truncate_inode_pages_range()
reiser4-export-remove_from_page_cache.patch
reiser4: export pagecache add/remove functions to modules
reiser4-export-page_cache_readahead.patch
reiser4: export page_cache_readahead to modules
reiser4-reget-page-mapping.patch
reiser4: vfs: re-check page->mapping after calling try_to_release_page()
reiser4-rcu-barrier.patch
reiser4: add rcu_barrier() synchronization point
reiser4-export-inode_lock.patch
reiser4: export inode_lock to modules
reiser4-export-pagevec-funcs.patch
reiser4: export pagevec functions to modules
reiser4-export-radix_tree_preload.patch
reiser4: export radix_tree_preload() to modules
reiser4-export-find_get_pages.patch
reiser4-radix-tree-tag.patch
reiser4: add new radix tree tag
reiser4-radix_tree_lookup_slot.patch
reiser4: add radix_tree_lookup_slot()
reiser4-perthread-pages.patch
reiser4: per-thread page pools
reiser4-include-reiser4.patch
reiser4: add to build system
reiser4-doc.patch
reiser4: documentation
reiser4-only.patch
reiser4: main fs
reiser4-recover-read-performance.patch
reiser4: recover read performance
reiser4-export-find_get_pages_tag.patch
reiser4-export-find_get_pages_tag
reiser4-add-missing-context.patch
add-acpi-based-floppy-controller-enumeration.patch
Add ACPI-based floppy controller enumeration.
possible-dcache-bug-debugging-patch.patch
Possible dcache BUG: debugging patch
serial-add-support-for-non-standard-xtals-to-16c950-driver.patch
serial: add support for non-standard XTALs to 16c950 driver
add-support-for-possio-gcc-aka-pcmcia-siemens-mc45.patch
Add support for Possio GCC AKA PCMCIA Siemens MC45
generic-serial-cli-conversion.patch
generic-serial cli() conversion
specialix-io8-cli-conversion.patch
Specialix/IO8 cli() conversion
sx-cli-conversion.patch
SX cli() conversion
revert-allow-oem-written-modules-to-make-calls-to-ia64-oem-sal-functions.patch
revert "allow OEM written modules to make calls to ia64 OEM SAL functions"
md-add-interface-for-userspace-monitoring-of-events.patch
md: add interface for userspace monitoring of events.
make-acpi_bus_register_driver-consistent-with-pci_register_driver-again.patch
make acpi_bus_register_driver() consistent with pci_register_driver()
remove-lock_section-from-x86_64-spin_lock-asm.patch
remove LOCK_SECTION from x86_64 spin_lock asm
kfree_skb-dump_stack.patch
kfree_skb-dump_stack
cancel_rearming_delayed_work.patch
cancel_rearming_delayed_work()
ipvs-deadlock-fix.patch
ipvs deadlock fix
minimal-ide-disk-updates.patch
Minimal ide-disk updates
use-find_trylock_page-in-free_swap_and_cache-instead-of-hand-coding.patch
use find_trylock_page in free_swap_and_cache instead of hand coding
radeonfb-fix-spurious-error-return-in-fbio_radeon_set_mirror.patch
radeonfb: Fix spurious error return in FBIO_RADEON_SET_MIRROR
w100fb-make-blanking-function-interrupt-safe.patch
w100fb: Make blanking function interrupt safe
kyrofb-copy__user-return-value-checks-added-to-kyro-fb.patch
kyrofb: copy_*_user return value checks added to kyro fb
skeletonfb-documentation-fixes.patch
skeletonfb: Documentation fixes
intelfb-add-partial-support-915g-chipset.patch
intelfb: Add partial support 915G chipset
sisfb_compat_ioctl-warning-fix.patch
fbdev compat_ioctl warning fix
sis-warning-fix.patch
sis warning fix
tridentfbc-make-some-code-static.patch
tridentfb.c: make some code static
tridentfb-warning-fix.patch
tridentfb warning fix
md-fix-multipath-assembly-bug.patch
md: fix multipath assembly bug
md-raid-kconfig-cleanups-remove-experimental-tag-from-raid-6.patch
md: RAID Kconfig cleanups, remove experimental tag from RAID-6
device-mapper-store-name-directly-against-device.patch
device-mapper: Store name directly against device
device-mapper-record-restore-bio-state.patch
device-mapper: Record & restore bio state.
device-mapper-export-map_info.patch
device-mapper: Export map_info
figure-out-who-is-inserting-bogus-modules.patch
Figure out who is inserting bogus modules
detect-atomic-counter-underflows.patch
detect atomic counter underflows
update-documentation-filesystems-locking.patch
Update Documentation/filesystems/Locking
post-halloween-doc.patch
post halloween doc
periodically-scan-redzone-entries-and-slab-control-structures.patch
periodically scan redzone entries and slab control structures
fuse-maintainers-kconfig-and-makefile-changes.patch
Subject: [PATCH 1/11] FUSE - MAINTAINERS, Kconfig and Makefile changes
fuse-core.patch
Subject: [PATCH 2/11] FUSE - core
fuse-device-functions.patch
Subject: [PATCH 3/11] FUSE - device functions
fuse-device-functions-fix-race-in-interrupted-request.patch
fuse: fix race in interrupted request
fuse-device-functions-fix.patch
fuse: better error reporting in fuse_fill_super
fuse-fix-llseek-on-device.patch
FUSE: fix llseek on device
fuse-make-two-functions-static.patch
fuse: make two functions static
fuse-fix-variable-with-confusing-name.patch
fuse: fix variable with confusing name
fuse-read-only-operations.patch
Subject: [PATCH 4/11] FUSE - read-only operations
fuse-read-write-operations.patch
Subject: [PATCH 5/11] FUSE - read-write operations
fuse-read-write-operations-fix.patch
fuse: fix hard link operation
fuse-file-operations.patch
Subject: [PATCH 6/11] FUSE - file operations
fuse-mount-options.patch
Subject: [PATCH 7/11] FUSE - mount options
fuse-dont-check-against-zero-fsuid.patch
fuse: don't check against zero fsuid
fuse-remove-mount_max-and-user_allow_other-module-parameters.patch
fuse: remove mount_max and user_allow_other module parameters
fuse-extended-attribute-operations.patch
Subject: [PATCH 8/11] FUSE - extended attribute operations
fuse-readpages-operation.patch
Subject: [PATCH 9/11] FUSE - readpages operation
fuse-nfs-export.patch
Subject: [PATCH 10/11] FUSE - NFS export
fuse-direct-i-o.patch
Subject: [PATCH 11/11] FUSE - direct I/O
fuse-transfer-readdir-data-through-device.patch
fuse: transfer readdir data through device
cryptoapi-prepare-for-processing-multiple-buffers-at.patch
CryptoAPI: prepare for processing multiple buffers at a time
cryptoapi-update-padlock-to-process-multiple-blocks-at.patch
CryptoAPI: Update PadLock to process multiple blocks at once
update-email-address-of-andrea-arcangeli.patch
update email address of Andrea Arcangeli
compile-error-blackbird_load_firmware.patch
blackbird_load_firmware compile fix
i386-x86_64-apicc-make-two-functions-static.patch
i386/x86_64 apic.c: make two functions static
i386-cyrixc-make-a-function-static.patch
i386 cyrix.c: make a function static
mtrr-some-cleanups.patch
mtrr: some cleanups
i386-cpu-commonc-some-cleanups.patch
i386 cpu/common.c: some cleanups
i386-cpuidc-make-two-functions-static.patch
i386 cpuid.c: make two functions static
i386-efic-make-some-code-static.patch
i386 efi.c: make some code static
i386-x86_64-io_apicc-misc-cleanups.patch
i386/x86_64 io_apic.c: misc cleanups
i386-mpparsec-make-mp_processor_info-static.patch
i386 mpparse.c: make MP_processor_info static
i386-x86_64-msrc-make-two-functions-static.patch
i386/x86_64 msr.c: make two functions static
3w-abcdh-tw_device_extension-remove-an-unused-filed.patch
3w-abcd.h: TW_Device_Extension: remove an unused field
hpet-make-some-code-static.patch
hpet: make some code static
26-patch-i386-trapsc-make-a-function-static.patch
i386 traps.c: make a function static
i386-semaphorec-make-4-functions-static.patch
i386 semaphore.c: make 4 functions static
kill-aux_device_present.patch
kill aux_device_present
i386-setupc-make-4-variables-static.patch
i386 setup.c: make 4 variables static
mostly-i386-mm-cleanup.patch
(mostly i386) mm cleanup
update-email-address-of-benjamin-lahaise.patch
Update email address of Benjamin LaHaise
update-email-address-of-philip-blundell.patch
Update email address of Philip Blundell
kernel-acctc-make-a-function-static.patch
kernel/acct.c: make a function static
kernel-auditc-make-some-functions-static.patch
kernel/audit.c: make some functions static
kernel-capabilityc-make-a-spinlock-static.patch
kernel/capability.c: make a spinlock static
mm-thrashc-make-a-variable-static.patch
mm/thrash.c: make a variable static
lib-kernel_lockc-make-kernel_sem-static.patch
lib/kernel_lock.c: make kernel_sem static
saa7146_vv_ksymsc-remove-two-unused-export_symbol_gpls.patch
saa7146_vv_ksyms.c: remove two unused EXPORT_SYMBOL_GPL's
fix-placement-of-static-inline-in-nfsdh.patch
fix placement of static inline in nfsd.h
drivers-block-umemc-make-two-functions-static.patch
drivers/block/umem.c: make two functions static
drivers-block-xdc-make-a-variable-static.patch
drivers/block/xd.c: make a variable static
kernel-forkc-make-mm_cachep-static.patch
kernel/fork.c: make mm_cachep static
kernel-forkc-make-mm_cachep-static-fix.patch
kernel-forkc-make-mm_cachep-static fix
mm-page-writebackc-remove-an-unused-function.patch
mm/page-writeback.c: remove an unused function
mm-shmemc-make-a-struct-static.patch
mm/shmem.c: make a struct static
misc-isapnp-cleanups.patch
misc ISAPNP cleanups
some-pnp-cleanups.patch
some PNP cleanups
if-0-cx88_risc_disasm.patch
#if 0 cx88_risc_disasm
make-loglevels-in-init-mainc-a-little-more-sane.patch
Make loglevels in init/main.c a little more sane.
isicom-use-null-for-pointer.patch
sparse: use NULL for pointer
remove-bouncing-email-address-of-hennus-bergman.patch
remove bouncing email address of Hennus Bergman
cirrusfbc-make-some-code-static.patch
cirrusfb.c: make some code static
matroxfb_basec-make-some-code-static.patch
matroxfb_base.c: make some code static
matroxfb_basec-make-some-code-static-fix.patch
matroxfb_basec-make-some-code-static fix
asiliantfbc-make-some-code-static.patch
asiliantfb.c: make some code static
i386-apic-kconfig-cleanups.patch
i386 APIC Kconfig cleanups
security-seclvlc-make-some-code-static.patch
security/seclvl.c: make some code static
drivers-block-elevatorc-make-two-functions-static.patch
drivers/block/elevator.c: make two functions static
drivers-block-rdc-make-two-variables-static.patch
drivers/block/rd.c: make two variables static
loopc-make-two-functions-static.patch
loop.c: make two functions static
remove-bouncing-email-address-of-thomas-hood.patch
remove bouncing email address of Thomas Hood
fs-adfs-dir_fc-remove-an-unused-function.patch
fs/adfs/dir_f.c: remove an unused function
drivers-char-moxac-if-0-an-unused-function.patch
drivers/char/moxa.c: #if 0 an unused function
fs-lockd-clntprocc-make-2-functions-static.patch
fs/lockd/clntproc.c: make 2 functions static
oss-sb_cardc-no-need-to-include-mcah.patch
OSS sb_card.c: no need to include mca.h
ioschedc-use-proper-documentation-path.patch
*-iosched.c: Use proper documentation path
kernel-resourcec-make-resource_op-static.patch
kernel/resource.c: make resource_op static
kernel-power-mainc-make-pm_states-static.patch
kernel/power/main.c: make pm_states static
kernel-sysc-make-some-code-static.patch
kernel/sys.c: make some code static
scsi-ipsc-make-some-code-static.patch
SCSI ips.c: make some code static
scsi-psi240ic-make-4-functions-static.patch
SCSI psi240i.c: make 4 functions static
scsi-src-make-a-struct-static.patch
SCSI sr.c: make a struct static
small-drivers-video-kyro-cleanups.patch
small drivers/video/kyro/ cleanups
drivers-video-i810-make-some-code-static.patch
drivers/video/i810/: make some code static
floppyc-make-some-code-static.patch
floppy.c: make some code static
drivers-block-nbdc-make-3-functions-static.patch
drivers/block/nbd.c: make 3 functions static
drivers-block-cpqarrayc-small-cleanups.patch
drivers/block/cpqarray.c: small cleanups
pcxx-remove-obsolete-driver.patch
pcxx: Remove obsolete driver
pty-oops-fix.patch
pty oops fix
mark-the-mcd-cdrom-driver-as-broken.patch
mark the mcd cdrom driver as BROKEN
warning-fix-in-drivers-cdrom-mcdc.patch
warning fix in drivers/cdrom/mcd.c
wavefront-reduce-stack-usage.patch
wavefront: reduce stack usage
mm-page-writebackc-remove-an-unused-function-2.patch
mm/page-writeback.c: remove an unused function #2
generic_serialh-kill-incorrect-gs_debug-reference.patch
generic_serial.h: kill incorrect gs_debug reference
kernel-timerc-make-two-variables-static.patch
kernel/timer.c: make two variables static
remove-the-unused-oss-maestro_tablesh.patch
remove the unused OSS maestro_tables.h
fs-hfs-misc-cleanups.patch
fs/hfs/: misc cleanups
fs-hpfs-make-some-code-static.patch
fs/hpfs/: make some code static
fs-hfsplus-misc-cleanups.patch
fs/hfsplus/: misc cleanups
i386-x86_64-processc-make-hlt_counter-static.patch
i386/x86_64 process.c: make hlt_counter static
i386-mach-default-topologyc-make-cpu_devices-static.patch
i386/mach-default/topology.c: make cpu_devices static
i386-math-emu-misc-cleanups.patch
i386/math-emu/: misc cleanups
non-pc-parport-config-change.patch
non-PC parport config change
prism54-misc-cleanups.patch
prism54: misc cleanups
scsi-qlogicfcc-some-cleanups.patch
SCSI qlogicfc.c: some cleanups
scsi-qlogicispc-some-cleanups.patch
SCSI qlogicisp.c: some cleanups
savagefbc-make-some-code-static.patch
savagefb.c: make some code static
hpet-setup-comment-fix.patch
hpet setup comment fix
fs-ncpfs-ncplib_kernelc-make-a-function-static.patch
fs/ncpfs/ncplib_kernel.c: make a function static
kill-iphase5526.patch
kill IPHASE5526
fs-nfs-make-some-code-static.patch
fs/nfs/: make some code static
i386-x86_64-acpi-sleepc-kill-unused-acpi_save_state_disk.patch
i386/x86_64: acpi/sleep.c: kill unused acpi_save_state_disk
smpbootc-cleanups.patch
smp{,boot}.c cleanups
i386-kernel-i387c-misc-cleanups.patch
i386/kernel/i387.c: misc cleanups
i386-x86_64-i8259c-make-mask_and_ack_8259a-static.patch
i386/x86_64 i8259.c: make mask_and_ack_8259A static
scsi-sym53c416c-make-a-function-static.patch
SCSI sym53c416.c: make a function static
scsi-ultrastorc-make-a-variable-static.patch
SCSI ultrastor.c: make a variable static
kernel-intermodulec-make-inter_module_get-static.patch
kernel/intermodule.c: make inter_module_get static
^ permalink raw reply [flat|nested] 45+ messages in thread
end of thread, other threads:[~2005-02-14 13:27 UTC | newest]
Thread overview: 45+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2005-02-10 20:51 2.6.11-rc3-mm2 Jack O'Quin
2005-02-11 0:04 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 0:47 ` 2.6.11-rc3-mm2 Chris Wright
2005-02-11 2:09 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 2:22 ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11 3:26 ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11 3:41 ` 2.6.11-rc3-mm2 Paul Davis
2005-02-11 5:04 ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11 6:34 ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11 6:42 ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11 5:09 ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11 6:57 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 7:54 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 8:25 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 8:48 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 8:58 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 9:01 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 9:04 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 9:27 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:49 ` 2.6.11-rc3-mm2 Paul Davis
2005-02-11 19:42 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 19:57 ` 2.6.11-rc3-mm2 Lee Revell
2005-02-11 8:14 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 8:22 ` 2.6.11-rc3-mm2 Christoph Hellwig
2005-02-11 8:41 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 8:59 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 9:40 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 9:53 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 17:37 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:49 ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 20:10 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:45 ` 2.6.11-rc3-mm2 Paul Davis
2005-02-14 5:21 ` 2.6.11-rc3-mm2 Werner Almesberger
-- strict thread matches above, loose matches on Subject: below --
2005-02-10 10:35 2.6.11-rc3-mm2 Andrew Morton
2005-02-10 13:35 ` 2.6.11-rc3-mm2 Christoph Hellwig
2005-02-10 20:01 ` 2.6.11-rc3-mm2 Andrew Morton
2005-02-12 22:43 ` 2.6.11-rc3-mm2 Olaf Dietsche
2005-02-10 22:13 ` 2.6.11-rc3-mm2 Corey Minyard
2005-02-10 22:42 ` 2.6.11-rc3-mm2 Benjamin Herrenschmidt
2005-02-10 23:02 ` 2.6.11-rc3-mm2 Andrew Morton
2005-02-10 23:31 ` 2.6.11-rc3-mm2 Benjamin Herrenschmidt
2005-02-10 23:17 ` 2.6.11-rc3-mm2 Adrian Bunk
2005-02-11 16:29 ` 2.6.11-rc3-mm2 Yuval Tanny
2005-02-12 14:53 ` 2.6.11-rc3-mm2 Henning Rohde
2005-02-14 13:22 ` 2.6.11-rc3-mm2 Stefano Rivoir
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).