o kernel/ksyms.c: set_cpus_schedule was EXPORT_SYMBOL_GPL, bring it back
Originally, before this set of patches moving stuff out from kernel/ksyms.c,
set_cpus_schedule was EXPORT_SYMBOL_GPL, my mistake, bring it back.
Also follow Andrew Morton's suggestions of moving the EXPORT_SYMBOL{_GPL) even
closer to the place where the symbol exported is defined, i.e. just after the
symbol definition, this makes mistakes more difficult to happen, as when the
symbol definition is #ifdefed the EXPORT_SYMBOL{_GPL} is in the same block.
Rik van Riel [Wed, 1 Oct 2003 03:43:42 +0000 (20:43 -0700)]
[PATCH] syscall number for vserver
Vserver is a patch that implements BSD jail style virtual host semantics
inside Linux, where every process not only runs in its own namespace (it
reuses the chroot code for that, should switch to CLONE_NEWNS for 2.6),
but also its own hostname and IP address as well as its own view of
/proc.
Because of that added functionality, it needs more than what is
available in the LSM framework (which can only allow/deny permissions,
not alter return values).
The source code has been running stable for the last few years and is in
use at quite a few service providers. The Fedora project also wants to
use vserver for their build system. However, vserver for 2.4 just tacks
their syscalls onto the end of the syscall table and the userland tools
find those "dynamic numbers" somehow ... EWWWW.
For 2.6 I'd like to do things right. At the moment the vserver patch
has sys_new_s_context and sys_set_ipv4root calls, but since we'll
probably end up getting an ipv6 call too and people are planning future
functionality, I guess it would be more appropriate to multiplex these
through one sys_vserver patch, in the same way sys_ipc works.
For your reference, you can find more information about
vserver on these pages:
I estimate the project has about a dozen developers now. We are
planning on making the implementation for 2.6 fairly lightweight,
reusing infrastructure from other code where possible and only doing
things through sys_vserver where there is no other way.
This small change just adds sys_vserver to the syscall table.
Alexander Viro [Wed, 1 Oct 2003 03:42:10 +0000 (20:42 -0700)]
[PATCH] EFS set_blocksize() error handling
There doesn't seem to be any active maintainer for EFS: It's either
abandoned, or never required specific patches too badly (also quite
possible in this case).
It went into the tree in 2.3.2 and from there to 2.6.0-test6 I see
nothing that would look like maintainer's update. OTOH, it's read-only
and shouldn't be too badly broken (or hard to keep alive).
Outside of trunk (i.e. in 2.4.16--) we have a backport of global 2.5
change (sb_bread()) and check for set_blocksize() failures (from Alan).
This is the 2.6.x equivalent.
Matthew Wilcox [Tue, 30 Sep 2003 15:06:44 +0000 (08:06 -0700)]
[PATCH] PA-RISC updates
PA-RISC updates for 2.6.0-test6
- Some more support for 64-bit userspace
- Move many EXPORT_SYMBOLs out of parisc_ksyms.c
- Make both the OSS and ALSA harmony drivers build
- ioctl typechecking
- Make math-emu build without warnings.
- Persuade SuckyIO to not crash the machine.
It might not have prevented me from reporting the potential bug, but I
would've known you'd thought about it, it might help future developers,
and it's unlikely to become dangerously wrong.
Found and fixed a longstanding problem with the late execution of
the various deferred AML opcodes (such as Operation Regions,
Buffer Fields, Buffers, and Packages)...
This fixes the "region size computed incorrectly" problem.
Fixed several 64-bit issues with prototypes, casting and data types.
The patch below adds the ebt_limit match, which is the equivalent of
the iptables limit match. This enables limiting the number of frames
processed per time unit.
The patch is from Tom Marshall <tommy_at_home.tig-grr.com>.
Pete Zaitcev [Mon, 29 Sep 2003 17:23:23 +0000 (10:23 -0700)]
[SPARC]: jsflash update
Parts of this come from a janitor named Domen, unfortunately,
I forgot his e-mail... Anyhow, it's obvious that janitors
did not try to compile result of their efforts, this version
at least builds.
- common umc8672_init() for built-in and module
- release hwif only if hwif->chipset == ide_umc8672
- mark exit functions with __exit
- do not use ide_hwifs[] directly
- minor cleanups
- common qd65xx_init() for built-in and module
- release hwif only if hwif->chipset == ide_qd65xx
- mark exit functions with __exit
- do not use ide_hwifs[] directly
- minor cleanups
- common ht6560b_init() for built-in and module
- release hwif only if hwif->chipset == ide_ht6560b
- when releasing hwif, restore hwif->channel to the default value
- mark exit functions with __exit
- do not use ide_hwifs[] directly
- minor cleanups
- common dtc2278_init() for built-in and module
- touch hwifs only if hwif->chipset == ide_unknown for both ports,
so we don't thrash already used hwifs when loading module
- release hwif only if hwif->chipset == ide_dtc2278
- mark exit functions with __exit
- do not use ide_hwifs[] directly
- minor cleanups
- common ali14xx_init() for built-in and module
- do not call findPort() twice
- touch hwifs only if chipset was found and initialized
- release hwif only if hwif->chipset == ide_ali14xx
- when releasing hwif, restore hwif->channel to the default value
- mark exit functions with __exit
- do not use ide_hwifs[] directly
- minor cleanups
projects / linux / log