2.6.11-rc4-mm1
Andrew Morton
ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
- Various fixes and updates all over the place. Things seem to have slowed
down a bit.
- Last, final, ultimate call: if anyone has patches in here which are 2.6.11
material, please tell me.
Changes since 2.6.11-rc3-mm1:
linus.patch
bk-acpi.patch
bk-agpgart.patch
bk-alsa.patch
bk-cifs.patch
bk-cpufreq.patch
bk-driver-core.patch
bk-driver-core-infiniband-build-fix.patch
bk-drm-via.patch
bk-i2c.patch
bk-ide-dev.patch
bk-ieee1394.patch
bk-input.patch
bk-dtor-input.patch
bk-jfs.patch
bk-kbuild.patch
bk-kconfig.patch
bk-libata.patch
bk-netdev.patch
bk-ntfs.patch
bk-pci.patch
bk-scsi.patch
bk-serial.patch
bk-usb.patch
bk-watchdog.patch
Latest versions of external bk trees
-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
-add-try_acquire_console_sem.patch
-update-aty128fb-sleep-wakeup-code-for-new-powermac-changes.patch
-radeonfb-update.patch
-radeonfb-build-fix.patch
-fix-32-bit-calls-to-snd_pcm_channel_info.patch
-update-to-ipmi-driver-to-support-old-dmi-spec.patch
-serio-warning-fix.patch
-fix-small-vmalloc-per-allocation-limit.patch
-net-s2io-replace-schedule_timeout-with-msleep.patch
-nls_cp936c-is-not-synchronized-with-ms-translation-table.patch
-add-local-bio-pool-support-and-modify-dm.patch
-add-local-bio-pool-support-and-modify-dm-uninline-zero_fill_bio.patch
-floppy-add-sysfs-symlink.patch
-pcmcia-add-support-ti-pci4510-cardbus-bridge.patch
-mark-the-mcd-cdrom-driver-as-broken.patch
-tridentfbc-make-some-code-static.patch
Merged
+ppc64-fix-compilation-for-maple-board.patch
ppc64 build fix
+alps-do-not-activate-on-unsupported-models.patch
Input driver safety.
+device-mapper-dm-raid1-deadlock-fix.patch
dm deadlock fix
+fix-ip_rt_gc_min_interval_ms-procfs-sysctl.patch
Fix a networking sysctl
+ppc32-64-bit-resource-fix.patch
pcp32 build fix (for bk-pci.patch)
+nfsd-discard-cache_hashed-flag-keeping-information-in-refcount-instead.patch
nfsd fix
+panasonic-acpi-driver.patch
+pcc_acpi-build-fix.patch
+new-sony_acpi-driver.patch
+acpi-fix-a-if-statement-in-setup_sys_fs_device_files.patch
+fix-help-for-acpi_container.patch
Various ACPI fixes and enhancements
+tpm-build-fix.patch
+bk-driver-core-infiniband-build-fix.patch
Fix bk-driver-core.patch build bugs
+fix-for-the-ipmi-smb-driver.patch
+ipmi-documentation-updates.patch
IPMI driver fixes
+ide-fix-masked_irq-arg-handling-for-ide_do_request.patch
Old patch to fix an IDE DMA problem
+ppc-cpufreq-kconfig-fix.patch
Fix a bk-kbuild ppc32 problem.
+sis900-oops-fix.patch
Fix oops in this net driver
+tone-down-pci=routeirq-message.patch
+pcmcia-bridge-resource-management-fix.patch
More fixes for bk-pci.patch
+add-scsi-changer-driver.patch
SCSI changer support
+scsi-ch-build-fix.patch
scsi build fix
+6300esb-watchdog-driver.patch
New watchdog driver
+stop-using-base-argument-in-__free_pages_bulk.patch
+stop-using-base-argument-in-__free_pages_bulk-tidy.patch
mm code cleanup
+mempool-protect-buffer-overflow-in-mempool_resize.patch
mempool fixes
+move-accounting-function-calls-out-of-critical-vm-code-pathspatch-fix.patch
Fix lockup in move-accounting-function-calls-out-of-critical-vm-code-pathspatch.patch
+ppc32-update-arch-ppc-configs-pmac_defconfig.patch
+ppc32-artesyn-katana-platform-update.patch
+ppc32-artesyn-katana-enet-update.patch
+ppc32-move-irq_descstatus-irq_level-bit-setup-to-xilinx_picc.patch
+ppc32-lindentify-ppc4xx-pic-driver.patch
+ppc32-ppc4xx-pic-ack-parent-uic-in-disable_irq.patch
+ppc32-report-chip-version-in-proc-cpuinfo-for-85xx-boards.patch
+ppc32-fix-formatting-of-cds-common-platform-file.patch
ppc32 stuff
+fix-iounmap-and-a-pageattr-memleak-x86-and-x86-64.patch
Fix x86/x86_64 low-level mm handling
+x86_64-dump-stack-in-early-exception.patch
Add a dump_stack() when x86_64 dies early in boot (this patch is old and
will be dropped).
+altix-ignore-input-during-early-boot.patch
+altix-ioc4-serial-driver-support.patch
ALtix updates
+m32r-use-generic-bugh.patch
m32r code consolidation
-fix-put_user-under-mmap_sem-in-sys_get_mempolicy.patch
This is done in fix-futex-mmap_sem-deadlock.patch now.
+serial-add-the-output-interface-control-to.patch
MIPS serial driver updates
+areca-raid-linux-scsi-driver-fix.patch
New RAID driver (this patch is having a hard life and needs a re-review)
+add-local-bio-pool-support-and-modify-dm.patch
+add-local-bio-pool-support-and-modify-dm-uninline-zero_fill_bio.patch
+add-local-bio-pool-support-and-modify-dm-use-global-bio-set-pool.patch
BIO enhancements for devicemapper
+fix-ufs-quota.patch
UFS quota fix
+run-softirqs-on-proper-processor-on-offline.patch
CPU hotplug fix
+aops-based-loop-io.patch
In the loop driver, fall back to using the file_operations if the right
address_space_operations aren't available.
+tty-output-lossage-fix.patch
Fix tty character droppage
+add-timing-information-to-printk-messages.patch
Option to timestamp printk output.
+seccomp.patch
+seccomp-tidy.patch
Andrea's secure computing thing
+minor-bttv-driver-update.patch
+tv-tuner-module-update.patch
bttv/TV updates
+remove-mount-option-parsing-from-procfs.patch
cleanup
+credits-update.patch
credits update
+bksend-example-script-fix.patch
Fix bk-send docco
+export-kallsyms_lookup_name.patch
Export a symbol for kprobes
+add-nobh_writepage-support.patch
+add-nobh_writepage-support-tidy.patch
+add-nobh_writepage-support-fix.patch
Add full writepage support for those filesystems which use the
no-buffer_head address_space_operations.
+fix-1-wire-dallas-in-bigendian-machines.patch
Fix the w1 driver for big-endian hardware.
+fix-futex-mmap_sem-deadlock.patch
Fix double-down_read in the futex and mempolicy code
+inotify.patch
Not sure if this is the latest version.
+posix-timers-cpu-clock-support-for-posix-timers-fix2.patch
Fix posix-timers-cpu-clock-support-for-posix-timers.patch again
+pcmcia-yenta_socket-ti4150-support.patch
+pcmcia-pd6729-convert-to-pci_register_driver.patch
+pcmcia-rsrc_nonstatic-sysfs-output.patch
+pcmcia-rsrc_nonstatic-sysfs-input.patch
+pcmcia-mark-resource-setup-as-done.patch
+pcmcia-pcmcia_device_probe.patch
+pcmcia-pcmcia_device_remove.patch
+pcmcia-pcmcia_device_add.patch
+pcmcia-use-bus_rescan_devices.patch
+pcmcia-add-pcmcia-devices-autonomously.patch
+pcmcia-determine-some-useful-information-about-devices.patch
+pcmcia-per-device-sysfs-output.patch
pcmcia updates
+nfsacl-encode-and-decode-arbitrary-xdr-arrays-fix2.patch
Fix nfsacl-encode-and-decode-arbitrary-xdr-arrays.patch even more. (I'll be
droping all the nfsacl patches when the new version comes through).
+nfsacl-return-enosys-for-rpc-programs-that-are-unavailable-fix.patch
Another nfsacl fix
+kgdb-documentation-fix.patch
Fix kgdb docco
+perfctr-2710-api-update-1-4-common.patch
+perfctr-2710-api-update-2-4-i386.patch
+perfctr-2710-api-update-3-4-x86_64.patch
+perfctr-2710-api-update-4-4-ppc32.patch
perfctr updates
+au1x00_uart-deadlock-fix.patch
Fix tty echo deadlock in this serial driver
-make-acpi_bus_register_driver-consistent-with-pci_register_driver-again.patch
I think I dropped this.
+tridentfbc-make-some-code-static.patch
+intelfb-vesa_modes-require-config_fb_modehelpers.patch
+fbdev-make-fb_find_mode-return-failure-if-modular.patch
+fbdev-logo-code-fixes.patch
+fbdev-kbuild-cleanups.patch
+geodefb-add-geode-framebuffer-driver.patch
+nvidiafb-add-update-framebuffer-driver-for-nvidia-chipsets.patch
+fbdev-generic-drawing-function-cleanups.patch
+fbdev-generic-drawing-function-cleanups-fix.patch
fbdev things
+md-remove-possible-oops-in-md-raid1.patch
+md-make-raid5-and-raid6-robust-against-failure-during-recovery.patch
+md-remove-kludgy-level-check-from-mdc.patch
+md-merge-md_enter_safemode-into-md_check_recovery.patch
+md-improve-locking-on-safemode-and-move-superblock-writes.patch
+md-improve-the-interface-to-sync_request.patch
+md-optimised-resync-using-bitmap-based-intent-logging.patch
+md-optimised-resync-using-bitmap-based-intent-logging-fix.patch
+md-raid1-support-for-bitmap-intent-logging.patch
+md-optimise-reconstruction-when-re-adding-a-recently-failed-drive.patch
RAID updates
+device-mapper-multipath.patch
+device-mapper-multipath-round-robin-path-selector.patch
+device-mapper-multipath-hardware-handler.patch
+device-mapper-multipath-hardware-handler-for-emc.patch
+device-mapper-tag-multipath-exports-gpl.patch
+device-mapper-some-code-formatting-cleanups.patch
+device-mapper-some-multipath-fn-renames.patch
More DM updates
+mxserc-remove-unused-variable.patch
+update-panic-comment.patch
+pm3fb-remove-kernel-22-code.patch
+sstfbc-make-some-code-static.patch
+scsi-53c700c-make-ncr_700_intr-static.patch
+scsi-dpt_i2oc-make-some-code-static.patch
+i386-io_apicc-make-two-variables-static.patch
+i386-x86_64-mpparsec-make-some-code-static.patch
+i386-quirksc-make-a-function-static.patch
+drivers-block-paride-cleanups.patch
+cfq-ioschedc-make-some-code-static.patch
+deadline-ioschedc-make-a-struct-static.patch
+remove-obsolete-linux-resourceh-inclusion-from-asm-generic-siginfoh.patch
Little code tweaks
+fix-pm_message_t-in-generic-code.patch
+fix-u32-vs-pm_message_t-in-usb.patch
+fix-u32-vs-pm_message_t-confusion-in-oss.patch
+fix-u32-vs-pm_message_t-confusion-in-pcmcia.patch
+fix-u32-vs-pm_message_t-confusion-in-firewire.patch
+fix-u32-vs-pm_message_t-in-network-device-drivers.patch
+fix-u32-vs-pm_message_t-confusion-in-framebuffers.patch
+fix-u32-vs-pm_message_t-confusion-in-mmc.patch
+fix-u32-vs-pm_message_t-confusion-in-serials.patch
+fix-u32-vs-pm_message_t-in-macintosh.patch
+fix-u32-vs-pm_message_t-confusion-in-agp.patch
The great pm_message_t conversion.
+fs-jffs-misc-cleanups.patch
+fs-jffs2-misc-cleanups.patch
+drivers-block-cciss-misc-cleanups.patch
+remove-unused-get_resource_list-declaration.patch
+typo-in-include-linux-compilerh.patch
More little fixes
number of patches in -mm: 701
number of changesets in external trees: 791
number of patches in -mm only: 677
total patches: 1468
All 701 patches:
linus.patch
ppc64-fix-compilation-for-maple-board.patch
ppc64: fix compilation for Maple board
alps-do-not-activate-on-unsupported-models.patch
ALPS: do not activate on unsupported models
device-mapper-dm-raid1-deadlock-fix.patch
device-mapper: dm-raid1 deadlock fix
fix-ip_rt_gc_min_interval_ms-procfs-sysctl.patch
ipv4: Fix ip_rt_gc_min_interval_ms procfs/sysctl
ppc32-64-bit-resource-fix.patch
ppc32: 64 bit resource 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
nfsd-discard-cache_hashed-flag-keeping-information-in-refcount-instead.patch
nfsd: discard CACHE_HASHED flag, keeping information in refcount instead.
ia64-config_apci_numa-fix.patch
ia64 CONFIG_APCI_NUMA fix
ia64-acpi-build-fix.patch
ia64 acpi build fix
bk-acpi.patch
panasonic-acpi-driver.patch
Panasonic ACPI driver
pcc_acpi-build-fix.patch
pcc_acpi 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
new-sony_acpi-driver.patch
new sony_acpi driver
acpi-fix-a-if-statement-in-setup_sys_fs_device_files.patch
acpi: fix a if-statement in setup_sys_fs_device_files()
bk-agpgart.patch
bk-alsa.patch
bk-cifs.patch
bk-cpufreq.patch
cpufreq-core-reduce-warning-messages.patch
cpufreq-core: reduce warning messages
bk-driver-core.patch
tpm-build-fix.patch
tpm-build-fix
bk-driver-core-infiniband-build-fix.patch
bk-driver-core infiniband build fix
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
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
fix-for-the-ipmi-smb-driver.patch
Fix for the IPMI SMB driver
ipmi-documentation-updates.patch
IPMI documentation updates
bk-ide-dev.patch
ide-fix-masked_irq-arg-handling-for-ide_do_request.patch
ide: Fix masked_irq arg handling for ide_do_request()
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
twidjoy-build-fix.patch
twidjoy-build-fix
bk-jfs.patch
bk-kbuild.patch
bk-kconfig.patch
ppc-cpufreq-kconfig-fix.patch
ppc32: cpufreq kconfig fix
bk-libata.patch
bk-netdev.patch
sis900-oops-fix.patch
sis900 kernel oops fix
bk-ntfs.patch
bk-pci.patch
tone-down-pci=routeirq-message.patch
tone down pci=routeirq message
pcmcia-bridge-resource-management-fix.patch
pcmcia bridge resource management fix
bk-scsi.patch
add-scsi-changer-driver.patch
add scsi changer driver
scsi-ch-build-fix.patch
scsi ch.c build fix
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
6300esb-watchdog-driver.patch
6300ESB watchdog driver
mm.patch
add -mmN to EXTRAVERSION
fix-help-for-acpi_container.patch
Fix help for ACPI_CONTAINER
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
stop-using-base-argument-in-__free_pages_bulk.patch
stop using "base" argument in __free_pages_bulk()
stop-using-base-argument-in-__free_pages_bulk-tidy.patch
stop-using-base-argument-in-__free_pages_bulk-tidy
mempool-protect-buffer-overflow-in-mempool_resize.patch
mempool: protect buffer overflow in mempool_resize
fix-mincore-cornercases-overflow-caused-by-large-len.patch
Fix mincore cornercases: overflow caused by large "len"
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
move-accounting-function-calls-out-of-critical-vm-code-pathspatch-fix.patch
move-accounting-function-calls-out-of-critical-vm-code-pathspatch fix
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
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
ppc32-update-arch-ppc-configs-pmac_defconfig.patch
ppc32: update arch/ppc/configs/pmac_defconfig
ppc32-artesyn-katana-platform-update.patch
ppc32: Artesyn Katana platform update
ppc32-artesyn-katana-enet-update.patch
ppc32: Artesyn Katana enet update
ppc32-move-irq_descstatus-irq_level-bit-setup-to-xilinx_picc.patch
ppc32: move irq_desc[].status, IRQ_LEVEL bit setup to xilinx_pic.c
ppc32-lindentify-ppc4xx-pic-driver.patch
ppc32: Lindentify PPC4xx PIC driver
ppc32-ppc4xx-pic-ack-parent-uic-in-disable_irq.patch
ppc32: PPC4xx PIC: ack parent UIC in disable_irq
ppc32-report-chip-version-in-proc-cpuinfo-for-85xx-boards.patch
ppc32: report chip version in /proc/cpuinfo for 85xx boards
ppc32-fix-formatting-of-cds-common-platform-file.patch
ppc32: fix formatting of CDS common platform file
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
fix-iounmap-and-a-pageattr-memleak-x86-and-x86-64.patch
fix iounmap and a pageattr memleak (x86 and x86-64)
x86_64-dump-stack-in-early-exception.patch
x86_64-dump-stack-in-early-exception
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
altix-ignore-input-during-early-boot.patch
Altix: Ignore input during early boot
altix-ioc4-serial-driver-support.patch
Altix: ioc4 serial driver support
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
m32r-use-generic-bugh.patch
m32r: use generic bug.h
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
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
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
serial-add-the-output-interface-control-to.patch
serial: add the output interface control to VR41xx SIU driver
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
areca-raid-linux-scsi-driver-fix.patch
areca-raid-linux-scsi-driver-fix
minor-conceptual-fix-for-proc-kcore-header-size.patch
minor conceptual fix for /proc/kcore header size
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
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
add-local-bio-pool-support-and-modify-dm-use-global-bio-set-pool.patch
add-local-bio-pool-support-and-modify-dm: use global bio set pool
fix-ufs-quota.patch
Implement quota reading and writing functions for UFS.
run-softirqs-on-proper-processor-on-offline.patch
Run softirqs on proper processor on offline
aops-based-loop-io.patch
a_ops-based loop I/O
tty-output-lossage-fix.patch
tty output lossage fix
add-timing-information-to-printk-messages.patch
add timing information to printk messages
seccomp.patch
seccomp: secure computing support
seccomp-tidy.patch
seccomp-tidy
minor-bttv-driver-update.patch
minor bttv driver update
tv-tuner-module-update.patch
tv tuner module update.
remove-mount-option-parsing-from-procfs.patch
remove mount option parsing from procfs
credits-update.patch
CREDITS Update
bksend-example-script-fix.patch
bksend example script fix
export-kallsyms_lookup_name.patch
export kallsyms_lookup_name()
add-nobh_writepage-support.patch
Add nobh_writepage() support
add-nobh_writepage-support-tidy.patch
add-nobh_writepage-support-tidy
add-nobh_writepage-support-fix.patch
add-nobh_writepage-support fix
fix-1-wire-dallas-in-bigendian-machines.patch
Fix 1-Wire Dallas in bigendian machines
fix-futex-mmap_sem-deadlock.patch
Fix futex mmap_sem deadlock
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
inotify.patch
inotify
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)
posix-timers-cpu-clock-support-for-posix-timers-fix2.patch
Fix lockup in sys_timer_settime
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-update-vrc4171_card.patch
pcmcia: update vrc4171_card
pcmcia-yenta_socket-ti4150-support.patch
pcmcia: yenta_socket - ti4150 support
pcmcia-pd6729-convert-to-pci_register_driver.patch
pcmcia: pd6729 - convert to pci_register_driver()
pcmcia-rsrc_nonstatic-sysfs-output.patch
pcmcia: rsrc_nonstatic: sysfs output
pcmcia-rsrc_nonstatic-sysfs-input.patch
pcmcia: rsrc_nonstatic: sysfs input
pcmcia-mark-resource-setup-as-done.patch
pcmcia: mark resource setup as done
pcmcia-pcmcia_device_probe.patch
pcmcia: pcmcia_device_probe
pcmcia-pcmcia_device_remove.patch
pcmcia: pcmcia_device_remove
pcmcia-pcmcia_device_add.patch
pcmcia: pcmcia_device_add
pcmcia-use-bus_rescan_devices.patch
pcmcia: use bus_rescan_devices
pcmcia-add-pcmcia-devices-autonomously.patch
pcmcia: add pcmcia devices autonomously
pcmcia-determine-some-useful-information-about-devices.patch
pcmcia: determine some useful information about devices
pcmcia-per-device-sysfs-output.patch
pcmcia: per-device sysfs output
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-encode-and-decode-arbitrary-xdr-arrays-fix2.patch
nfsacl-encode-and-decode-arbitrary-xdr-arrays-fix2
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
Include FS_POSIX_ACL if nfs server needs it
nfsacl-return-enosys-for-rpc-programs-that-are-unavailable-fix.patch
nfsacl-return-enosys-for-rpc-programs-that-are-unavailable fix
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
kgdb-documentation-fix.patch
kgdb documentation fix
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
periodically-scan-redzone-entries-and-slab-control-structures.patch
periodically scan redzone entries and slab control structures
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
perfctr-2710-api-update-1-4-common.patch
perfctr-2.7.10 API update 1/4: common
perfctr-2710-api-update-2-4-i386.patch
perfctr-2.7.10 API update 2/4: i386
perfctr-2710-api-update-3-4-x86_64.patch
perfctr-2.7.10 API update 3/4: x86_64
perfctr-2710-api-update-4-4-ppc32.patch
perfctr-2.7.10 API update 4/4: 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
au1x00_uart-deadlock-fix.patch
au1x00_uart deadlock fix
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.
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
intelfb-vesa_modes-require-config_fb_modehelpers.patch
intelfb: vesa_modes require CONFIG_FB_MODEHELPERS
fbdev-make-fb_find_mode-return-failure-if-modular.patch
fbdev: Make fb_find_mode() return failure if modular
fbdev-logo-code-fixes.patch
fbdev: Logo code fixes
fbdev-kbuild-cleanups.patch
fbdev: Kbuild cleanups
geodefb-add-geode-framebuffer-driver.patch
geodefb: Add Geode framebuffer driver
nvidiafb-add-update-framebuffer-driver-for-nvidia-chipsets.patch
nvidiafb: Add update framebuffer driver for nVidia chipsets
fbdev-generic-drawing-function-cleanups.patch
fbdev: Generic drawing function cleanups
fbdev-generic-drawing-function-cleanups-fix.patch
c~fbdev-generic-drawing-function-cleanups-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
md-remove-possible-oops-in-md-raid1.patch
md: remove possible oops in md/raid1
md-make-raid5-and-raid6-robust-against-failure-during-recovery.patch
md: make raid5 and raid6 robust against failure during recovery.
md-remove-kludgy-level-check-from-mdc.patch
md: remove kludgy level check from md.c
md-merge-md_enter_safemode-into-md_check_recovery.patch
md: merge md_enter_safemode into md_check_recovery
md-improve-locking-on-safemode-and-move-superblock-writes.patch
md: improve locking on 'safemode' and move superblock writes
md-improve-the-interface-to-sync_request.patch
md: improve the interface to sync_request
md-optimised-resync-using-bitmap-based-intent-logging.patch
md: optimised resync using Bitmap based intent logging
md-optimised-resync-using-bitmap-based-intent-logging-fix.patch
md-optimised-resync-using-bitmap-based-intent-logging fix
md-raid1-support-for-bitmap-intent-logging.patch
md: raid1 support for bitmap intent logging
md-optimise-reconstruction-when-re-adding-a-recently-failed-drive.patch
md: optimise reconstruction when re-adding a recently failed drive.
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
device-mapper-multipath.patch
device-mapper: multipath
device-mapper-multipath-round-robin-path-selector.patch
device-mapper: multipath round-robin path selector.
device-mapper-multipath-hardware-handler.patch
device-mapper: multipath hardware handler
device-mapper-multipath-hardware-handler-for-emc.patch
device-mapper: multipath hardware handler for EMC
device-mapper-tag-multipath-exports-gpl.patch
device-mapper: tag multipath exports GPL
device-mapper-some-code-formatting-cleanups.patch
device-mapper: Some code/formatting cleanups
device-mapper-some-multipath-fn-renames.patch
device-mapper: Some multipath fn renames
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
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
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
mxserc-remove-unused-variable.patch
mxser.c: remove unused variable
update-panic-comment.patch
Update panic() comment
pm3fb-remove-kernel-22-code.patch
pm3fb: remove kernel 2.2 code
sstfbc-make-some-code-static.patch
sstfb.c: make some code static
scsi-53c700c-make-ncr_700_intr-static.patch
SCSI 53c700.c: make NCR_700_intr static
scsi-dpt_i2oc-make-some-code-static.patch
SCSI: dpt_i2o.c: make some code static
i386-io_apicc-make-two-variables-static.patch
i386 io_apic.c: make two variables static
i386-x86_64-mpparsec-make-some-code-static.patch
i386/x86_64: mpparse.c: make some code static
i386-quirksc-make-a-function-static.patch
i386 quirks.c: make a function static
drivers-block-paride-cleanups.patch
drivers/block/paride/ cleanups (fwd)
cfq-ioschedc-make-some-code-static.patch
cfq-iosched.c: make some code static
deadline-ioschedc-make-a-struct-static.patch
deadline-iosched.c: make a struct static
remove-obsolete-linux-resourceh-inclusion-from-asm-generic-siginfoh.patch
remove obsolete linux/resource.h inclusion from asm-generic/siginfo.h
fix-pm_message_t-in-generic-code.patch
Fix pm_message_t in generic code
fix-u32-vs-pm_message_t-in-usb.patch
Fix u32 vs. pm_message_t in USB
fix-u32-vs-pm_message_t-confusion-in-oss.patch
Fix u32 vs. pm_message_t confusion in OSS
fix-u32-vs-pm_message_t-confusion-in-pcmcia.patch
Fix u32 vs. pm_message_t confusion in PCMCIA
fix-u32-vs-pm_message_t-confusion-in-firewire.patch
Fix u32 vs. pm_message_t confusion in firewire
fix-u32-vs-pm_message_t-in-network-device-drivers.patch
Fix u32 vs. pm_message_t in network device drivers
fix-u32-vs-pm_message_t-confusion-in-framebuffers.patch
Fix u32 vs. pm_message_t confusion in framebuffers
fix-u32-vs-pm_message_t-confusion-in-mmc.patch
Fix u32 vs. pm_message_t confusion in MMC
fix-u32-vs-pm_message_t-confusion-in-serials.patch
Fix u32 vs. pm_message_t confusion in serials
fix-u32-vs-pm_message_t-in-macintosh.patch
Fix u32 vs. pm_message_t in macintosh
fix-u32-vs-pm_message_t-confusion-in-agp.patch
Fix u32 vs. pm_message_t confusion in AGP
fs-jffs-misc-cleanups.patch
fs/jffs/: misc cleanups
fs-jffs2-misc-cleanups.patch
fs/jffs2/: misc cleanups
drivers-block-cciss-misc-cleanups.patch
drivers/block/cciss*: misc cleanups
remove-unused-get_resource_list-declaration.patch
Remove unused get_resource_list() declaration
typo-in-include-linux-compilerh.patch
typo in include/linux/compiler.h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Mathieu Segaud
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
>
>
> - Various fixes and updates all over the place. Things seem to have slowed
> down a bit.
>
> - Last, final, ultimate call: if anyone has patches in here which are 2.6.11
> material, please tell me.
>
>
>
> Changes since 2.6.11-rc3-mm1:
[snip]
> +inotify.patch
>
> Not sure if this is the latest version.
it is the latest Robert Love posted against -mm kernels, but in
inotify_ignore():
static int inotify_ignore(struct inotify_device *dev, s32 wd)
{
struct inotify_watch *watch;
int ret = 0;
spin_lock(&dev->lock);
watch = dev_find_wd(dev, wd);
spin_unlock(&dev->lock); <------------- lock is released, but
if (!watch) {
ret = -EINVAL;
goto out;
}
__remove_watch(watch, dev); <---------- must be called with lock held
out:
spin_unlock(&dev->lock); <------------- anyway, lock is
return ret; released and sub_preempt_count
} BUG's on SMP and PREEMPT
__remove_watch() must be called with ->lock held on dev.
Anyway, ->lock is released after label out.
Signed-off-by: Mathieu Segaud <ma...@minas-morgul.org>
Jesper Juhl
> - Last, final, ultimate call: if anyone has patches in here which are 2.6.11
> material, please tell me.
I guess that depends on how you define 2.6.11 material at this point, but
I have a few patches that I wrote in there, that I think are potential
candidates due to them being fairly trivial, obviously correct and not
having caused any problems since entering -mm. Those patches might as well
get merged into 2.6.11 now and get out of your queue/hair.
The patches I have in mind are these:
fix-placement-of-static-inline-in-nfsdh.patch
--
This one has no actual impact on the generated code, it just kills a few
warnings when building with gcc -W, so merging that up should be harmless.
kyrofb-copy__user-return-value-checks-added-to-kyro-fb.patch
--
This one just adds a few return value checks to copy_*_user calls and
returns -EFAULT when failing. I've seen no complains about the patch on
the list and it seems to be the obviously correct thing to do - might as
well get merged.
warning-fix-in-drivers-cdrom-mcdc.patch
--
Trivial, obviously correct, warning fix to an ancient driver. No point in
having you carry it around in -mm, let's just merge it.
make-loglevels-in-init-mainc-a-little-more-sane.patch
--
This one just changes a few loglevels, so the potential for breakage is
extremely low. Besides I believe I've argued the case for the new
loglevels being more sane than the old ones well enough, and noone has
complained about the patch.
The patches above are all very low risk, so they shouldn't cause any
problems for 2.6.11. Let us merge them now to a) get the bennefit of them
in 2.6.11 and b) get them out of your -mm queue.
nitpick note: despite some of these patches having From: lines in them in
your -mm patch set that list other people they where all written by me.
Other people getting listed as From: (and thus later as patch author in
the changelogs and bk) seems to happen when other people resend the
patches to the list or when they pass through maintainers before they
reach you. Just to set the record straight; I initially wrote the patches
above.
Kind regards,
Jesper Juhl <juhl...@dif.dk>
Helge Hafting
when trying to mount /var.
(I have two IDE disks on the same cable, and an IDE cdrom on another.)
They are usually hda, hdb, and hdc.
MAKEDEV hdq did not help. Looking at sysfs, it turns out that
/dev/hdq1 is at major:3 minor:1025 if I interpret things right.
(/dev/hda1 is at 3:1, which is correct.)
These numbers did not work with my mknod, it created 7:1 instead.
So I didn't get to test this mysterious device.
But I assume this is a mistake of some sort, I haven't heard about any
change in the IDE numbering coming up? 2.6.1-rc3-mm1 works as expected.
It may be interesting to note that my root raid-1 came up fine,
consisting of hdq1 and hda1 instead of the usual hdb1 and hda1.
Helge Hafting
Robert Love
> it is the latest Robert Love posted against -mm kernels, but in
> inotify_ignore():
I posted an updated patch last Friday, which fixed this.
Anyhow, this is the correct fix.
Signed-off-by: Robert Love <r...@novell.com>
Thanks,
Robert Love
Steven Cole
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
>
>
> - Various fixes and updates all over the place. Things seem to have slowed
> down a bit.
>
I am having trouble getting recent -mm kernels to boot on my test box.
For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
VFS: Cannot open root device "301" or unknown-block(3,1)
Please append a correct "root=" boot option
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
2.6.11-rc2-mm1 boots fine, and so do plain -rc3 and -rc4.
I copied a working .config from an earlier kernel(-rc3), and ran make oldconfig,
answering most of the new questions 'n'.
I did try appending root=0301 (which worked last year after similar symptoms,
but that didn't help this time).
The root fs is ext3, which is compiled in.
Any help appreciated.
Steven
Output of grep ^CONFIG .config:
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_BROKEN_ON_SMP=y
CONFIG_LOCALVERSION="-GX110"
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
CONFIG_BSD_PROCESS_ACCT=y
CONFIG_SYSCTL=y
CONFIG_EMBEDDED=y
CONFIG_BASE_SMALL=1
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_X86_PC=y
CONFIG_MPENTIUMIII=y
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
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=y
CONFIG_X86_UP_APIC=y
CONFIG_X86_UP_IOAPIC=y
CONFIG_X86_LOCAL_APIC=y
CONFIG_X86_IO_APIC=y
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_P4THERMAL=y
CONFIG_MICROCODE=y
CONFIG_X86_MSR=y
CONFIG_X86_CPUID=y
CONFIG_EDD=y
CONFIG_NOHIGHMEM=y
CONFIG_MTRR=y
CONFIG_PHYSICAL_START=0x100000
CONFIG_PCI=y
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_BINFMT_ELF=y
CONFIG_BINFMT_MISC=y
CONFIG_PREVENT_FIRMWARE_BUILD=y
CONFIG_BLK_DEV_FD=y
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_RAM=y
CONFIG_BLK_DEV_RAM_COUNT=16
CONFIG_BLK_DEV_RAM_SIZE=32000
CONFIG_BLK_DEV_INITRD=y
CONFIG_INITRAMFS_SOURCE=""
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
CONFIG_BLK_DEV_IDECD=y
CONFIG_IDE_GENERIC=y
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
CONFIG_IDEDMA_PCI_AUTO=y
CONFIG_BLK_DEV_PIIX=y
CONFIG_BLK_DEV_IDEDMA=y
CONFIG_IDEDMA_AUTO=y
CONFIG_NET=y
CONFIG_PACKET=y
CONFIG_PACKET_MMAP=y
CONFIG_UNIX=y
CONFIG_NET_KEY=y
CONFIG_INET=y
CONFIG_XFRM=y
CONFIG_NETDEVICES=y
CONFIG_NET_ETHERNET=y
CONFIG_MII=y
CONFIG_NET_VENDOR_3COM=y
CONFIG_VORTEX=y
CONFIG_INPUT=y
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
CONFIG_SERIO_SERPORT=y
CONFIG_SERIO_LIBPS2=y
CONFIG_SOUND_GAMEPORT=y
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
CONFIG_SERIAL_8250=y
CONFIG_SERIAL_8250_CONSOLE=y
CONFIG_SERIAL_8250_NR_UARTS=4
CONFIG_SERIAL_8250_EXTENDED=y
CONFIG_SERIAL_8250_SHARE_IRQ=y
CONFIG_SERIAL_CORE=y
CONFIG_SERIAL_CORE_CONSOLE=y
CONFIG_UNIX98_PTYS=y
CONFIG_FTAPE=y
CONFIG_ZFTAPE=y
CONFIG_ZFT_DFLT_BLK_SZ=10240
CONFIG_ZFT_COMPRESSOR=y
CONFIG_FT_NR_BUFFERS=3
CONFIG_FT_PROC_FS=y
CONFIG_FT_NORMAL_DEBUG=y
CONFIG_FT_STD_FDC=y
CONFIG_FT_FDC_THR=8
CONFIG_FT_FDC_MAX_RATE=2000
CONFIG_FT_ALPHA_CLOCK=0
CONFIG_AGP=y
CONFIG_AGP_INTEL=y
CONFIG_VIDEO_DEV=y
CONFIG_VIDEO_SELECT=y
CONFIG_VGA_CONSOLE=y
CONFIG_DUMMY_CONSOLE=y
CONFIG_USB_ARCH_HAS_HCD=y
CONFIG_USB_ARCH_HAS_OHCI=y
CONFIG_EXT2_FS=y
CONFIG_EXT2_FS_XATTR=y
CONFIG_EXT3_FS=y
CONFIG_JBD=y
CONFIG_FS_MBCACHE=y
CONFIG_REISER4_FS=y
CONFIG_REISERFS_FS=y
CONFIG_ISO9660_FS=y
CONFIG_FAT_FS=y
CONFIG_VFAT_FS=y
CONFIG_FAT_DEFAULT_CODEPAGE=437
CONFIG_FAT_DEFAULT_IOCHARSET="iso8859-1"
CONFIG_NTFS_FS=y
CONFIG_NTFS_RW=y
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
CONFIG_DEVFS_FS=y
CONFIG_TMPFS=y
CONFIG_RAMFS=y
CONFIG_PARTITION_ADVANCED=y
CONFIG_MSDOS_PARTITION=y
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
CONFIG_NLS_CODEPAGE_850=y
CONFIG_NLS_ASCII=y
CONFIG_NLS_ISO8859_1=y
CONFIG_NLS_UTF8=y
CONFIG_DEBUG_KERNEL=y
CONFIG_MAGIC_SYSRQ=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_FRAME_POINTER=y
CONFIG_X86_FIND_SMP_CONFIG=y
CONFIG_X86_MPPARSE=y
CONFIG_SECURITY=y
CONFIG_SECURITY_NETWORK=y
CONFIG_SECURITY_CAPABILITIES=y
CONFIG_CRC_CCITT=y
CONFIG_CRC32=y
CONFIG_LIBCRC32C=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
CONFIG_X86_BIOS_REBOOT=y
Brice Goglin
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
Hi Andrew,
I can't get PCMCIA to work anymore since rc4-mm1.
It was working great with rc4 and rc3-mm1.
PCMCIA loads without any apparent problem (see attached dmesg).
But when I plug my orinoco card, nothing happens.
The hermes/orinoco modules are not even loaded as before.
cardctl insert/eject hangs.
Attached are dmesg and lsmod from rc4 and rc4-mm1, lspci and .config.
I'd like to help by reverting some patches.
But there seems to have tons of pcmcia modifications
since rc3-mm1.
Which one(s) do you think might be responsible for this ?
Regards,
Brice
> -pcmcia-add-support-ti-pci4510-cardbus-bridge.patch
> +pcmcia-bridge-resource-management-fix.patch
Andrew Morton
>
> This kernel came up, but my boot script complained about no /dev/hdb3
> when trying to mount /var.
> (I have two IDE disks on the same cable, and an IDE cdrom on another.)
> They are usually hda, hdb, and hdc.
>
> MAKEDEV hdq did not help. Looking at sysfs, it turns out that
> /dev/hdq1 is at major:3 minor:1025 if I interpret things right.
> (/dev/hda1 is at 3:1, which is correct.)
> These numbers did not work with my mknod, it created 7:1 instead.
> So I didn't get to test this mysterious device.
>
> But I assume this is a mistake of some sort, I haven't heard about any
> change in the IDE numbering coming up? 2.6.1-rc3-mm1 works as expected.
>
> It may be interesting to note that my root raid-1 came up fine,
> consisting of hdq1 and hda1 instead of the usual hdb1 and hda1.
I don't know what could be causing that. Please send .config. If you set
CONFIG_BASE_FULL=n, try setting it to `y'.
Andrew Morton
>
> Andrew Morton wrote:
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
> >
> >
> > - Various fixes and updates all over the place. Things seem to have slowed
> > down a bit.
> >
>
> I am having trouble getting recent -mm kernels to boot on my test box.
> For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
>
> VFS: Cannot open root device "301" or unknown-block(3,1)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
>
> 2.6.11-rc2-mm1 boots fine, and so do plain -rc3 and -rc4.
>
> I copied a working .config from an earlier kernel(-rc3), and ran make oldconfig,
> answering most of the new questions 'n'.
>
> I did try appending root=0301 (which worked last year after similar symptoms,
> but that didn't help this time).
>
> The root fs is ext3, which is compiled in.
> CONFIG_BASE_SMALL=1
Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0,
then retest.
Benoit Boissinot
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-=
rc4/2.6.11-rc4-mm1/
>
>
> - Various fixes and updates all over the place. Things seem to have =
slowed
> down a bit.
>
> - Last, final, ultimate call: if anyone has patches in here which are=
2.6.11
> material, please tell me.
>
>
>
> Changes since 2.6.11-rc3-mm1:
>
> make ITIMER_REAL per-process
>
> make-itimer_prof-itimer_virtual-per-process.patch
> make ITIMER_PROF, ITIMER_VIRTUAL per-process
>
gcc-4.0 warns with reasons on this patches:
kernel/itimer.c: In function ‘do_getitimer’:
kernel/itimer.c:61: warning: ‘val’ is used uninitialize=
d in this
function
Signed-off-by: Benoit Boissinot <benoit.b...@ens-lyon.org>
--- linux/kernel/itimer.c 2005-02-23 12:16:36.000000000 +0100
+++ linux-test/kernel/itimer.c 2005-02-23 21:53:10.000000000 +0100
@@ -58,7 +58,7 @@ int do_getitimer(int which, struct itime
if (cputime_le(cval, utime)) { /* about to fire */
val = jiffies_to_cputime(1);
} else {
- val = cputime_sub(val, utime);
+ val = cputime_sub(cval, utime);
}
}
spin_unlock_irq(&tsk->sighand->siglock);
@@ -84,7 +84,7 @@ int do_getitimer(int which, struct itime
if (cputime_le(cval, ptime)) { /* about to fire */
val = jiffies_to_cputime(1);
} else {
- val = cputime_sub(val, ptime);
+ val = cputime_sub(cval, ptime);
}
}
spin_unlock_irq(&tsk->sighand->siglock);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"=
Dominik Brodowski
On Wed, Feb 23, 2005 at 07:20:09PM +0100, Brice Goglin wrote:
> Andrew Morton a écrit :
> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11=
-rc4/2.6.11-rc4-mm1/
>
> I can't get PCMCIA to work anymore since rc4-mm1.
> It was working great with rc4 and rc3-mm1.
>
> PCMCIA loads without any apparent problem (see attached dmesg).
One thing surprises me: the sockets don't get IO resources allocated:
> yenta 0000:02:03.1: no resource of type 100 available, trying to cont=
inue...
> yenta 0000:02:03.1: no resource of type 100 available, trying to cont=
inue...
which doesn't happen in earlier kernels. In lspci this shows itself as:
I/O window 0: 00000000-00000003 =
I/O window 1: 00000000-00000003 =
> Which one(s) do you think might be responsible for this ?
My gut tells me
> >+pcmcia-bridge-resource-management-fix.patch
is responsible for this "no resource available" message, because the ot=
her
ones relate to other areas.
If the error persists, it'd be great if you could apply the other PCMCI=
A
patches to the working -rc4 tree and check if it continues to work -- o=
r,
the other way round, removing the PCMCIA patches completely and checkin=
g
whether it works then.
Thanks,
Dominik
Adrian Bunk
> Changes since 2.6.11-rc3-mm1:
>...
> bk-kbuild.patch
>...
This adds -Wno-pointer-sign to the main Makefile a second time.
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
Roland McGrath
Ack! I did a quick merge of my well-tested patches with the cputime_t
stuff, and apparently didn't do quite as much testing as I thought I did.
There was a little query/replace error in my per-process-itimer-cpu patch
now in -mm. Your patch is necessary but not sufficient. This patch fixes
all the errors.
Thanks,
Roland
Signed-off-by: Roland McGrath <rol...@redhat.com>
--- linux-2.6/kernel/itimer.c
+++ linux-2.6/kernel/itimer.c
@@ -56,9 +56,9 @@ int do_getitimer(int which, struct itime
t = next_thread(t);
} while (t != tsk);
if (cputime_le(cval, utime)) { /* about to fire */
- val = jiffies_to_cputime(1);
+ cval = jiffies_to_cputime(1);
} else {
- val = cputime_sub(val, utime);
+ cval = cputime_sub(cval, utime);
}
}
spin_unlock_irq(&tsk->sighand->siglock);
@@ -82,9 +82,9 @@ int do_getitimer(int which, struct itime
t = next_thread(t);
} while (t != tsk);
if (cputime_le(cval, ptime)) { /* about to fire */
- val = jiffies_to_cputime(1);
+ cval = jiffies_to_cputime(1);
} else {
- val = cputime_sub(val, ptime);
+ cval = cputime_sub(cval, ptime);
}
}
spin_unlock_irq(&tsk->sighand->siglock);
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
John Cherry
Web page with links to complete details:
http://developer.osdl.org/cherry/compile/
Kernel bzImage bzImage bzImage modules bzImage modules
(defconfig) (allno) (allyes) (allyes) (allmod) (allmod)
--------------- ---------- -------- -------- -------- -------- --------
2.6.11-rc4-mm1 22w/0e 0w/0e 271w/0e 10w/0e 25w/0e 249w/0e
2.6.11-rc3-mm2 14w/0e 0w/0e 192w/0e 6w/0e 19w/0e 172w/0e
2.6.11-rc3-mm1 13w/10e 0w/7e 196w/12e 6w/0e 18w/12e 177w/0e
2.6.11-rc2-mm2 15w/0e 0w/0e 201w/0e 6w/0e 18w/0e 182w/0e
2.6.11-rc2-mm1 15w/0e 0w/0e 306w/14e 6w/0e 18w/0e 294w/0e
2.6.11-rc1-mm2 21w/0e 0w/0e 316w/9e 6w/0e 22w/0e 294w/0e
2.6.11-rc1-mm1 21w/0e 0w/0e 319w/0e 6w/0e 23w/0e 298w/0e
2.6.10-mm3 21w/0e 0w/0e 320w/0e 6w/0e 23w/0e 299w/0e
2.6.10-mm2 21w/0e 0w/0e 440w/0e 6w/0e 23w/0e 420w/0e
2.6.10-mm1 12w/0e 0w/0e 414w/0e 6w/0e 17w/0e 399w/0e
2.6.10-rc3-mm1 12w/0e 0w/0e 414w/0e 6w/0e 16w/0e 401w/0e
2.6.10-rc2-mm4 15w/0e 1w/7e 421w/0e 6w/0e 16w/0e 408w/0e
2.6.10-rc2-mm3 15w/0e 0w/0e 1255w/12e 66w/0e 16w/0e 1507w/0e
2.6.10-rc2-mm2 15w/0e 0w/0e 1362w/15e 65w/0e 16w/0e 1612w/2e
2.6.10-rc2-mm1 15w/0e 0w/0e 1405w/11e 65w/0e 16w/0e 1652w/0e
2.6.10-rc1-mm5 16w/0e 0w/0e 1587w/0e 65w/0e 20w/0e 1834w/0e
2.6.10-rc1-mm4 16w/0e 0w/0e 1485w/9e 65w/0e 20w/0e 1732w/0e
(Compiles with gcc 3.2.2)
2.6.10-rc1-mm3 7w/31e 0w/9e 496w/141e 4w/0e 4w/50e 693w/83e
2.6.10-rc1-mm2 16w/1e 1w/1e 529w/1e 4w/0e 12w/1e 729w/0e
2.6.10-mm1 12w/0e 0w/0e 414w/0e 6w/0e 17w/0e 399w/0e
2.6.10-rc3-mm1 12w/0e 0w/0e 414w/0e 6w/0e 16w/0e 401w/0e
2.6.10-rc2-mm4 15w/0e 1w/7e 421w/0e 6w/0e 16w/0e 408w/0e
2.6.10-rc2-mm3 15w/0e 0w/0e 1255w/12e 66w/0e 16w/0e 1507w/0e
2.6.10-rc2-mm2 15w/0e 0w/0e 1362w/15e 65w/0e 16w/0e 1612w/2e
2.6.10-rc2-mm1 15w/0e 0w/0e 1405w/11e 65w/0e 16w/0e 1652w/0e
2.6.10-rc1-mm5 16w/0e 0w/0e 1587w/0e 65w/0e 20w/0e 1834w/0e
2.6.10-rc1-mm4 16w/0e 0w/0e 1485w/9e 65w/0e 20w/0e 1732w/0e
(Compiles with gcc 3.2.2)
2.6.10-rc1-mm3 7w/31e 0w/9e 496w/141e 4w/0e 4w/50e 693w/83e
2.6.10-rc1-mm2 16w/1e 1w/1e 529w/1e 4w/0e 12w/1e 729w/0e
2.6.10-rc1-mm1 16w/1e 1w/1e 592w/1e 4w/0e 13w/1e 857w/0e
2.6.9-mm1 6w/1e 1w/1e 1761w/15e 65w/0e 9w/0e 2086w/0e
2.6.9-rc4-mm1 5w/0e 0w/0e 1766w/11e 43w/0e 6w/0e 1798w/0e
2.6.9-rc3-mm3 5w/0e 0w/0e 1756w/11e 43w/0e 4w/0e 1786w/0e
2.6.9-rc3-mm2 10w/0e 4w/9e 1754w/14e 43w/0e 4w/0e 1782w/1e
2.6.9-rc3-mm1 10w/0e 4w/10e 1768w/0e 43w/0e 4w/0e 1796w/0e
2.6.9-rc2-mm4 10w/0e 5w/0e 2573w/0e 41w/0e 4w/0e 2600w/0e
2.6.9-rc2-mm3 10w/0e 5w/0e 2400w/0e 41w/0e 4w/0e 2435w/0e
2.6.9-rc2-mm2 10w/0e 5w/0e 2919w/0e 41w/0e 4w/0e 2954w/0e
2.6.9-rc2-mm1 0w/0e 2w/0e 3541w/9e 41w/0e 3w/9e 3567w/0e
2.6.9-rc1-mm4 0w/0e 1w/0e 55w/0e 3w/0e 2w/0e 48w/0e
2.6.9-rc1-mm3 0w/0e 0w/0e 55w/13e 3w/0e 1w/0e 49w/1e
2.6.9-rc1-mm2 0w/0e 0w/0e 53w/11e 3w/0e 1w/0e 47w/0e
2.6.9-rc1-mm1 0w/0e 0w/0e 80w/0e 4w/0e 1w/0e 74w/0e
2.6.8.1-mm4 0w/0e 0w/0e 78w/0e 4w/0e 1w/0e 73w/0e
2.6.8.1-mm3 0w/96e 0w/0e 78w/97e 4w/0e 1w/0e 74w/89e
2.6.8.1-mm2 0w/96e 0w/0e 78w/97e 4w/0e 1w/0e 74w/89e
2.6.8.1-mm1 0w/0e 0w/0e 78w/0e 4w/0e 1w/0e 74w/0e
2.6.8-rc4-mm1 0w/0e 0w/5e 81w/0e 4w/0e 1w/0e 75w/0e
2.6.8-rc3-mm2 1w/7e 0w/5e 82w/8e 4w/0e 2w/8e 75w/0e
2.6.8-rc3-mm1 0w/0e 1w/5e 81w/9e 4w/0e 1w/0e 75w/0e
2.6.8-rc2-mm2 0w/0e 4w/5e 87w/9e 4w/0e 1w/0e 80w/0e
2.6.8-rc2-mm1 0w/0e 0w/0e 83w/9e 3w/0e 1w/0e 81w/0e
2.6.8-rc1-mm1 0w/0e 0w/0e 88w/9e 5w/0e 1w/0e 87w/0e
2.6.7-mm7 0w/0e 0w/0e 89w/9e 5w/0e 1w/0e 84w/0e
2.6.7-mm6 0w/0e 0w/0e 85w/9e 5w/0e 1w/0e 80w/0e
2.6.7-mm5 0w/0e 0w/0e 92w/0e 5w/0e 1w/0e 87w/0e
2.6.7-mm4 0w/0e 0w/0e 94w/0e 5w/0e 1w/0e 89w/0e
2.6.7-mm3 0w/0e 0w/0e 90w/6e 5w/0e 1w/0e 86w/0e
2.6.7-mm2 0w/0e 0w/0e 109w/0e 7w/0e 1w/0e 106w/0e
2.6.7-mm1 0w/0e 5w/0e 108w/0e 5w/0e 1w/0e 104w/0e
2.6.7-rc3-mm2 0w/0e 5w/0e 105w/10e 5w/0e 2w/0e 100w/2e
2.6.7-rc3-mm1 0w/0e 5w/0e 104w/10e 5w/0e 2w/0e 100w/2e
2.6.7-rc2-mm2 0w/0e 5w/0e 109w/10e 5w/0e 2w/0e 105w/2e
2.6.7-rc2-mm1 0w/0e 12w/0e 158w/13e 5w/0e 3w/0e 153w/4e
2.6.7-rc1-mm1 0w/0e 6w/0e 108w/0e 5w/0e 2w/0e 104w/0e
2.6.6-mm5 0w/0e 0w/0e 109w/5e 5w/0e 2w/0e 110w/0e
2.6.6-mm4 0w/0e 0w/0e 112w/9e 5w/0e 2w/5e 106w/1e
2.6.6-mm3 3w/9e 0w/0e 120w/26e 5w/0e 2w/0e 114w/10e
2.6.6-mm2 4w/11e 0w/0e 120w/24e 6w/0e 2w/0e 118w/9e
2.6.6-mm1 1w/0e 0w/0e 118w/25e 6w/0e 2w/0e 114w/10e
2.6.6-rc3-mm2 0w/0e 0w/0e 117w/ 0e 8w/0e 2w/0e 116w/0e
2.6.6-rc3-mm1 0w/0e 0w/0e 120w/10e 8w/0e 2w/0e 152w/2e
2.6.6-rc2-mm2 0w/0e 1w/5e 118w/ 0e 8w/0e 3w/0e 118w/0e
2.6.6-rc2-mm1 0w/0e 0w/0e 115w/ 0e 7w/0e 3w/0e 116w/0e
2.6.6-rc1-mm1 0w/0e 0w/7e 122w/ 0e 7w/0e 4w/0e 122w/0e
2.6.5-mm6 0w/0e 0w/0e 123w/ 0e 7w/0e 4w/0e 124w/0e
2.6.5-mm5 0w/0e 0w/0e 119w/ 0e 7w/0e 4w/0e 120w/0e
2.6.5-mm4 0w/0e 0w/0e 120w/ 0e 7w/0e 4w/0e 121w/0e
2.6.5-mm3 0w/0e 1w/0e 121w/12e 7w/0e 3w/0e 123w/0e
2.6.5-mm2 0w/0e 0w/0e 128w/12e 7w/0e 3w/0e 134w/0e
2.6.5-mm1 0w/0e 5w/0e 122w/ 0e 7w/0e 3w/0e 124w/0e
2.6.5-rc3-mm4 0w/0e 0w/0e 124w/ 0e 8w/0e 4w/0e 126w/0e
2.6.5-rc3-mm3 0w/0e 5w/0e 129w/14e 8w/0e 4w/0e 129w/6e
2.6.5-rc3-mm2 0w/0e 5w/0e 130w/14e 8w/0e 4w/0e 129w/6e
2.6.5-rc3-mm1 0w/0e 5w/0e 129w/ 0e 8w/0e 4w/0e 129w/0e
2.6.5-rc2-mm5 0w/0e 5w/0e 130w/ 0e 8w/0e 4w/0e 129w/0e
2.6.5-rc2-mm4 0w/0e 5w/0e 134w/ 0e 8w/0e 3w/0e 133w/0e
2.6.5-rc2-mm3 0w/0e 5w/0e 134w/ 0e 8w/0e 3w/0e 133w/0e
2.6.5-rc2-mm2 0w/0e 5w/0e 137w/ 0e 8w/0e 3w/0e 134w/0e
2.6.5-rc2-mm1 0w/0e 5w/0e 136w/ 0e 8w/0e 3w/0e 134w/0e
2.6.5-rc1-mm2 0w/0e 5w/0e 135w/ 5e 8w/0e 3w/0e 133w/0e
2.6.5-rc1-mm1 0w/0e 5w/0e 135w/ 5e 8w/0e 3w/0e 133w/0e
2.6.4-mm2 1w/2e 5w/2e 144w/10e 8w/0e 3w/2e 144w/0e
2.6.4-mm1 1w/0e 5w/0e 146w/ 5e 8w/0e 3w/0e 144w/0e
2.6.4-rc2-mm1 1w/0e 5w/0e 146w/12e 11w/0e 3w/0e 147w/2e
2.6.4-rc1-mm2 1w/0e 5w/0e 144w/ 0e 11w/0e 3w/0e 145w/0e
2.6.4-rc1-mm1 1w/0e 5w/0e 147w/ 5e 11w/0e 3w/0e 147w/0e
2.6.3-mm4 1w/0e 5w/0e 146w/ 0e 7w/0e 3w/0e 142w/0e
2.6.3-mm3 1w/2e 5w/2e 146w/15e 7w/0e 3w/2e 144w/5e
2.6.3-mm2 1w/8e 5w/0e 140w/ 0e 7w/0e 3w/0e 138w/0e
2.6.3-mm1 1w/0e 5w/0e 143w/ 5e 7w/0e 3w/0e 141w/0e
2.6.3-rc3-mm1 1w/0e 0w/0e 144w/13e 7w/0e 3w/0e 142w/3e
2.6.3-rc2-mm1 1w/0e 0w/265e 144w/ 5e 7w/0e 3w/0e 145w/0e
2.6.3-rc1-mm1 1w/0e 0w/265e 141w/ 5e 7w/0e 3w/0e 143w/0e
2.6.2-mm1 2w/0e 0w/264e 147w/ 5e 7w/0e 3w/0e 173w/0e
2.6.2-rc3-mm1 2w/0e 0w/265e 146w/ 5e 7w/0e 3w/0e 172w/0e
2.6.2-rc2-mm2 0w/0e 0w/264e 145w/ 5e 7w/0e 3w/0e 171w/0e
2.6.2-rc2-mm1 0w/0e 0w/264e 146w/ 5e 7w/0e 3w/0e 172w/0e
2.6.2-rc1-mm3 0w/0e 0w/265e 144w/ 8e 7w/0e 3w/0e 169w/0e
2.6.2-rc1-mm2 0w/0e 0w/264e 144w/ 5e 10w/0e 3w/0e 171w/0e
2.6.2-rc1-mm1 0w/0e 0w/264e 144w/ 5e 10w/0e 3w/0e 171w/0e
2.6.1-mm5 2w/5e 0w/264e 153w/11e 10w/0e 3w/0e 180w/0e
2.6.1-mm4 0w/821e 0w/264e 154w/ 5e 8w/1e 5w/0e 179w/0e
2.6.1-mm3 0w/0e 0w/0e 151w/ 5e 10w/0e 3w/0e 177w/0e
2.6.1-mm2 0w/0e 0w/0e 143w/ 5e 12w/0e 3w/0e 171w/0e
2.6.1-mm1 0w/0e 0w/0e 146w/ 9e 12w/0e 6w/0e 171w/0e
2.6.1-rc2-mm1 0w/0e 0w/0e 149w/ 0e 12w/0e 6w/0e 171w/4e
2.6.1-rc1-mm2 0w/0e 0w/0e 157w/15e 12w/0e 3w/0e 185w/4e
2.6.1-rc1-mm1 0w/0e 0w/0e 156w/10e 12w/0e 3w/0e 184w/2e
2.6.0-mm2 0w/0e 0w/0e 161w/ 0e 12w/0e 3w/0e 189w/0e
2.6.0-mm1 0w/0e 0w/0e 173w/ 0e 12w/0e 3w/0e 212w/0e
John
Brice Goglin
>>>+pcmcia-bridge-resource-management-fix.patch
>
> is responsible for this "no resource available" message, because the =
other
> ones relate to other areas.
Yes, good catch, reverting it makes PCMCIA work again.
Let me know if you want me to test some patches.
Thanks,
Brice
Steven Cole
> Steven Cole <elen...@mesatop.com> wrote:
>> I am having trouble getting recent -mm kernels to boot on my test box.
>> For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
>>
>> VFS: Cannot open root device "301" or unknown-block(3,1)
>> Please append a correct "root=" boot option
>> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
>>
[snipped]
>
> Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0,
> then retest.
Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be missing.
[root@spc1 steven]# uname -r
2.6.11-rc4-mm1-GX110
[root@spc1 steven]# mount -t reiser4 /dev/hdb1 /reiser4_testing
mount: special device /dev/hdb1 does not exist
Reading another post (and looking in /dev), I tried hdq:
[root@spc1 steven]# mount -t reiser4 /dev/hdq1 /reiser4_testing
[root@spc1 steven]# df -T
Filesystem Type Size Used Avail Use% Mounted on
/dev/hda1 ext3 304M 75M 214M 26% /
/dev/hda9 reiserfs 8.3G 3.9G 4.4G 48% /home
/dev/hda8 ext3 464M 8.1M 432M 2% /tmp
/dev/hda6 ext3 7.4G 1.7G 5.4G 24% /usr
/dev/hda7 ext3 1.9G 86M 1.7G 5% /var
/dev/hdq1 reiser4 18G 217M 18G 2% /reiser4_testing
Snipped from dmesg:
hda: ST320423A, ATA DISK drive
hdb: WDC WD200BB-75AUA1, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: SONY CD-RW CRX160E, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
hda: max request size: 128KiB
hda: 40011300 sectors (20485 MB) w/512KiB Cache, CHS=39693/16/63, UDMA(66)
hda: cache flushes not supported
/dev/ide/host0/bus0/target0/lun0: p1 p2 < p5 p6 p7 p8 p9 >
hdb: max request size: 128KiB
hdb: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(66)
hdb: cache flushes not supported
/dev/ide/host0/bus0/target1/lun0: p1
Steven
Francois Romieu
[...]
> - Last, final, ultimate call: if anyone has patches in here which are 2.6.11
> material, please tell me.
Any chance to convince the alien who took control of Jeff's libata queue to
push:
r8169: synchronization and balancing when the device is closed
(1.1982.1.58 ?)
Test case on current 2.6.11-rc4:
- ifconfig ethX 10.0.0.1 up
- ifconfig ethX down
- ifconfig ethX 10.0.0.1 up
-> Rx does not work any more
- ifconfig ethX down
-> command hangs
--
Ueimor
J.A. Magallon
On 02.23, Andrew Morton wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
>
>
> - Various fixes and updates all over the place. Things seem to have slowed
> down a bit.
>
> - Last, final, ultimate call: if anyone has patches in here which are 2.6.11
> material, please tell me.
>
Two points:
- I lost my keyboard :(. USB, but plugged into PS/2 with an adapter.
- hdb is missing. initscripts show an strange message about hdq ??
As I read the same on other post, I think something has screwed the
ide device naming scheme ...
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.10-jam10 (gcc 3.4.3 (Mandrakelinux 10.2 3.4.3-3mdk)) #2
Laurent Riffard
> Helge Hafting <helge....@aitel.hist.no> wrote:
>
>>This kernel came up, but my boot script complained about no /dev/hdb3
>> when trying to mount /var.
>> (I have two IDE disks on the same cable, and an IDE cdrom on another.)
>> They are usually hda, hdb, and hdc.
>>
>> MAKEDEV hdq did not help. Looking at sysfs, it turns out that
>> /dev/hdq1 is at major:3 minor:1025 if I interpret things right.
>> (/dev/hda1 is at 3:1, which is correct.)
>> These numbers did not work with my mknod, it created 7:1 instead.
>> So I didn't get to test this mysterious device.
>>
>> But I assume this is a mistake of some sort, I haven't heard about any
>> change in the IDE numbering coming up? 2.6.1-rc3-mm1 works as expected.
>>
>> It may be interesting to note that my root raid-1 came up fine,
>> consisting of hdq1 and hda1 instead of the usual hdb1 and hda1.
>
>
> I don't know what could be causing that. Please send .config. If you set
> CONFIG_BASE_FULL=n, try setting it to `y'.
>
this is just a "me too"...
Here is some few lines from dmesg :
Uniform Multi-Platform E-IDE driver Revision: 7.00alpha2
ide: Assuming 33MHz system bus speed for PIO modes; override with idebus=xx
VP_IDE: IDE controller at PCI slot 0000:00:04.1
VP_IDE: chipset revision 6
VP_IDE: not 100% native mode: will probe irqs later
VP_IDE: VIA vt82c686b (rev 40) IDE UDMA100 controller on pci0000:00:04.1
ide0: BM-DMA at 0xd800-0xd807, BIOS settings: hda:DMA, hdb:DMA
ide1: BM-DMA at 0xd808-0xd80f, BIOS settings: hdc:DMA, hdd:DMA
Probing IDE interface ide0...
hda: ST340016A, ATA DISK drive
hdb: Maxtor 6Y080L0, ATA DISK drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14
Probing IDE interface ide1...
hdc: CD-950E/AKU, ATAPI CD/DVD-ROM drive
hdd: LITE-ON LTR-48125S, ATAPI CD/DVD-ROM drive
ide1 at 0x170-0x177,0x376 on irq 15
Probing IDE interface ide2...
Probing IDE interface ide3...
Probing IDE interface ide4...
Probing IDE interface ide5...
hda: max request size: 128KiB
hda: 78165360 sectors (40020 MB) w/2048KiB Cache, CHS=65535/16/63, UDMA(100)
hda: cache flushes not supported
hda: hda1 hda2 hda3 < hda5 hda6 hda7 hda8 hda9 hda10 > hda4
hdb: max request size: 128KiB
hdb: 160086528 sectors (81964 MB) w/2048KiB Cache, CHS=65535/16/63,
UDMA(100)
hdb: cache flushes supported
hdq: hdq1 hdq2 < hdq5 hdq6 hdq7 hdq8 >
~$ ls -l /dev/hd*
brw-rw---- 1 root disk 3, 0 fév 23 22:45 /dev/hda
brw-rw---- 1 root disk 3, 1 fév 23 22:45 /dev/hda1
brw-rw---- 1 root disk 3, 10 fév 23 22:45 /dev/hda10
brw-rw---- 1 root disk 3, 2 fév 23 22:45 /dev/hda2
brw-rw---- 1 root disk 3, 3 fév 23 22:45 /dev/hda3
brw-rw---- 1 root disk 3, 4 fév 23 22:45 /dev/hda4
brw-rw---- 1 root disk 3, 5 fév 23 22:45 /dev/hda5
brw-rw---- 1 root disk 3, 6 fév 23 22:45 /dev/hda6
brw-rw---- 1 root disk 3, 7 fév 23 22:45 /dev/hda7
brw-rw---- 1 root disk 3, 8 fév 23 22:45 /dev/hda8
brw-rw---- 1 root disk 3, 9 fév 23 22:45 /dev/hda9
brw-rw---- 1 laurent cdrom 22, 0 fév 23 22:45 /dev/hdc
brw------- 1 root root 22, 64 fév 23 22:45 /dev/hdd
brw-rw---- 1 root disk 3, 1024 fév 23 22:45 /dev/hdq
brw-rw---- 1 root disk 3, 1025 fév 23 22:45 /dev/hdq1
brw-rw---- 1 root disk 3, 1026 fév 23 22:45 /dev/hdq2
brw-rw---- 1 root disk 3, 1029 fév 23 22:45 /dev/hdq5
brw-rw---- 1 root disk 3, 1030 fév 23 22:45 /dev/hdq6
brw-rw---- 1 root disk 3, 1031 fév 23 22:45 /dev/hdq7
brw-rw---- 1 root disk 3, 1032 fév 23 22:45 /dev/hdq8
brw-rw---- 1 root disk 22, 1024 fév 23 22:45 /dev/hds
/dev/hdq should be /dev/hdb.
hey, what's this /dev/hds ? digging into /sys/block...
~$ ls -l /sys/block/hds/device
lrwxrwxrwx 1 root root 0 fév 23 22:45 /sys/block/hds/device ->
../../devices/pci0000:00/0000:00:04.1/ide1/1.1/
/dev/hdq should be /dev/hdd...
~$ ls -l /proc/ide
total 4
-r--r--r-- 1 root root 0 fév 23 23:28 drivers
lrwxrwxrwx 1 root root 8 fév 23 23:28 hda -> ide0/hda/
lrwxrwxrwx 1 root root 8 fév 23 23:28 hdb -> ide0/hdb/
lrwxrwxrwx 1 root root 8 fév 23 23:28 hdc -> ide1/hdc/
lrwxrwxrwx 1 root root 8 fév 23 23:28 hdd -> ide1/hdd/
dr-xr-xr-x 4 root root 0 fév 23 23:28 ide0/
dr-xr-xr-x 4 root root 0 fév 23 23:28 ide1/
-r--r--r-- 1 root root 0 fév 23 23:28 via
~$ ls -d /sys/block/hd*
/sys/block/hda/ /sys/block/hdc/ /sys/block/hdq/ /sys/block/hds/
.config is attached
~~
laurent
Matt Mackall
> I copied a working .config from an earlier kernel(-rc3), and ran make
> oldconfig, answering most of the new questions 'n'.
Then you get into trouble with stuff under CONFIG_EMBEDDED. Answering
'n' turns off stock functionality. Though you really ought not have
CONFIG_EMBEDDED turned on anyway. I'm not sure how CONFIG_BASE_SMALL
is causing problems as the blockdev bit got dropped already. I'll poke
around..
Andrew, looks like turning on EMBEDDED causes a bunch of options to
spill onto the general setup menu in menuconfig because of the
placement of the bool piece:
Fix up bustedness in menuconfig
Signed-off-by: Matt Mackall <m...@selenic.com>
Index: mm1/init/Kconfig
===================================================================
--- mm1.orig/init/Kconfig 2005-02-23 13:32:38.000000000 -0800
+++ mm1/init/Kconfig 2005-02-23 14:27:18.699676896 -0800
@@ -274,11 +274,6 @@ config BASE_FULL
Disabling this option reduces the size of miscellaneous core
kernel data structures.
-config BASE_SMALL
- int
- default 0 if BASE_FULL
- default 1 if !BASE_FULL
-
config FUTEX
bool "Enable futex support" if EMBEDDED
default y
@@ -360,6 +355,11 @@ config TINY_SHMEM
default !SHMEM
bool
+config BASE_SMALL
+ int
+ default 0 if BASE_FULL
+ default 1 if !BASE_FULL
+
menu "Loadable module support"
config MODULES
--
Mathematics is the supreme nostalgia of our time.
Steven Cole
(Replying to myself)
I decided to fix 2.6.11-rc3-mm1 with CONFIG_BASE_FULL=y and see if
the hdb/hdq confusion existed with that earlier kernel, but when I
ran lilo, I got a "Fatal: cache_add: LILO internal error" message.
[root@spc1 steven]# /sbin/lilo -v
LILO version 22.6.1, Copyright (C) 1992-1998 Werner Almesberger
Development beyond version 21 Copyright (C) 1999-2004 John Coffman
Released 17-Nov-2004, and compiled at 20:03:17 on Jan 15 2005
Reading boot sector from /dev/hda
Fatal: cache_add: LILO internal error
This box is still running 2.6.11-rc4-mm1 from above, and was booted
with append="root=0301" accidentally left in lilo.conf from earlier testing.
Matt Mackall
> Steven Cole <elen...@mesatop.com> wrote:
> >
> > Andrew Morton wrote:
> > > Steven Cole <elen...@mesatop.com> wrote:
> >
> > >> I am having trouble getting recent -mm kernels to boot on my test box.
> > >> For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
> > >>
> > >> VFS: Cannot open root device "301" or unknown-block(3,1)
> > >> Please append a correct "root=" boot option
> > >> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
> > >>
> > [snipped]
> > >
> > > Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0,
> > > then retest.
> >
> > Yes, that worked.
>
> base-small-shrink-chrdevs-hash.patch has the same problem which
> base-small-shrink-major_names-hash.patch had.
Hard to see how that could happen.
> > 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be missing.
> >
> > [root@spc1 steven]# uname -r
> > 2.6.11-rc4-mm1-GX110
> > [root@spc1 steven]# mount -t reiser4 /dev/hdb1 /reiser4_testing
> > mount: special device /dev/hdb1 does not exist
>
> It would seem that your /dev/hdb1 block-special device node isn't present.
> Try `mknod /dev/hdb1 3 65'.
He's got devfs. Something change there recently?
--
Mathematics is the supreme nostalgia of our time.
Matt Mackall
> Le 23.02.2005 21:12, Andrew Morton a ?crit :
> >Helge Hafting <helge....@aitel.hist.no> wrote:
> >
> >>This kernel came up, but my boot script complained about no /dev/hdb3
> >>when trying to mount /var.
> >>(I have two IDE disks on the same cable, and an IDE cdrom on another.)
> >>They are usually hda, hdb, and hdc.
> >>
> >>MAKEDEV hdq did not help. Looking at sysfs, it turns out that
> >>/dev/hdq1 is at major:3 minor:1025 if I interpret things right.
> >>(/dev/hda1 is at 3:1, which is correct.)
> >>These numbers did not work with my mknod, it created 7:1 instead.
> >>So I didn't get to test this mysterious device.
> >>
> >>But I assume this is a mistake of some sort, I haven't heard about any
> >>change in the IDE numbering coming up? 2.6.1-rc3-mm1 works as expected.
> >>
> >>It may be interesting to note that my root raid-1 came up fine,
> >>consisting of hdq1 and hda1 instead of the usual hdb1 and hda1.
> >
> >
> >I don't know what could be causing that. Please send .config. If you set
> >CONFIG_BASE_FULL=n, try setting it to `y'.
> >
>
> this is just a "me too"...
>
> Here is some few lines from dmesg :
>
> hdq: hdq1 hdq2 < hdq5 hdq6 hdq7 hdq8 >
Neat.
> ~$ ls -l /dev/hd*
> brw-rw---- 1 root disk 3, 0 f?v 23 22:45 /dev/hda
> brw-rw---- 1 root disk 3, 1 f?v 23 22:45 /dev/hda1
> brw-rw---- 1 root disk 3, 10 f?v 23 22:45 /dev/hda10
> brw-rw---- 1 root disk 3, 2 f?v 23 22:45 /dev/hda2
> brw-rw---- 1 root disk 3, 3 f?v 23 22:45 /dev/hda3
> brw-rw---- 1 root disk 3, 4 f?v 23 22:45 /dev/hda4
> brw-rw---- 1 root disk 3, 5 f?v 23 22:45 /dev/hda5
> brw-rw---- 1 root disk 3, 6 f?v 23 22:45 /dev/hda6
> brw-rw---- 1 root disk 3, 7 f?v 23 22:45 /dev/hda7
> brw-rw---- 1 root disk 3, 8 f?v 23 22:45 /dev/hda8
> brw-rw---- 1 root disk 3, 9 f?v 23 22:45 /dev/hda9
> brw-rw---- 1 laurent cdrom 22, 0 f?v 23 22:45 /dev/hdc
> brw------- 1 root root 22, 64 f?v 23 22:45 /dev/hdd
> brw-rw---- 1 root disk 3, 1024 f?v 23 22:45 /dev/hdq
Looks like you're using udev.
> CONFIG_BASE_FULL=y
> CONFIG_BASE_SMALL=0
Ok, that's unrelated to the weird IDE numbering then.
Andrew Morton
>
> It does not seem to be finding the keyboard at all...
Can you confirm that Linus's tree is OK? You'd best use the patch
at http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/ to make sure you
have the latest stuff.
Ed Tomlinson
>
> On 02.23, Andrew Morton wrote:
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
> >
> >
> > - Various fixes and updates all over the place. Things seem to have slowed
> > down a bit.
> >
> > - Last, final, ultimate call: if anyone has patches in here which are 2.6.11
> > material, please tell me.
> >
>
> Two points:
>
> - I lost my keyboard :(. USB, but plugged into PS/2 with an adapter.
Mine too. Details sent in another message...
Ed
Andrew Morton
>
> Le 23.02.2005 21:12, Andrew Morton a écrit :
> > Helge Hafting <helge....@aitel.hist.no> wrote:
> >
b3
> >> when trying to mount /var.
er.)
> >> They are usually hda, hdb, and hdc.
> >>
> >> MAKEDEV hdq did not help. Looking at sysfs, it turns out that
> >> /dev/hdq1 is at major:3 minor:1025 if I interpret things right.
> >> (/dev/hda1 is at 3:1, which is correct.)
> >> These numbers did not work with my mknod, it created 7:1 instead.
> >> So I didn't get to test this mysterious device.
> >>
any
> >> change in the IDE numbering coming up? 2.6.1-rc3-mm1 works as exp=
ected.
> >>
> >> It may be interesting to note that my root raid-1 came up fine,
> >> consisting of hdq1 and hda1 instead of the usual hdb1 and hda1.
> >
> >
you set
> > CONFIG_BASE_FULL=n, try setting it to `y'.
> >
>
> this is just a "me too"...
Confusing. Are you saying that the hdd->hdq problem is happening even =
with
CONFIG_BASE_FULL=y?
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel"=
Ed Tomlinson
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
>
>
> - Various fixes and updates all over the place. Things seem to have slowed
> down a bit.
>
> - Last, final, ultimate call: if anyone has patches in here which are 2.6.11
> material, please tell me.
It boots fine here except that my keyboard is dead, rc3-mm2 is fine. The .config was built via
using rc3-mm2's config and make oldconfig. Looking it the boot log I see:
in rc3-mm2
Feb 23 17:49:20 grover kernel: Initializing Cryptographic API
Feb 23 17:49:20 grover kernel: Linux agpgart interface v0.101 (c) Dave Jones
Feb 23 17:49:20 grover kernel: [drm] Initialized drm 1.0.0 20040925
Feb 23 17:49:20 grover kernel: ACPI: PS/2 Keyboard Controller [PS2K] at I/O 0x60, 0x64, irq 1
Feb 23 17:49:20 grover kernel: ACPI: PS/2 Mouse Controller [PS2M] at irq 12
Feb 23 17:49:20 grover kernel: serio: i8042 AUX port at 0x60,0x64 irq 12
Feb 23 17:49:20 grover kernel: serio: i8042 KBD port at 0x60,0x64 irq 1
Feb 23 17:49:20 grover kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
in rc4-mm1
Feb 23 17:46:54 grover kernel: Initializing Cryptographic API
Feb 23 17:46:54 grover kernel: inotify device minor=63
Feb 23 17:46:54 grover kernel: Linux agpgart interface v0.101 (c) Dave Jones
Feb 23 17:46:54 grover kernel: [drm] Initialized drm 1.0.0 20040925
Feb 23 17:46:54 grover kernel: Serial: 8250/16550 driver $Revision: 1.90 $ 48 ports, IRQ sharing enabled
Feb 23 17:46:54 grover kernel: ttyS0 at I/O 0x3f8 (irq = 4) is a 16550A
It does not seem to be finding the keyboard at all...
Ideas?
Ed Tomlinson
diff -u ../11-3-2/.config .config
--- ../11-3-2/.config 2005-02-12 09:55:28.000000000 -0500
+++ .config 2005-02-23 07:10:53.000000000 -0500
@@ -1,7 +1,7 @@
#
# Automatically generated make config: don't edit
-# Linux kernel version: 2.6.11-rc3-mm2
-# Sat Feb 12 09:55:28 2005
+# Linux kernel version: 2.6.11-rc4-mm1
+# Wed Feb 23 07:10:53 2005
#
CONFIG_X86_64=y
CONFIG_64BIT=y
@@ -91,6 +91,7 @@
CONFIG_X86_MCE_INTEL=y
CONFIG_PHYSICAL_START=0x100000
CONFIG_KEXEC=y
+CONFIG_SECCOMP=y
CONFIG_GENERIC_HARDIRQS=y
CONFIG_GENERIC_IRQ_PROBE=y
@@ -119,6 +120,8 @@
CONFIG_ACPI_ASUS=m
# CONFIG_ACPI_IBM is not set
CONFIG_ACPI_TOSHIBA=m
+# CONFIG_ACPI_PCC is not set
+# CONFIG_ACPI_SONY is not set
CONFIG_ACPI_BLACKLIST_YEAR=0
# CONFIG_ACPI_DEBUG is not set
CONFIG_ACPI_BUS=y
@@ -459,6 +462,7 @@
CONFIG_BLK_DEV_SR=m
# CONFIG_BLK_DEV_SR_VENDOR is not set
CONFIG_CHR_DEV_SG=m
+# CONFIG_CHR_DEV_SCH is not set
#
# Some SCSI devices (e.g. CD jukebox) support multiple LUNs
@@ -493,6 +497,7 @@
# CONFIG_SCSI_ATA_PIIX is not set
CONFIG_SCSI_SATA_NV=m
# CONFIG_SCSI_SATA_PROMISE is not set
+# CONFIG_SCSI_SATA_QSTOR is not set
# CONFIG_SCSI_SATA_SX4 is not set
# CONFIG_SCSI_SATA_SIL is not set
# CONFIG_SCSI_SATA_SIS is not set
@@ -543,6 +548,8 @@
CONFIG_DM_SNAPSHOT=m
CONFIG_DM_MIRROR=m
CONFIG_DM_ZERO=m
+CONFIG_DM_MULTIPATH=m
+CONFIG_DM_MULTIPATH_EMC=m
#
# Fusion MPT device support
@@ -971,6 +978,11 @@
CONFIG_BT_HCIBPA10X=m
CONFIG_BT_HCIBFUSB=m
CONFIG_BT_HCIVHCI=m
+CONFIG_IEEE80211=m
+# CONFIG_IEEE80211_DEBUG is not set
+CONFIG_IEEE80211_CRYPT_WEP=m
+CONFIG_IEEE80211_CRYPT_CCMP=m
+CONFIG_IEEE80211_CRYPT_TKIP=m
CONFIG_NETDEVICES=y
CONFIG_DUMMY=m
CONFIG_BONDING=m
@@ -1263,6 +1275,8 @@
# CONFIG_JOYSTICK_JOYDUMP is not set
CONFIG_INPUT_TOUCHSCREEN=y
CONFIG_TOUCHSCREEN_GUNZE=m
+# CONFIG_TOUCHSCREEN_ELO is not set
+# CONFIG_TOUCHSCREEN_MK712 is not set
CONFIG_INPUT_MISC=y
CONFIG_INPUT_PCSPKR=m
CONFIG_INPUT_UINPUT=m
@@ -1293,6 +1307,7 @@
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
+CONFIG_INOTIFY=y
CONFIG_SERIAL_NONSTANDARD=y
CONFIG_COMPUTONE=m
CONFIG_ROCKETPORT=m
@@ -1370,6 +1385,7 @@
CONFIG_IB700_WDT=m
CONFIG_WAFER_WDT=m
CONFIG_I8XX_TCO=m
+# CONFIG_I6300ESB_WDT is not set
CONFIG_SC1200_WDT=m
CONFIG_SCx200_WDT=m
CONFIG_60XX_WDT=m
@@ -1444,6 +1460,11 @@
CONFIG_HANGCHECK_TIMER=m
#
+# TPM devices
+#
+# CONFIG_TCG_TPM is not set
+
+#
# I2C support
#
CONFIG_I2C=m
@@ -1471,6 +1492,7 @@
CONFIG_I2C_NFORCE2=m
CONFIG_I2C_PARPORT=m
CONFIG_I2C_PARPORT_LIGHT=m
+# CONFIG_I2C_PIIX4 is not set
CONFIG_I2C_PROSAVAGE=m
CONFIG_I2C_SAVAGE4=m
CONFIG_SCx200_ACB=m
@@ -1496,6 +1518,7 @@
CONFIG_SENSORS_FSCHER=m
# CONFIG_SENSORS_FSCPOS is not set
CONFIG_SENSORS_GL518SM=m
+CONFIG_SENSORS_GL520SM=m
CONFIG_SENSORS_IT87=m
# CONFIG_SENSORS_LM63 is not set
CONFIG_SENSORS_LM75=m
@@ -1509,6 +1532,7 @@
CONFIG_SENSORS_MAX1619=m
# CONFIG_SENSORS_PC87360 is not set
# CONFIG_SENSORS_SMSC47B397 is not set
+CONFIG_SENSORS_SIS5595=m
# CONFIG_SENSORS_SMSC47M1 is not set
CONFIG_SENSORS_VIA686A=m
CONFIG_SENSORS_W83781D=m
@@ -1682,6 +1706,10 @@
# Graphics support
#
CONFIG_FB=y
+CONFIG_FB_CFB_FILLRECT=y
+CONFIG_FB_CFB_COPYAREA=y
+CONFIG_FB_CFB_IMAGEBLIT=y
+CONFIG_FB_SOFT_CURSOR=y
CONFIG_FB_MODE_HELPERS=y
# CONFIG_FB_TILEBLITTING is not set
CONFIG_FB_CIRRUS=m
@@ -1695,6 +1723,7 @@
CONFIG_VIDEO_SELECT=y
CONFIG_FB_HGA=m
# CONFIG_FB_HGA_ACCEL is not set
+# CONFIG_FB_NVIDIA is not set
CONFIG_FB_RIVA=m
CONFIG_FB_RIVA_I2C=y
CONFIG_FB_RIVA_DEBUG=y
@@ -1726,6 +1755,7 @@
CONFIG_FB_VOODOO1=m
CONFIG_FB_TRIDENT=m
# CONFIG_FB_TRIDENT_ACCEL is not set
+# CONFIG_FB_GEODE is not set
CONFIG_FB_VIRTUAL=m
#
@@ -2281,6 +2311,7 @@
CONFIG_MAGIC_SYSRQ=y
CONFIG_LOG_BUF_SHIFT=14
CONFIG_DETECT_SOFTLOCKUP=y
+# CONFIG_PRINTK_TIME is not set
# CONFIG_SCHEDSTATS is not set
# CONFIG_DEBUG_SLAB is not set
CONFIG_DEBUG_PREEMPT=y
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Mathieu Segaud
> Helge Hafting <helge....@aitel.hist.no> wrote:
>>
>> This kernel came up, but my boot script complained about no /dev/hdb3
>> when trying to mount /var.
>> (I have two IDE disks on the same cable, and an IDE cdrom on another.)
>> They are usually hda, hdb, and hdc.
>>
>> MAKEDEV hdq did not help. Looking at sysfs, it turns out that
>> /dev/hdq1 is at major:3 minor:1025 if I interpret things right.
>> (/dev/hda1 is at 3:1, which is correct.)
>> These numbers did not work with my mknod, it created 7:1 instead.
>> So I didn't get to test this mysterious device.
>>
>> But I assume this is a mistake of some sort, I haven't heard about any
>> change in the IDE numbering coming up? 2.6.1-rc3-mm1 works as expected.
>>
>> It may be interesting to note that my root raid-1 came up fine,
>> consisting of hdq1 and hda1 instead of the usual hdb1 and hda1.
>
> I don't know what could be causing that. Please send .config. If you set
> CONFIG_BASE_FULL=n, try setting it to `y'.
I've got the same problem here on my box, udev creates hds and hdu
entries when running 2.6.11-rc4-mm1, whereas it creates correctly hdf
et hdh, on other kernels.
here follows .config:
Dmitry Torokhov
> On Wednesday 23 February 2005 17:38, J.A. Magallon wrote:
> >
> > On 02.23, Andrew Morton wrote:
> > >
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
> > >
> > >
> > > - Various fixes and updates all over the place. Things seem to have slowed
> > > down a bit.
> > >
> > > - Last, final, ultimate call: if anyone has patches in here which are 2.6.11
> > > material, please tell me.
> > >
> >
> > Two points:
> >
> > - I lost my keyboard :(. USB, but plugged into PS/2 with an adapter.
>
> Mine too. Details sent in another message...
>
Does i8042.nopnp help?
--
Dmitry
Brice Goglin
>>>+pcmcia-bridge-resource-management-fix.patch
>
> is responsible for this "no resource available" message, because the =
other
> ones relate to other areas.
This line from dmesg-2.6.11-rc4 is no longer present in -rc4-mm1:
PCI: Transparent bridge - 0000:00:1e.0
This is probably due to this patch too, right ?
Was it supposed to changed that ?
lspci -tv says that the PCMCIA bridge whose resources are broken
is behind this no-longer transparent bridge.
-[00]-+-00.0 Intel Corp. 82830 830 Chipset Host Bridge
+-01.0-[01]----00.0 ATI Technologies Inc Radeon Mobility M6 LY
+-1d.0 Intel Corp. 82801CA/CAM USB (Hub #1)
+-1d.1 Intel Corp. 82801CA/CAM USB (Hub #2)
+-1d.2 Intel Corp. 82801CA/CAM USB (Hub #3)
+-1e.0-[02-04]--+-03.0 Texas Instruments PCI1420
| +-03.1 Texas Instruments PCI1420
| +-04.0 Agere Systems (former Lucent Microelectr=
onics) LT WinModem
| +-08.0 Intel Corp. 82801CAM (ICH3) PRO/100 VM (=
KM) Ethernet Controller
| \-09.0 ESS Technology ES1988 Allegro-1
+-1f.0 Intel Corp. 82801CAM ISA Bridge (LPC)
\-1f.1 Intel Corp. 82801CAM IDE U100
Hope this helps.
Brice
Greg KH
>
> ~$ ls -l /sys/block/hds/device
> ../../devices/pci0000:00/0000:00:04.1/ide1/1.1/
>
> /dev/hdq should be /dev/hdd...
>
> ~$ ls -l /proc/ide
> total 4
> lrwxrwxrwx 1 root root 8 f?v 23 23:28 hda -> ide0/hda/
> lrwxrwxrwx 1 root root 8 f?v 23 23:28 hdb -> ide0/hdb/
> lrwxrwxrwx 1 root root 8 f?v 23 23:28 hdc -> ide1/hdc/
> lrwxrwxrwx 1 root root 8 f?v 23 23:28 hdd -> ide1/hdd/
> dr-xr-xr-x 4 root root 0 f?v 23 23:28 ide0/
> dr-xr-xr-x 4 root root 0 f?v 23 23:28 ide1/
> -r--r--r-- 1 root root 0 f?v 23 23:28 via
> ~$ ls -d /sys/block/hd*
> /sys/block/hda/ /sys/block/hdc/ /sys/block/hdq/ /sys/block/hds/
What does /proc/devices show?
thanks,
greg k-h
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
Andrew Morton
>
> > Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
> > missing.
Looking at the IDE update in rc4-mm1:
+void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
+{
+ ide_hwif_t *hwif = drive->hwif;
+ unsigned int unit = drive->select.all & (1 << 4);
+
+ disk->major = hwif->major;
+ disk->first_minor = unit << PARTN_BITS;
+ sprintf(disk->disk_name, "hd%c", 'a' + hwif->index * MAX_DRIVES + unit);
+ disk->queue = drive->queue;
+}
Looks funny.
Could someone try this?
- unsigned int unit = drive->select.all & (1 << 4);
+ unsigned int unit = (drive->select.all >> 4) & 1;
Matt Mackall
> Andrew Morton <ak...@osdl.org> disait derni??rement que :
Are these misnamed and misnumbered devices mountable? If not, can you
mknod device nodes at the proper major:minor location and have them
work?
Seems ->disk_name is getting modified between ide_setup() and
add_disk() somehow, giving us:
hdb: ...
hdq: hdq1 hdq2...
--
Mathematics is the supreme nostalgia of our time.
Andrew Morton
>
> Could someone try this?
Let's turn that into a real patch.
--- 25/drivers/ide/ide-probe.c~ide_init_disk-fix Wed Feb 23 16:24:44 2005
+++ 25-akpm/drivers/ide/ide-probe.c Wed Feb 23 16:24:55 2005
@@ -1269,7 +1269,7 @@ EXPORT_SYMBOL_GPL(ide_unregister_region)
void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
{
ide_hwif_t *hwif = drive->hwif;
- unsigned int unit = drive->select.all & (1 << 4);
+ unsigned int unit = (drive->select.all >> 4) & 1;
disk->major = hwif->major;
disk->first_minor = unit << PARTN_BITS;
_
Fabian Fenaut
> On Wednesday 23 February 2005 18:12, Ed Tomlinson wrote:
>
>> On Wednesday 23 February 2005 17:38, J.A. Magallon wrote:
>>
>>> On 02.23, Andrew Morton wrote:
>>>
>>>> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
>>>>
>>>> - Various fixes and updates all over the place. Things seem to
>>>> have slowed down a bit.
>>>>
>>>> - Last, final, ultimate call: if anyone has patches in here
>>>> which are 2.6.11 material, please tell me.
>>>
>>> Two points:
>>>
>>> - I lost my keyboard :(. USB, but plugged into PS/2 with an
>>> adapter.
>>
>> Mine too. Details sent in another message...
>
> Does i8042.nopnp help?
yes, keyboard is back
Andrew Morton a ecrit le 24.02.2005 00:25:
> Ed Tomlinson <tom...@cam.org> wrote:
>
>> It does not seem to be finding the keyboard at all...
>
> Can you confirm that Linus's tree is OK? You'd best use the patch at
> http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/ to make
> sure you have the latest stuff.
2.6.11-rc4 +
http://www.kernel.org/pub/linux/kernel/v2.5/testing/cset/cset-20050223_2308.txt.gz
is indeed ok :
Feb 24 01:08:23 odie kernel: Kernel command line:
BOOT_IMAGE=2.6.11-rc4-ff ro root=305 hdd=ide-scsi
[...]
Feb 24 01:08:23 odie kernel: input: AT Translated Set 2 keyboard on
isa0060/serio0
Thank you,
Fabian
Ed Tomlinson
> On Wednesday 23 February 2005 18:12, Ed Tomlinson wrote:
> > On Wednesday 23 February 2005 17:38, J.A. Magallon wrote:
> > >
> > > On 02.23, Andrew Morton wrote:
> > > >
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
> > > >
> > > >
> > > > - Various fixes and updates all over the place. Things seem to have slowed
> > > > down a bit.
> > > >
> > > > - Last, final, ultimate call: if anyone has patches in here which are 2.6.11
> > > > material, please tell me.
> > > >
> > >
> > > Two points:
> > >
> > > - I lost my keyboard :(. USB, but plugged into PS/2 with an adapter.
> >
> > Mine too. Details sent in another message...
> >
>
> Does i8042.nopnp help?
Dmitry, Yes it works fine with this kernel parm. I run with hotplug on and udev off.
Andrew, 11-bk is also fine (without the parm).
Thanks
Ed Tomlinson
Matt Mackall
> Steven Cole <elen...@mesatop.com> wrote:
> >
> > > Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
> > > missing.
>
> Looking at the IDE update in rc4-mm1:
>
> +void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
> +{
> + ide_hwif_t *hwif = drive->hwif;
> + unsigned int unit = drive->select.all & (1 << 4);
> +
> + disk->major = hwif->major;
> + disk->first_minor = unit << PARTN_BITS;
> + sprintf(disk->disk_name, "hd%c", 'a' + hwif->index * MAX_DRIVES + unit);
> + disk->queue = drive->queue;
> +}
>
> Looks funny.
>
> Could someone try this?
>
> - unsigned int unit = drive->select.all & (1 << 4);
> + unsigned int unit = (drive->select.all >> 4) & 1;
Apparently there's already an 'hdb' sitting in drive->name, perhaps we
ought to do disk->disk_name = drive->name for the non-devfs case.
--
Mathematics is the supreme nostalgia of our time.
Andrew Morton
>
> Andrew Morton wrote:
> > Steven Cole <elen...@mesatop.com> wrote:
>
> >> I am having trouble getting recent -mm kernels to boot on my test box.
> >> For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
> >>
> >> VFS: Cannot open root device "301" or unknown-block(3,1)
> >> Please append a correct "root=" boot option
> >> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(3,1)
> >>
> [snipped]
> >
> > Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0,
> > then retest.
>
> Yes, that worked.
hmm, OK. Matt, we have a block major enumeration problem. It appears that
base-small-shrink-chrdevs-hash.patch has the same problem which
base-small-shrink-major_names-hash.patch had.
> 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be missing.
>
> [root@spc1 steven]# uname -r
> 2.6.11-rc4-mm1-GX110
> [root@spc1 steven]# mount -t reiser4 /dev/hdb1 /reiser4_testing
> mount: special device /dev/hdb1 does not exist
It would seem that your /dev/hdb1 block-special device node isn't present.
Try `mknod /dev/hdb1 3 65'.
> hdb: max request size: 128KiB
> hdb: 39102336 sectors (20020 MB) w/2048KiB Cache, CHS=38792/16/63, UDMA(66)
> hdb: cache flushes not supported
> /dev/ide/host0/bus0/target1/lun0: p1
We found a partition.
Matt Mackall
> Andrew Morton wrote:
> >Steven Cole <elen...@mesatop.com> wrote:
>
> >>I am having trouble getting recent -mm kernels to boot on my test box.
> >>For 2.6.11-rc3-mm2 and 2.6.11-rc4-mm1 I get the following:
> >>
> >>VFS: Cannot open root device "301" or unknown-block(3,1)
> >>Please append a correct "root=" boot option
> >>Kernel panic - not syncing: VFS: Unable to mount root fs on
> >>unknown-block(3,1)
> >>
> [snipped]
> >
> >Please set CONFIG_BASE_FULL=y. Check that this causes CONFIG_BASE_SMALL=0,
> >then retest.
>
> Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
> missing.
Can you retry CONFIG_BASE_FULL=n with Andrew's patch?
You may need to boot back into a sane kernel for LILO to operate properly.
--- 25/drivers/ide/ide-probe.c~ide_init_disk-fix Wed Feb 23 16:24:44 2005
+++ 25-akpm/drivers/ide/ide-probe.c Wed Feb 23 16:24:55 2005
@@ -1269,7 +1269,7 @@ EXPORT_SYMBOL_GPL(ide_unregister_region)
void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
{
ide_hwif_t *hwif = drive->hwif;
- unsigned int unit = drive->select.all & (1 << 4);
+ unsigned int unit = (drive->select.all >> 4) & 1;
disk->major = hwif->major;
disk->first_minor = unit << PARTN_BITS;
--
Mathematics is the supreme nostalgia of our time.
Benoit Boissinot
> On Wed, Feb 23, 2005 at 04:16:53PM -0800, Andrew Morton wrote:
> > Steven Cole <elen...@mesatop.com> wrote:
> > >
> > > > Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
> > > > missing.
> >
> > Looking at the IDE update in rc4-mm1:
> >
> > +void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
> > +{
> > + ide_hwif_t *hwif = drive->hwif;
> > + unsigned int unit = drive->select.all & (1 << 4);
> > +
If i grep in the tree, for select.all, it looks like from the initialization
that you can not recover the unit from select.all (ide.c line 235 and 1882)
since the function used is not invertible.
> >
> > Could someone try this?
> >
> > - unsigned int unit = drive->select.all & (1 << 4);
> > + unsigned int unit = (drive->select.all >> 4) & 1;
>
> Apparently there's already an 'hdb' sitting in drive->name, perhaps we
> ought to do disk->disk_name = drive->name for the non-devfs case.
>
init_hwif_default initialized it right.
Could something like this work ?
regards,
Benoit
Matt Mackall
> On Wed, 23 Feb 2005 16:41:59 -0800, Matt Mackall <m...@selenic.com> wrote:
> > On Wed, Feb 23, 2005 at 04:16:53PM -0800, Andrew Morton wrote:
> > > Steven Cole <elen...@mesatop.com> wrote:
> > > >
> > > > > Yes, that worked. 2.6.11-rc4-mm1 now boots OK, but hdb1 seems to be
> > > > > missing.
> > >
> > > Looking at the IDE update in rc4-mm1:
> > >
> > > +void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
> > > +{
> > > + ide_hwif_t *hwif = drive->hwif;
> > > + unsigned int unit = drive->select.all & (1 << 4);
> > > +
>
> If i grep in the tree, for select.all, it looks like from the initialization
> that you can not recover the unit from select.all (ide.c line 235 and 1882)
> since the function used is not invertible.
They're fine, if a bit ugly. Unit is either 0 or 1. So:
(unit<<4) | 0xa0
is equivalent to unit * 16 as the mask won't mask off any bits.
> > >
> > > Could someone try this?
> > >
> > > - unsigned int unit = drive->select.all & (1 << 4);
> > > + unsigned int unit = (drive->select.all >> 4) & 1;
> >
> > Apparently there's already an 'hdb' sitting in drive->name, perhaps we
> > ought to do disk->disk_name = drive->name for the non-devfs case.
> >
> init_hwif_default initialized it right.
>
> Could something like this work ?
No, because they're arrays and not pointers. I've booted with the
obvious strcpy, works fine.
Adrian Bunk
>...
> Changes since 2.6.11-rc3-mm1:
>...
> bk-driver-core-infiniband-build-fix.patch
>...
This gives me the following compile error:
<-- snip -->
...
CC drivers/infiniband/core/user_mad.o
drivers/infiniband/core/user_mad.c:587: warning: 'class_device_attr_dev' defined but not used
...
<-- snip -->
Reverting this patch fixes the warning (but I don't know about the
underlying issues).
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
Adrian Bunk
>...
> Changes since 2.6.11-rc3-mm1:
>...
>...
> More DM updates
>...
This causes the following compile warnings:
<-- snip -->
...
CC drivers/md/dm-hw-handler.o
drivers/md/dm-hw-handler.c: In function `dm_scsi_err_handler':
drivers/md/dm-hw-handler.c:154: warning: unused variable `sense_key'
drivers/md/dm-hw-handler.c:154: warning: unused variable `asc'
drivers/md/dm-hw-handler.c:154: warning: unused variable `ascq'
...
<-- snip -->
Trivial fix:
<-- snip -->
Signed-off-by: Adrian Bunk <bu...@stusta.de>
--- linux-2.6.11-rc4-mm1-full/drivers/md/dm-hw-handler.c.old 2005-02-24 01:59:45.000000000 +0100
+++ linux-2.6.11-rc4-mm1-full/drivers/md/dm-hw-handler.c 2005-02-24 02:00:05.000000000 +0100
@@ -151,9 +151,9 @@
unsigned dm_scsi_err_handler(struct hw_handler *hwh, struct bio *bio)
{
+#if 0
int sense_key, asc, ascq;
-#if 0
if (bio->bi_error & BIO_SENSE) {
/* FIXME: This is just an initial guess. */
/* key / asc / ascq */
Bartlomiej Zolnierkiewicz
> Andrew Morton <ak...@osdl.org> wrote:
> >
> > Could someone try this?
>
> Let's turn that into a real patch.
>
> --- 25/drivers/ide/ide-probe.c~ide_init_disk-fix Wed Feb 23 16:24:44 2005
> +++ 25-akpm/drivers/ide/ide-probe.c Wed Feb 23 16:24:55 2005
> @@ -1269,7 +1269,7 @@ EXPORT_SYMBOL_GPL(ide_unregister_region)
> void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
> {
> ide_hwif_t *hwif = drive->hwif;
> - unsigned int unit = drive->select.all & (1 << 4);
> + unsigned int unit = (drive->select.all >> 4) & 1;
>
> disk->major = hwif->major;
> disk->first_minor = unit << PARTN_BITS;
thanks Andrew
fscking bitfields hopefully viro will kill them soon
Steven Cole
Andrew's above patch fixes the hdb->hdq insanity, but I still need
CONFIG_BASE_FULL=y. I tried unsetting CONFIG_BASE_FULL, and again
got the "VFS: Cannot open root device" message (with akpm's patch).
Steven
Steven Cole
Andrew's above patch fixes the hdb->hdq insanity, but I still need
CONFIG_BASE_FULL=y. I tried unsetting CONFIG_BASE_FULL, and again
got the "VFS: Cannot open root device" message (with akpm's patch).
Steven
-
Laurent Riffard
Le 24.02.2005 00:20, Andrew Morton a écrit :
> Laurent Riffard <laurent...@free.fr> wrote:
>
>>Le 23.02.2005 21:12, Andrew Morton a écrit :
>>
>>>Helge Hafting <helge....@aitel.hist.no> wrote:
>>>
>>>
>>>>when trying to mount /var.
>>>>They are usually hda, hdb, and hdc.
>>>>
>>>>MAKEDEV hdq did not help. Looking at sysfs, it turns out that
>>>>/dev/hdq1 is at major:3 minor:1025 if I interpret things right.
>>>>(/dev/hda1 is at 3:1, which is correct.)
>>>>These numbers did not work with my mknod, it created 7:1 instead.
>>>>So I didn't get to test this mysterious device.
>>>>
>>>>change in the IDE numbering coming up? 2.6.1-rc3-mm1 works as expected.
>>>>
>>>>It may be interesting to note that my root raid-1 came up fine,
>>>>consisting of hdq1 and hda1 instead of the usual hdb1 and hda1.
>>>
>>>
>>>CONFIG_BASE_FULL=n, try setting it to `y'.
>>>
>>
>>this is just a "me too"...
>
>
> CONFIG_BASE_FULL=y?
>
yes, I do.
--
laurent
Laurent Riffard
Le 24.02.2005 00:47, Greg KH a écrit :
> On Wed, Feb 23, 2005 at 11:36:50PM +0100, Laurent Riffard wrote:
>
>>hey, what's this /dev/hds ? digging into /sys/block...
>>
>>~$ ls -l /sys/block/hds/device
>>lrwxrwxrwx 1 root root 0 f?v 23 22:45 /sys/block/hds/device ->
>>../../devices/pci0000:00/0000:00:04.1/ide1/1.1/
>>
>>/dev/hdq should be /dev/hdd...
>>
>>~$ ls -l /proc/ide
>>total 4
>>-r--r--r-- 1 root root 0 f?v 23 23:28 drivers
>>lrwxrwxrwx 1 root root 8 f?v 23 23:28 hda -> ide0/hda/
>>lrwxrwxrwx 1 root root 8 f?v 23 23:28 hdb -> ide0/hdb/
>>lrwxrwxrwx 1 root root 8 f?v 23 23:28 hdc -> ide1/hdc/
>>lrwxrwxrwx 1 root root 8 f?v 23 23:28 hdd -> ide1/hdd/
>>dr-xr-xr-x 4 root root 0 f?v 23 23:28 ide0/
>>dr-xr-xr-x 4 root root 0 f?v 23 23:28 ide1/
>>-r--r--r-- 1 root root 0 f?v 23 23:28 via
>>~$ ls -d /sys/block/hd*
>>/sys/block/hda/ /sys/block/hdc/ /sys/block/hdq/ /sys/block/hds/
>
>
> What does /proc/devices show?
Character devices:
1 mem
4 /dev/vc/0
4 tty
5 /dev/tty
5 /dev/console
5 /dev/ptmx
6 lp
7 vcs
10 misc
13 input
14 sound
29 fb
116 alsa
128 ptm
136 pts
171 ieee1394
180 usb
Block devices:
1 ramdisk
2 fd
3 ide0
7 loop
22 ide1
253 pktcdvd
254 device-mapper
Do you see something strange here ?
--
laurent
Greg KH
>
>
> Le 24.02.2005 00:47, Greg KH a ?crit :
No, ide0 is 3 and ide1 is 22, which is "standard". Hm, what's that
pktcdvd and device-mapper doing there? Do you need those drivers? Can
you try it without building them and see if that helps?
thanks,
greg k-h
Laurent Riffard
I do need device-mapper, since I put /usr and /var on LVM filesystems. I
use ptkcdvd to copy data to CD-RW. I can remove this one.
Anyway, this patch from Andrew fixed the problem :
http://lkml.org/lkml/2005/2/23/214.
So I won't try to remove pktcdvd and device-mapper driver (except if you
_really_ want me to do so).
Thanks for your interest.
--
laurent
Adrian Bunk
But the suggestion in the help text is IMHO too strong and therefore
removed by this patch.
Signed-off-by: Adrian Bunk <bu...@stusta.de>
--- linux-2.6.11-rc4-mm1-full/arch/i386/Kconfig.old 2005-02-24 22:47:32.000000000 +0100
+++ linux-2.6.11-rc4-mm1-full/arch/i386/Kconfig 2005-02-24 22:48:11.000000000 +0100
@@ -903,8 +903,6 @@
and the task is only allowed to execute a few safe syscalls
defined by each seccomp mode.
- If unsure, say Y. Only embedded should say N here.
-
source "drivers/perfctr/Kconfig"
config PHYSICAL_START
Andrea Arcangeli
On Thu, Feb 24, 2005 at 10:51:36PM +0100, Adrian Bunk wrote:
> seccomp might be a nice feature under some circumstances.
> But the suggestion in the help text is IMHO too strong and therefore
> removed by this patch.
Why too strong? The reason there is a config option is for the embedded
space, where clearly they want to compile into the kernel only the
strict features they use.
There are no risks in enabling seccomp and the size of the kernel image
won't change in any significant way either.
So I'd prefer to keep the "If unsure, say Y." and it seems appropriate
to me.
You have to say Y, if later on you want to sell your CPU resources with
Cpushare. BTW, you can already test it if you download version 0.8 of
the LGPL'd Cpushare software, it'll connect to the server and it'll
execute a remote seccomp computation and then it'll hang around until
you stop it with ./stop_cpushare.sh (and you will see your client
connected in the homepage stats). I didn't finish writing all the code
yet but it's already a decent demo for the seccomp part at least.
Anyway the help text is a minor detail after all. Thanks to everyone who
helped and provided feedback about the seccomp patch, especially to
Andrew. I'm very glad to see it in -mm right now!
Greg KH
> I do need device-mapper, since I put /usr and /var on LVM filesystems. I
> use ptkcdvd to copy data to CD-RW. I can remove this one.
>
> Anyway, this patch from Andrew fixed the problem :
> http://lkml.org/lkml/2005/2/23/214.
Yeah, it's not in my code! :)
> So I won't try to remove pktcdvd and device-mapper driver (except if you
> _really_ want me to do so).
Nope, as long as the above patch works for you, I'm happy.
thanks,
greg k-h
J.A. Magallon
On 02.24, Dmitry Torokhov wrote:
> On Wednesday 23 February 2005 18:12, Ed Tomlinson wrote:
> > On Wednesday 23 February 2005 17:38, J.A. Magallon wrote:
> > >
> > > On 02.23, Andrew Morton wrote:
> > > >
> > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
> > > >
> > > >
> > > > - Various fixes and updates all over the place. Things seem to have slowed
> > > > down a bit.
> > > >
> > > > - Last, final, ultimate call: if anyone has patches in here which are 2.6.11
> > > > material, please tell me.
> > > >
> > >
> > > Two points:
> > >
> > > - I lost my keyboard :(. USB, but plugged into PS/2 with an adapter.
> >
> > Mine too. Details sent in another message...
> >
>
> Does i8042.nopnp help?
>
Yes, that makes things work.
Even better than ever before, now an USB mouse and a PS/2 logitech
trackball work fine both at the same time. In console and in X.
In previous kernels PS/2 was dead or jumped heavily when an usb mouse
was plugged. The keyboard works both in PS/2 (with adapter) and in USB.
Now a tricky question: the mouse and the trackball move the pointer in X
at different speeds. Is there any way to tell the kernel they have
the same DPI ? Or can I tweak the speed/DPI settings for them separately
to get a more or less similar movement ?
TIA
--
J.A. Magallon <jamagallon()able!es> \ Software is like sex:
werewolf!able!es \ It's better when it's free
Mandrakelinux release 10.2 (Cooker) for i586
Linux 2.6.10-jam11 (gcc 3.4.3 (Mandrakelinux 10.2 3.4.3-3mdk)) #1
Felipe Alfaro Solana
> >
> > Could someone try this?
>
> Let's turn that into a real patch.
>
> --- 25/drivers/ide/ide-probe.c~ide_init_disk-fix Wed Feb 23 16:24:44 2005
> +++ 25-akpm/drivers/ide/ide-probe.c Wed Feb 23 16:24:55 2005
> @@ -1269,7 +1269,7 @@ EXPORT_SYMBOL_GPL(ide_unregister_region)
> void ide_init_disk(struct gendisk *disk, ide_drive_t *drive)
> {
> ide_hwif_t *hwif = drive->hwif;
> - unsigned int unit = drive->select.all & (1 << 4);
> + unsigned int unit = (drive->select.all >> 4) & 1;
>
> disk->major = hwif->major;
> disk->first_minor = unit << PARTN_BITS;
> _
>
> -
Works for me.
Thanks.
Dmitry Torokhov
>
> On 02.24, Dmitry Torokhov wrote:
> > On Wednesday 23 February 2005 18:12, Ed Tomlinson wrote:
> > > On Wednesday 23 February 2005 17:38, J.A. Magallon wrote:
> > > >
> > > > On 02.23, Andrew Morton wrote:
> > > > >
> > > > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.11-rc4/2.6.11-rc4-mm1/
> > > > >
> > > > >
> > > > > - Various fixes and updates all over the place. Things seem to have slowed
> > > > > down a bit.
> > > > >
> > > > > - Last, final, ultimate call: if anyone has patches in here which are 2.6.11
> > > > > material, please tell me.
> > > > >
> > > >
> > > > Two points:
> > > >
> > > > - I lost my keyboard :(. USB, but plugged into PS/2 with an adapter.
> > >
> > > Mine too. Details sent in another message...
> > >
> >
> > Does i8042.nopnp help?
> >
>
> Yes, that makes things work.
> Even better than ever before, now an USB mouse and a PS/2 logitech
> trackball work fine both at the same time. In console and in X.
> In previous kernels PS/2 was dead or jumped heavily when an usb mouse
> was plugged. The keyboard works both in PS/2 (with adapter) and in USB.
>
> Now a tricky question: the mouse and the trackball move the pointer in X
> at different speeds. Is there any way to tell the kernel they have
> the same DPI ? Or can I tweak the speed/DPI settings for them separately
> to get a more or less similar movement ?
>
You can try changing PS/2 mouse rate and resolution via the following
sysfs attributes:
/sys/bus/serio/devices/serioX/rate
/sys/bus/serio/devices/serioX/resolution
like this:
echo -n "200" > /sys/bus/serio/devices/serio1/resolution
Or you could try setting both mice as separate devices in X...
--
Dmitry
Adrian Bunk
> Hello Adrian,
Hi Andrea,
> On Thu, Feb 24, 2005 at 10:51:36PM +0100, Adrian Bunk wrote:
> > seccomp might be a nice feature under some circumstances.
> > But the suggestion in the help text is IMHO too strong and therefore
> > removed by this patch.
>
> Why too strong? The reason there is a config option is for the embedded
> space, where clearly they want to compile into the kernel only the
> strict features they use.
>
> There are no risks in enabling seccomp and the size of the kernel image
> won't change in any significant way either.
>
> So I'd prefer to keep the "If unsure, say Y." and it seems appropriate
> to me.
>
> You have to say Y, if later on you want to sell your CPU resources with
> Cpushare. BTW, you can already test it if you download version 0.8 of
> the LGPL'd Cpushare software, it'll connect to the server and it'll
> execute a remote seccomp computation and then it'll hang around until
> you stop it with ./stop_cpushare.sh (and you will see your client
> connected in the homepage stats). I didn't finish writing all the code
> yet but it's already a decent demo for the seccomp part at least.
>...
this sounds more like an "If unsure, say N.":
You don't need this feature unless you know you need it.
It's not about risk or the actual size of the code - there are many
small or big features in the kernel that might be useful under some
circumstances, but even the IPv6 help text still suggests to say N
to IPv6.
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
-
Andrea Arcangeli
> You don't need this feature unless you know you need it.
But you may not know that you need it since in the help text I
intentionally didn't mention which software requires the option to be
set to Y (I didn't mention it, since I didn't want to use the kernel
configuration help text to get free advertisement, but OTOH if people is
unsure while they configure the kernel I certainly prefer that they set
it to Y ;).
> It's not about risk or the actual size of the code - there are many
> small or big features in the kernel that might be useful under some
> circumstances, but even the IPv6 help text still suggests to say N
> to IPv6.
IPV6 is some relevant amount of code and complexity, seccomp is only a
few bytes and very simple, it's not even a kbyte of ram that you're
paying if you enable it. Only embedded cares about bytes, and that's why
the option exists for embedded.
One thing I'm concerned about (more than the "Y" in the help text) is
that the distributions will enable the option in their binary kernel
images. I hope they will given it's only a matter of a few bytes.
Thanks.
Adrian Bunk
>...
> Changes since 2.6.11-rc3-mm1:
>...
>...
Some of the options that needlessly wrote in their help text which
options they do selct (patch already sent) didn't obey the most
important rule of select
If you select something, you have to ensure that the dependencies
of what you do select are fulfilled.
resulting in the following compile error:
<-- snip -->
...
LD .tmp_vmlinux1
crypto/built-in.o(.init.text+0x31b): In function `aes_init':
: undefined reference to `crypto_register_alg'
crypto/built-in.o(.init.text+0x326): In function `michael_mic_init':
: undefined reference to `crypto_register_alg'
crypto/built-in.o(.exit.text+0x6): In function `aes_fini':
: undefined reference to `crypto_unregister_alg'
crypto/built-in.o(.exit.text+0x16): In function `michael_mic_exit':
: undefined reference to `crypto_unregister_alg'
net/built-in.o(.text+0x5ba52): In function `ieee80211_ccmp_init':
: undefined reference to `crypto_alloc_tfm'
net/built-in.o(.text+0x5ba94): In function `ieee80211_ccmp_init':
: undefined reference to `crypto_free_tfm'
net/built-in.o(.text+0x5bab7): In function `ieee80211_ccmp_deinit':
: undefined reference to `crypto_free_tfm'
net/built-in.o(.text+0x5c5c2): In function `ieee80211_tkip_init':
: undefined reference to `crypto_alloc_tfm'
net/built-in.o(.text+0x5c5d5): In function `ieee80211_tkip_init':
: undefined reference to `crypto_alloc_tfm'
net/built-in.o(.text+0x5c623): In function `ieee80211_tkip_init':
: undefined reference to `crypto_free_tfm'
net/built-in.o(.text+0x5c62a): In function `ieee80211_tkip_init':
: undefined reference to `crypto_free_tfm'
net/built-in.o(.text+0x5c65e): In function `ieee80211_tkip_deinit':
: undefined reference to `crypto_free_tfm'
net/built-in.o(.text+0x5c665): In function `ieee80211_tkip_deinit':
: undefined reference to `crypto_free_tfm'
make: *** [.tmp_vmlinux1] Error 1
<-- snip -->
This patch adds the missing selects of CRYPTO.
--- linux-2.6.11-rc4-mm1-full/net/ieee80211/Kconfig.old 2005-02-26 12:12:44.000000000 +0100
+++ linux-2.6.11-rc4-mm1-full/net/ieee80211/Kconfig 2005-02-26 12:13:47.000000000 +0100
@@ -42,10 +42,11 @@
"ieee80211_crypt_wep".
config IEEE80211_CRYPT_CCMP
tristate "IEEE 802.11i CCMP support"
depends on IEEE80211
+ select CRYPTO
select CRYPTO_AES
---help---
Include software based cipher suites in support of IEEE 802.11i
(aka TGi, WPA, WPA2, WPA-PSK, etc.) for use with CCMP enabled
networks.
@@ -54,10 +55,11 @@
"ieee80211_crypt_ccmp".
config IEEE80211_CRYPT_TKIP
tristate "IEEE 802.11i TKIP encryption"
depends on IEEE80211
+ select CRYPTO
select CRYPTO_MICHAEL_MIC
---help---
Include software based cipher suites in support of IEEE 802.11i
(aka TGi, WPA, WPA2, WPA-PSK, etc.) for use with TKIP enabled
networks.
Adrian Bunk
>...
> Changes since 2.6.11-rc3-mm1:
>...
>
> New RAID driver (this patch is having a hard life and needs a re-review)
>...
This patch contains the following cleanups:
- make needlessly global functions static
- move arcmsr_scsi_host_template from arcmsr.h to arcmsr.c
(code doesn't belong into header files)
Signed-off-by: Adrian Bunk <bu...@stusta.de>
---
Some notes:
- BOOLEAN/TRUE/FALSE, own get_min/get_max aren't kernel coding style
- the own subdirectory for this driver seems to be overkill
- aren't the "if defined(__x86_64__)" wrong for other 64bit
architectures?
drivers/scsi/arcmsr/arcmsr.c | 110 +++++++++++++++++++++++------------
drivers/scsi/arcmsr/arcmsr.h | 34 ----------
2 files changed, 73 insertions(+), 71 deletions(-)
--- linux-2.6.11-rc4-mm1-full/drivers/scsi/arcmsr/arcmsr.h.old 2005-02-27 16:06:56.000000000 +0100
+++ linux-2.6.11-rc4-mm1-full/drivers/scsi/arcmsr/arcmsr.h 2005-02-27 16:06:25.000000000 +0100
@@ -4802,38 +4802,4 @@
** (E) Checksum : checksum of length and status or data byte
**************************************************************************
*/
-extern int arcmsr_proc_info(struct Scsi_Host *host, char *buffer, char **start,
- off_t offset, int length, int inout);
-extern int arcmsr_bios_param(struct scsi_device *sdev,
- struct block_device *bdev, sector_t capacity,
- int *info);
-extern int arcmsr_release(struct Scsi_Host *);
-extern int arcmsr_queue_command(Scsi_Cmnd * cmd, void (*done) (Scsi_Cmnd *));
-extern int arcmsr_cmd_abort(Scsi_Cmnd *);
-extern int arcmsr_bus_reset(Scsi_Cmnd *);
-extern int arcmsr_ioctl(Scsi_Device * dev, int ioctl_cmd, void *arg);
-extern const char *arcmsr_info(struct Scsi_Host *);
-static Scsi_Host_Template arcmsr_scsi_host_template = {
- .module = THIS_MODULE,
- .proc_name = "arcmsr",
- .proc_info = arcmsr_proc_info,
- .name = "ARCMSR ARECA SATA RAID HOST Adapter" ARCMSR_DRIVER_VERSION, /* *name */
- .release = arcmsr_release,
- .info = arcmsr_info,
- .ioctl = arcmsr_ioctl,
- .queuecommand = arcmsr_queue_command,
- .eh_strategy_handler = NULL,
- .eh_abort_handler = arcmsr_cmd_abort,
- .eh_device_reset_handler = NULL,
- .eh_bus_reset_handler = arcmsr_bus_reset,
- .eh_host_reset_handler = NULL,
- .bios_param = arcmsr_bios_param,
- .can_queue = ARCMSR_MAX_OUTSTANDING_CMD,
- .this_id = ARCMSR_SCSI_INITIATOR_ID,
- .sg_tablesize = ARCMSR_MAX_SG_ENTRIES,
- .max_sectors = ARCMSR_MAX_XFER_SECTORS,
- .cmd_per_lun = ARCMSR_MAX_CMD_PERLUN,
- .unchecked_isa_dma = 0,
- .use_clustering = DISABLE_CLUSTERING,
-};
--- linux-2.6.11-rc4-mm1-full/drivers/scsi/arcmsr/arcmsr.c.old 2005-02-27 16:06:52.000000000 +0100
+++ linux-2.6.11-rc4-mm1-full/drivers/scsi/arcmsr/arcmsr.c 2005-02-27 16:06:25.000000000 +0100
@@ -121,15 +121,26 @@
static int arcmsr_halt_notify(struct notifier_block *nb, unsigned long event,
void *buf);
static void arcmsr_free_pci_pool(PACB pACB);
-void arcmsr_pcidev_disattach(PACB pACB);
-BOOLEAN arcmsr_wait_msgint_ready(PACB pACB);
-void arcmsr_iop_init(PACB pACB);
-int arcmsr_iop_ioctlcmd(PACB pACB, int ioctl_cmd, void *arg);
-int arcmsr_initialize(PACB pACB, struct pci_dev *pPCI_DEV);
+static void arcmsr_pcidev_disattach(PACB pACB);
+static void arcmsr_iop_init(PACB pACB);
+static int arcmsr_iop_ioctlcmd(PACB pACB, int ioctl_cmd, void *arg);
+static int arcmsr_initialize(PACB pACB, struct pci_dev *pPCI_DEV);
static irqreturn_t arcmsr_HwInterrupt(PACB pACB);
static int arcmsr_device_probe(struct pci_dev *pPCI_DEV,
const struct pci_device_id *id);
static void arcmsr_device_remove(struct pci_dev *pPCI_DEV);
+static int arcmsr_bios_param(struct scsi_device *sdev,
+ struct block_device *bdev,
+ sector_t capacity, int *geom);
+static int arcmsr_bus_reset(Scsi_Cmnd * cmd);
+static int arcmsr_cmd_abort(Scsi_Cmnd * cmd);
+static const char *arcmsr_info(struct Scsi_Host *host);
+static int arcmsr_ioctl(Scsi_Device * dev, int ioctl_cmd, void *arg);
+static int arcmsr_proc_info(struct Scsi_Host *host, char *buffer, char **start,
+ off_t offset, int length, int inout);
+static int arcmsr_queue_command(Scsi_Cmnd * cmd, void (*done) (Scsi_Cmnd *));
+static int arcmsr_release(struct Scsi_Host *host);
+
/*
**********************************************************************************
**
@@ -169,13 +180,37 @@
};
MODULE_DEVICE_TABLE(pci, arcmsr_device_id_table);
-struct pci_driver arcmsr_pci_driver = {
+static struct pci_driver arcmsr_pci_driver = {
.name = "arcmsr",
.id_table = arcmsr_device_id_table,
.probe = arcmsr_device_probe,
.remove = arcmsr_device_remove,
};
+static Scsi_Host_Template arcmsr_scsi_host_template = {
+ .module = THIS_MODULE,
+ .proc_name = "arcmsr",
+ .proc_info = arcmsr_proc_info,
+ .name = "ARCMSR ARECA SATA RAID HOST Adapter" ARCMSR_DRIVER_VERSION, /* *name */
+ .release = arcmsr_release,
+ .info = arcmsr_info,
+ .ioctl = arcmsr_ioctl,
+ .queuecommand = arcmsr_queue_command,
+ .eh_strategy_handler = NULL,
+ .eh_abort_handler = arcmsr_cmd_abort,
+ .eh_device_reset_handler = NULL,
+ .eh_bus_reset_handler = arcmsr_bus_reset,
+ .eh_host_reset_handler = NULL,
+ .bios_param = arcmsr_bios_param,
+ .can_queue = ARCMSR_MAX_OUTSTANDING_CMD,
+ .this_id = ARCMSR_SCSI_INITIATOR_ID,
+ .sg_tablesize = ARCMSR_MAX_SG_ENTRIES,
+ .max_sectors = ARCMSR_MAX_XFER_SECTORS,
+ .cmd_per_lun = ARCMSR_MAX_CMD_PERLUN,
+ .unchecked_isa_dma = 0,
+ .use_clustering = DISABLE_CLUSTERING,
+};
+
/*
*********************************************************************
*********************************************************************
@@ -213,8 +248,9 @@
*********************************************************************
*********************************************************************
*/
-int arcmsr_bios_param(struct scsi_device *sdev, struct block_device *bdev,
- sector_t capacity, int *geom)
+static int arcmsr_bios_param(struct scsi_device *sdev,
+ struct block_device *bdev,
+ sector_t capacity, int *geom)
{
int heads, sectors, cylinders, total_capacity;
@@ -409,7 +445,7 @@
**
**********************************************************************
*/
-void arcmsr_pci_unmap_dma(PCCB pCCB)
+static void arcmsr_pci_unmap_dma(PCCB pCCB)
{
PACB pACB = pCCB->pACB;
Scsi_Cmnd *pcmd = pCCB->pcmd;
@@ -528,7 +564,7 @@
**
**********************************************************************
*/
-void arcmsr_cmd_done(Scsi_Cmnd * pcmd)
+static void arcmsr_cmd_done(Scsi_Cmnd * pcmd)
{
pcmd->scsi_done(pcmd);
return;
@@ -540,7 +576,7 @@
**
************************************************************************
*/
-void arcmsr_flush_adapter_cache(PACB pACB)
+static void arcmsr_flush_adapter_cache(PACB pACB)
{
#if ARCMSR_DEBUG0
printk("arcmsr_flush_adapter_cache..............\n");
@@ -557,7 +593,7 @@
**
**********************************************************************
*/
-void arcmsr_ccb_complete(PCCB pCCB)
+static void arcmsr_ccb_complete(PCCB pCCB)
{
unsigned long flag;
PACB pACB = pCCB->pACB;
@@ -586,7 +622,7 @@
** if scsi error do auto request sense
**********************************************************************
*/
-void arcmsr_report_SenseInfoBuffer(PCCB pCCB)
+static void arcmsr_report_SenseInfoBuffer(PCCB pCCB)
{
Scsi_Cmnd *pcmd = pCCB->pcmd;
PSENSE_DATA psenseBuffer = (PSENSE_DATA) pcmd->sense_buffer;
@@ -611,7 +647,7 @@
** to insert pCCB into tail of pACB wait exec ccbQ
*********************************************************************
*/
-void arcmsr_queue_wait2go_ccb(PACB pACB, PCCB pCCB)
+static void arcmsr_queue_wait2go_ccb(PACB pACB, PCCB pCCB)
{
unsigned long flag;
int i = 0;
@@ -639,7 +675,7 @@
**
*********************************************************************
*/
-void arcmsr_abort_allcmd(PACB pACB)
+static void arcmsr_abort_allcmd(PACB pACB)
{
CHIP_REG_WRITE32(&pACB->pmu->inbound_msgaddr0,
ARCMSR_INBOUND_MESG0_ABORT_CMD);
@@ -653,7 +689,7 @@
**
**********************************************************************
*/
-BOOLEAN arcmsr_wait_msgint_ready(PACB pACB)
+static BOOLEAN arcmsr_wait_msgint_ready(PACB pACB)
{
uint32_t Index;
uint8_t Retries = 0x00;
@@ -678,7 +714,7 @@
** Return Value: Nothing.
****************************************************************************
*/
-void arcmsr_iop_reset(PACB pACB)
+static void arcmsr_iop_reset(PACB pACB)
{
PCCB pCCB;
uint32_t intmask_org, mask;
@@ -760,7 +796,7 @@
** PAGE_SIZE=4096 or 8192,PAGE_SHIFT=12
**********************************************************************
*/
-void arcmsr_build_ccb(PACB pACB, PCCB pCCB, Scsi_Cmnd * pcmd)
+static void arcmsr_build_ccb(PACB pACB, PCCB pCCB, Scsi_Cmnd * pcmd)
{
PARCMSR_CDB pARCMSR_CDB = (PARCMSR_CDB) & pCCB->arcmsr_cdb;
int8_t *psge = (int8_t *) & pARCMSR_CDB->u;
@@ -931,7 +967,7 @@
**
**************************************************************************
*/
-void arcmsr_post_wait2go_ccb(PACB pACB)
+static void arcmsr_post_wait2go_ccb(PACB pACB)
{
unsigned long flag;
PCCB pCCB;
@@ -965,7 +1001,7 @@
** Output:
**********************************************************************
*/
-void arcmsr_post_Qbuffer(PACB pACB)
+static void arcmsr_post_Qbuffer(PACB pACB)
{
uint8_t *pQbuffer;
PQBUFFER pwbuffer = (PQBUFFER) & pACB->pmu->ioctl_wbuffer;
@@ -996,7 +1032,7 @@
**
************************************************************************
*/
-void arcmsr_stop_adapter_bgrb(PACB pACB)
+static void arcmsr_stop_adapter_bgrb(PACB pACB)
{
#if ARCMSR_DEBUG0
printk("arcmsr_stop_adapter_bgrb..............\n");
@@ -1271,7 +1307,7 @@
**
************************************************************************
*/
-int arcmsr_iop_ioctlcmd(PACB pACB, int ioctl_cmd, void *arg)
+static int arcmsr_iop_ioctlcmd(PACB pACB, int ioctl_cmd, void *arg)
{
CMD_IOCTL_FIELD cmdioctlfld;
PCMD_IOCTL_FIELD pcmdioctlfld = &cmdioctlfld;
@@ -1617,7 +1653,7 @@
**
************************************************************************
*/
-int arcmsr_ioctl(Scsi_Device * dev, int ioctl_cmd, void *arg)
+static int arcmsr_ioctl(Scsi_Device * dev, int ioctl_cmd, void *arg)
{
PACB pACB;
int32_t match = 0x55AA, i;
@@ -1649,7 +1685,7 @@
**
**************************************************************************
*/
-PCCB arcmsr_get_freeccb(PACB pACB)
+static PCCB arcmsr_get_freeccb(PACB pACB)
{
PCCB pCCB;
unsigned long flag;
@@ -1821,7 +1857,7 @@
**} Scsi_Pointer;
***********************************************************************
*/
-int arcmsr_queue_command(Scsi_Cmnd * cmd, void (*done) (Scsi_Cmnd *))
+static int arcmsr_queue_command(Scsi_Cmnd * cmd, void (*done) (Scsi_Cmnd *))
{
struct Scsi_Host *host = cmd->device->host;
PACB pACB = (PACB) host->hostdata;
@@ -1872,7 +1908,7 @@
**
**********************************************************************
*/
-void arcmsr_start_adapter_bgrb(PACB pACB)
+static void arcmsr_start_adapter_bgrb(PACB pACB)
{
#if ARCMSR_DEBUG0
printk
@@ -1892,7 +1928,7 @@
**
**********************************************************************
*/
-void arcmsr_iop_init(PACB pACB)
+static void arcmsr_iop_init(PACB pACB)
{
uint32_t intmask_org, mask, outbound_doorbell, firmware_state = 0;
@@ -1932,7 +1968,7 @@
**
****************************************************************************
*/
-int arcmsr_bus_reset(Scsi_Cmnd * cmd)
+static int arcmsr_bus_reset(Scsi_Cmnd * cmd)
{
PACB pACB;
@@ -1949,7 +1985,7 @@
**
*****************************************************************************************
*/
-int arcmsr_seek_cmd2abort(Scsi_Cmnd * pabortcmd)
+static int arcmsr_seek_cmd2abort(Scsi_Cmnd * pabortcmd)
{
PACB pACB = (PACB) pabortcmd->device->host->hostdata;
PCCB pCCB;
@@ -2048,7 +2084,7 @@
**
*****************************************************************************************
*/
-int arcmsr_cmd_abort(Scsi_Cmnd * cmd)
+static int arcmsr_cmd_abort(Scsi_Cmnd * cmd)
{
int error;
@@ -2112,7 +2148,7 @@
**
*********************************************************************
*/
-const char *arcmsr_info(struct Scsi_Host *host)
+static const char *arcmsr_info(struct Scsi_Host *host)
{
static char buf[256];
PACB pACB;
@@ -2212,7 +2248,7 @@
**}
************************************************************************
*/
-int arcmsr_initialize(PACB pACB, struct pci_dev *pPCI_DEV)
+static int arcmsr_initialize(PACB pACB, struct pci_dev *pPCI_DEV)
{
uint32_t intmask_org, page_base, page_offset, mem_base_start;
dma_addr_t dma_addr;
@@ -2339,7 +2375,7 @@
*********************************************************************
*********************************************************************
*/
-int arcmsr_set_info(char *buffer, int length)
+static int arcmsr_set_info(char *buffer, int length)
{
#if ARCMSR_DEBUG0
printk("arcmsr_set_info.............\n");
@@ -2352,7 +2388,7 @@
**
*********************************************************************
*/
-void arcmsr_pcidev_disattach(PACB pACB)
+static void arcmsr_pcidev_disattach(PACB pACB)
{
PCCB pCCB;
uint32_t intmask_org, mask;
@@ -2489,8 +2525,8 @@
if(YN) SPRINTF(" Yes ");\
else SPRINTF(" No ")
-int arcmsr_proc_info(struct Scsi_Host *host, char *buffer, char **start,
- off_t offset, int length, int inout)
+static int arcmsr_proc_info(struct Scsi_Host *host, char *buffer, char **start,
+ off_t offset, int length, int inout)
{
uint8_t i;
char *pos = buffer;
@@ -2528,7 +2564,7 @@
**
************************************************************************
*/
-int arcmsr_release(struct Scsi_Host *host)
+static int arcmsr_release(struct Scsi_Host *host)
{
PACB pACB;
uint8_t match = 0xff, i;
Christoph Hellwig
> - aren't the "if defined(__x86_64__)" wrong for other 64bit
> architectures?
Yes. Having arch or 64bit ifdefs is pretty wrong pretty much always.
In one case it's only used to make a typedef a 32bit or 64bit integeger,
that should be using unsigned long directly always, but the other uses
looks like real problems.
Adrian Bunk
Signed-off-by: Adrian Bunk <bu...@stusta.de>
--- linux-2.6.11-rc4-mm1-full/drivers/scsi/ch.c.old 2005-02-28 18:14:48.000000000 +0100
+++ linux-2.6.11-rc4-mm1-full/drivers/scsi/ch.c 2005-02-28 18:14:55.000000000 +0100
@@ -118,7 +118,7 @@
static spinlock_t ch_devlist_lock = SPIN_LOCK_UNLOCKED;
static int ch_devcount;
-struct scsi_driver ch_template =
+static struct scsi_driver ch_template =
{
.owner = THIS_MODULE,
.gendrv = {
Adrian Bunk
> On Fri, Feb 25, 2005 at 10:14:54PM +0100, Adrian Bunk wrote:
> > You don't need this feature unless you know you need it.
>
> But you may not know that you need it since in the help text I
> intentionally didn't mention which software requires the option to be
> set to Y (I didn't mention it, since I didn't want to use the kernel
> configuration help text to get free advertisement, but OTOH if people is
> unsure while they configure the kernel I certainly prefer that they set
> it to Y ;).
If you want to use Cpushare, you know that you have to enable seccomp.
> Thanks.
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
-
Andrea Arcangeli
> If you want to use Cpushare, you know that you have to enable seccomp.
Oh yeah, I know it, you know it, but not everyone will know it while
configuring the kernel, infact I doubt they'll even know what Cpushare
is about while they configure the kernel ;). And I doubt they should be
required to know all those details in order to make that choice, and my
point is that seccomp is low overhead enough that everyone can enable it
if they're unsure, just in case. I'm just trying to explain why I
recommend it to Y by default "if unsure".
Jeff Garzik
> + select CRYPTO
> select CRYPTO_AES
> ---help---
> Include software based cipher suites in support of IEEE 802.11i
> (aka TGi, WPA, WPA2, WPA-PSK, etc.) for use with CCMP enabled
> networks.
> @@ -54,10 +55,11 @@
> "ieee80211_crypt_ccmp".
>
> config IEEE80211_CRYPT_TKIP
> tristate "IEEE 802.11i TKIP encryption"
> depends on IEEE80211
> + select CRYPTO
> select CRYPTO_MICHAEL_MIC
'select CRYPTO_AES' should 'select CRYPTO' automatically, I would hope.
Jeff
Adrian Bunk
> Adrian Bunk wrote:
> >+ select CRYPTO
> > select CRYPTO_AES
> > ---help---
> > Include software based cipher suites in support of IEEE 802.11i
> > (aka TGi, WPA, WPA2, WPA-PSK, etc.) for use with CCMP enabled
> > networks.
> >@@ -54,10 +55,11 @@
> > "ieee80211_crypt_ccmp".
> >
> > config IEEE80211_CRYPT_TKIP
> > tristate "IEEE 802.11i TKIP encryption"
> > depends on IEEE80211
> >+ select CRYPTO
> > select CRYPTO_MICHAEL_MIC
>
>
> 'select CRYPTO_AES' should 'select CRYPTO' automatically, I would hope.
This would result in a recursive dependency.
> Jeff
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
-
Jeff Garzik
> On Wed, Mar 02, 2005 at 01:43:04AM -0500, Jeff Garzik wrote:
>
>>Adrian Bunk wrote:
>>
>>>+ select CRYPTO
>>> select CRYPTO_AES
>>> ---help---
>>> Include software based cipher suites in support of IEEE 802.11i
>>> (aka TGi, WPA, WPA2, WPA-PSK, etc.) for use with CCMP enabled
>>> networks.
>>>@@ -54,10 +55,11 @@
>>> "ieee80211_crypt_ccmp".
>>>
>>>config IEEE80211_CRYPT_TKIP
>>> tristate "IEEE 802.11i TKIP encryption"
>>> depends on IEEE80211
>>>+ select CRYPTO
>>> select CRYPTO_MICHAEL_MIC
>>
>>
>>'select CRYPTO_AES' should 'select CRYPTO' automatically, I would hope.
>
>
> This would result in a recursive dependency.
No, it wouldn't. CRYPTO_AES depends on CRYPTO, which depends on nothing.
Jeff
Andrew Morton
>
> Adrian Bunk wrote:
> > On Wed, Mar 02, 2005 at 01:43:04AM -0500, Jeff Garzik wrote:
> >
> >>Adrian Bunk wrote:
> >>
> >>>+ select CRYPTO
> >>> select CRYPTO_AES
> >>> ---help---
> >>> Include software based cipher suites in support of IEEE 802.11i
> >>> (aka TGi, WPA, WPA2, WPA-PSK, etc.) for use with CCMP enabled
> >>> networks.
> >>>@@ -54,10 +55,11 @@
> >>> "ieee80211_crypt_ccmp".
> >>>
> >>>config IEEE80211_CRYPT_TKIP
> >>> tristate "IEEE 802.11i TKIP encryption"
> >>> depends on IEEE80211
> >>>+ select CRYPTO
> >>> select CRYPTO_MICHAEL_MIC
> >>
> >>
> >>'select CRYPTO_AES' should 'select CRYPTO' automatically, I would hope.
> >
> >
> > This would result in a recursive dependency.
>
> No, it wouldn't. CRYPTO_AES depends on CRYPTO, which depends on nothing.
>
Thing is, CRYPTO_AES on only selectable on x86.
So really, IEEE80211_CRYPT_CCMP should depend upon CRYPTO_AES rather than
selecting it. But that confuses users.
Jeff Garzik
> Jeff Garzik <jga...@pobox.com> wrote:
>
>>Adrian Bunk wrote:
>>
>>>On Wed, Mar 02, 2005 at 01:43:04AM -0500, Jeff Garzik wrote:
>>>
>>>
>>>>Adrian Bunk wrote:
>>>>
>>>>
>>>>>+ select CRYPTO
>>>>> select CRYPTO_AES
>>>>> ---help---
>>>>> Include software based cipher suites in support of IEEE 802.11i
>>>>> (aka TGi, WPA, WPA2, WPA-PSK, etc.) for use with CCMP enabled
>>>>> networks.
>>>>>@@ -54,10 +55,11 @@
>>>>> "ieee80211_crypt_ccmp".
>>>>>
>>>>>config IEEE80211_CRYPT_TKIP
>>>>> tristate "IEEE 802.11i TKIP encryption"
>>>>> depends on IEEE80211
>>>>>+ select CRYPTO
>>>>> select CRYPTO_MICHAEL_MIC
>>>>
>>>>
>>>>'select CRYPTO_AES' should 'select CRYPTO' automatically, I would hope.
>>>
>>>
>>>This would result in a recursive dependency.
>>
>>No, it wouldn't. CRYPTO_AES depends on CRYPTO, which depends on nothing.
>>
>
>
> Thing is, CRYPTO_AES on only selectable on x86.
You're thinking about CRYPTO_AES_586. But looking at crypto/Kconfig,
the dependencies are a bit weird:
config CRYPTO_AES
tristate "AES cipher algorithms"
depends on CRYPTO && !(X86 && !X86_64)
config CRYPTO_AES_586
tristate "AES cipher algorithms (i586)"
depends on CRYPTO && (X86 && !X86_64)
Andrew Morton
>
> > Thing is, CRYPTO_AES on only selectable on x86.
>
> You're thinking about CRYPTO_AES_586. But looking at crypto/Kconfig,
> the dependencies are a bit weird:
>
> config CRYPTO_AES
> tristate "AES cipher algorithms"
> depends on CRYPTO && !(X86 && !X86_64)
> config CRYPTO_AES_586
> tristate "AES cipher algorithms (i586)"
> depends on CRYPTO && (X86 && !X86_64)
That's pretty broken, isn't it?
Would be better to just do:
config CRYPTO_AES
select CRYPTO_AES_586 if (X86 && !X86_64)
select CRYPTO_AES_OTHER if !(X86 && !X86_64)
and hide CRYPTO_AES_586 and CRYPTO_AES_OTHER from the outside world.
Adrian Bunk
> Adrian Bunk wrote:
> >On Wed, Mar 02, 2005 at 01:43:04AM -0500, Jeff Garzik wrote:
> >
> >>Adrian Bunk wrote:
> >>
> >>>+ select CRYPTO
> >>> select CRYPTO_AES
> >>> ---help---
> >>> Include software based cipher suites in support of IEEE 802.11i
> >>> (aka TGi, WPA, WPA2, WPA-PSK, etc.) for use with CCMP enabled
> >>> networks.
> >>>@@ -54,10 +55,11 @@
> >>> "ieee80211_crypt_ccmp".
> >>>
> >>>config IEEE80211_CRYPT_TKIP
> >>> tristate "IEEE 802.11i TKIP encryption"
> >>> depends on IEEE80211
> >>>+ select CRYPTO
> >>> select CRYPTO_MICHAEL_MIC
> >>
> >>
> >>'select CRYPTO_AES' should 'select CRYPTO' automatically, I would hope.
> >
> >
> >This would result in a recursive dependency.
>
> No, it wouldn't. CRYPTO_AES depends on CRYPTO, which depends on nothing.
Exactly.
And if CRYPTO_AES would select CRYPTO, you'd have a recursive
dependency.
The only possible thing would be to change all dependencies on CRYPTO to
selects. This wouldn't be unlogical since the whole crypto subsystem is
only a helper for other subsystems.
James, any opinions on this issue?
> Jeff
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
-
Andrew Morton
>
> > Would be better to just do:
> >
> > config CRYPTO_AES
> > select CRYPTO_AES_586 if (X86 && !X86_64)
> > select CRYPTO_AES_OTHER if !(X86 && !X86_64)
> >
> > and hide CRYPTO_AES_586 and CRYPTO_AES_OTHER from the outside world.
>
>
Please resubmit.
Jeff Garzik
> Jeff Garzik <jga...@pobox.com> wrote:
>
>>>Thing is, CRYPTO_AES on only selectable on x86.
>>
>> You're thinking about CRYPTO_AES_586. But looking at crypto/Kconfig,
>> the dependencies are a bit weird:
>>
>> config CRYPTO_AES
>> tristate "AES cipher algorithms"
>> depends on CRYPTO && !(X86 && !X86_64)
>> config CRYPTO_AES_586
>> tristate "AES cipher algorithms (i586)"
>> depends on CRYPTO && (X86 && !X86_64)
>
>
> That's pretty broken, isn't it?
>
> Would be better to just do:
>
> config CRYPTO_AES
> select CRYPTO_AES_586 if (X86 && !X86_64)
> select CRYPTO_AES_OTHER if !(X86 && !X86_64)
>
> and hide CRYPTO_AES_586 and CRYPTO_AES_OTHER from the outside world.
Not really that easy. For x86 we have
aes
aes-586
aes-via
And my own personal custom-kernel preference is to use the C version of
the code on my x86 and x86-64 boxes.
Jeff
Jeff Garzik
> On Wed, Mar 02, 2005 at 05:41:50PM -0500, Jeff Garzik wrote:
>
>>Andrew Morton wrote:
>>
>>>Jeff Garzik <jga...@pobox.com> wrote:
>>>
>>>
>>>>>Thing is, CRYPTO_AES on only selectable on x86.
>>>>
>>>>You're thinking about CRYPTO_AES_586. But looking at crypto/Kconfig,
>>>>the dependencies are a bit weird:
>>>>
>>>>config CRYPTO_AES
>>>> tristate "AES cipher algorithms"
>>>> depends on CRYPTO && !(X86 && !X86_64)
>>>>config CRYPTO_AES_586
>>>> tristate "AES cipher algorithms (i586)"
>>>> depends on CRYPTO && (X86 && !X86_64)
>>>
>>>
>>>That's pretty broken, isn't it?
>>>
>>>Would be better to just do:
>>>
>>>config CRYPTO_AES
>>> select CRYPTO_AES_586 if (X86 && !X86_64)
>>> select CRYPTO_AES_OTHER if !(X86 && !X86_64)
>>>
>>>and hide CRYPTO_AES_586 and CRYPTO_AES_OTHER from the outside world.
>>
>>Not really that easy. For x86 we have
>>
>> aes
>> aes-586
>> aes-via
>
>
drivers/crypto
>>And my own personal custom-kernel preference is to use the C version of
>>the code on my x86 and x86-64 boxes.
>
>
> That's already not possible today.
It should be.
Adrian Bunk
> >Jeff Garzik <jga...@pobox.com> wrote:
> >
> >>>Thing is, CRYPTO_AES on only selectable on x86.
> >>
> >>You're thinking about CRYPTO_AES_586. But looking at crypto/Kconfig,
> >>the dependencies are a bit weird:
> >>
> >>config CRYPTO_AES
> >> tristate "AES cipher algorithms"
> >> depends on CRYPTO && !(X86 && !X86_64)
> >>config CRYPTO_AES_586
> >> tristate "AES cipher algorithms (i586)"
> >> depends on CRYPTO && (X86 && !X86_64)
> >
> >
> >That's pretty broken, isn't it?
> >
> >Would be better to just do:
> >
> >config CRYPTO_AES
> > select CRYPTO_AES_586 if (X86 && !X86_64)
> > select CRYPTO_AES_OTHER if !(X86 && !X86_64)
> >
> >and hide CRYPTO_AES_586 and CRYPTO_AES_OTHER from the outside world.
>
> Not really that easy. For x86 we have
>
> aes
> aes-586
> aes-via
Where is aes-via?
> And my own personal custom-kernel preference is to use the C version of
> the code on my x86 and x86-64 boxes.
That's already not possible today.
> Jeff
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
-
Adrian Bunk
> Jeff Garzik <jga...@pobox.com> wrote:
> >
> > > Thing is, CRYPTO_AES on only selectable on x86.
> >
> > You're thinking about CRYPTO_AES_586. But looking at crypto/Kconfig,
> > the dependencies are a bit weird:
> >
> > config CRYPTO_AES
> > tristate "AES cipher algorithms"
> > depends on CRYPTO && !(X86 && !X86_64)
> > config CRYPTO_AES_586
> > tristate "AES cipher algorithms (i586)"
> > depends on CRYPTO && (X86 && !X86_64)
>
> That's pretty broken, isn't it?
>
> Would be better to just do:
>
> config CRYPTO_AES
> select CRYPTO_AES_586 if (X86 && !X86_64)
> select CRYPTO_AES_OTHER if !(X86 && !X86_64)
>
> and hide CRYPTO_AES_586 and CRYPTO_AES_OTHER from the outside world.
http://www.ussg.iu.edu/hypermail/linux/kernel/0502.3/0518.html
http://www.ussg.iu.edu/hypermail/linux/kernel/0502.3/0523.html
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
-
Adrian Bunk
> On Tue, Mar 01, 2005 at 01:32:47AM +0100, Adrian Bunk wrote:
> > If you want to use Cpushare, you know that you have to enable seccomp.
>
> Oh yeah, I know it, you know it, but not everyone will know it while
> configuring the kernel, infact I doubt they'll even know what Cpushare
> is about while they configure the kernel ;). And I doubt they should be
> required to know all those details in order to make that choice, and my
> point is that seccomp is low overhead enough that everyone can enable it
> if they're unsure, just in case. I'm just trying to explain why I
> recommend it to Y by default "if unsure".
My point is simply:
The help text for an option you need only under very specific
circumstances shouldn't sound as if this option was nearly was
mandatory.
For me, that's a question principle, not of risks of breakage or code
size.
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
-
Adrian Bunk
> Adrian Bunk wrote:
> >On Wed, Mar 02, 2005 at 05:41:50PM -0500, Jeff Garzik wrote:
> >>Not really that easy. For x86 we have
> >>
> >> aes
> >> aes-586
> >> aes-via
> >
> >
> >Where is aes-via?
>
> drivers/crypto
>
>
> >>And my own personal custom-kernel preference is to use the C version of
> >>the code on my x86 and x86-64 boxes.
> >
> >
> >That's already not possible today.
>
> It should be.
OK, rethinking about it, your arguments sound reasonable.
Could anyone explain, what exactly happens if multiple "aes" algorithms
are compiled into the kernel?
Choosing between the i386 asm and the generic versions seems easy, bug
the VIA Padlock case sounds more tricky since it works only on a subset
of the i386 architecture.
> Jeff
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
-
Andrea Arcangeli
> My point is simply:
>
> The help text for an option you need only under very specific
> circumstances shouldn't sound as if this option was nearly was
> mandatory.
>
> For me, that's a question principle, not of risks of breakage or code
> size.
My point is that the size of the linux desktop userbase is already small
compared to other OS userbase, and I don't want to fragment it even
further risking people to set it to N. People setting this to N is an
huge risk. If most people set it to N I'll be forced to switch to make
drastic plan changes right away. This is why I'd prefer to leave the Y
recommandation for now ;)
Or I'll make it a syscall, do the embedded folks have a compilation
option to disable the sys_sched_setaffinity syscalls and bytecode? No
they don't. By you your same argument we should add a
CONFIG_SCHED_AFFININITY and we shouldn't recommend it to Y.
This isn't a device driver, this is a linux kernel API that some app can
depend on, and you don't know for sure which app will depend on it. So
you should definitely say Y if unsure.
Andrew Morton
>
> My point is simply:
>
> The help text for an option you need only under very specific
> circumstances shouldn't sound as if this option was nearly was
> mandatory.
I think the sort of sell-your-cycles service which this patch enables is a
neat idea, and one which is worth supporting, especially as the kernel
patch is so tiny. So we want as many machines as possible to support it.
So people don't need a special kernel just to join in.
Others may disagree, although nobody has.
And the patch is tiny.
Ingo Molnar
* Andrew Morton <ak...@osdl.org> wrote:
> Adrian Bunk <bu...@stusta.de> wrote:
> >
> > My point is simply:
> >
> > The help text for an option you need only under very specific
> > circumstances shouldn't sound as if this option was nearly was
> > mandatory.
>
> I think the sort of sell-your-cycles service which this patch enables is a
> neat idea, and one which is worth supporting, especially as the kernel
> patch is so tiny. So we want as many machines as possible to support it.
> So people don't need a special kernel just to join in.
>
> Others may disagree, although nobody has.
>
> And the patch is tiny.
see my earlier counter-arguments in the thread starting at:
http://marc.theaimsgroup.com/?l=linux-kernel&m=110630922022462&w=2
end result of the thread: seccomp is completely unnecessary code-bloat
and can be equivalently implemented via ptrace. I cannot believe this
made it into -BK ...
Ingo
Ingo Molnar
we at a minimum need the patch below.
Ingo
Signed-off-by: Ingo Molnar <mi...@elte.hu>
--- linux/arch/i386/Kconfig.orig
+++ linux/arch/i386/Kconfig
@@ -909,7 +909,6 @@ config REGPARM
config SECCOMP
bool "Enable seccomp to safely compute untrusted bytecode"
depends on PROC_FS
- default y
help
This kernel feature is useful for number crunching applications
that may need to compute untrusted bytecode during their
Ingo Molnar
* Ingo Molnar <mi...@elte.hu> wrote:
> see my earlier counter-arguments in the thread starting at:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=110630922022462&w=2
>
> end result of the thread: seccomp is completely unnecessary code-bloat
> and can be equivalently implemented via ptrace. I cannot believe this
> made it into -BK ...
let me moderate my initial reaction somewhat:
the point i see in seccomp is that while it cannot be trusted right now
(not because of any known factor but simply because it doesnt have
enough review, yet), it might at a certain point (in many years) become
more trustable than TRACE_SYSCALLS.
It doesnt use a 'server' process to control syscall execution,
everything is enforced by the kernel. It is also intentionally simple,
and hence maybe even provably secure from a Comp-Sci POV. (assuming
sys_read()/sys_write() and hardware-irq processing itself is secure,
which quite likely wont be provable in the foreseeable future).
Also, while the technological arguments i raised in support of ptrace
are true, ptrace has a perception issue: it is perceived as insecure -
even if PTRACE_TRACE itself is not affected. And when building trust in
a processing platform, perception is just as important as raw security.
this combination of arguments i think tips the balance in favor of
seccomp, but still, i hate the fact that the anti-ptrace sentiment was
used as a vehicle to get this feature into the kernel.
technical comment: seccomp goes outside the audit/selinux framework,
which i believe is a bug. Andrea?
Andrea Arcangeli
> this combination of arguments i think tips the balance in favor of
> seccomp, but still, i hate the fact that the anti-ptrace sentiment was
> used as a vehicle to get this feature into the kernel.
Why should I use excuses to get this feature into the kernel if this
wasn't the best way to reach my goal? Do you think I'm shooting myself
in the foot and that I'd be better off using ptrace?
One other reason of using seccomp that you didn't mention is how simple
it is for me to code everything using seccomp (and this also makes me
much more confortable about its security, regardless of ptrace). Seccomp
is an arch indipendent API, ptrace is not.
It's not just the security of ptrace that is less desiderable, but it's
also the API itself that is much less desiderable, since it's so
lowlevel.
> which quite likely wont be provable in the foreseeable future).
Please mention a _single_ bug that could allow you to escape the seccomp
jail in linux since 2.4.0 on x86 and x86-64 (and with escape I don't
mean sniffing data with mmx not being backwards compatible, or f00f DoS,
I mean executing code into the host as user nobody). I'm not aware of a
_single_ seccomp bug that could allow you to escape the seccomp jail
since 2.4.0 and probably much earlier.
Either you answer the above or you may want to stop spreading FUD about
seccomp (and in turn about Cpushare security).
You know that a seccomp security bug is guaranteed to be a _major_
security bug for linux at large, not just for Cpushare, so I don't see
why you claim it's not provable to be secure, since what you're really
saying is that it's not provable that Linux is secure in multiuser
environment.
Personally I'm very confortable that linux security is ok in
read/write/signal/exit syscalls/irqs. At least as far as the software is
concerned.
It's not like there was no auditing, since those code paths are the most
heavily executed and if people go search into mremap is not because they
wouldn't get any benefit in exploiting read(2) or write(2) instead of
mremap. They look into mremap because they didn't find anything
expoitable in read/write.
There have been positive comments from people about seccomp not just for
my private project, so perhaps it will be used by others too.
In large grid environments security is important too, not just for
Cpushare. In a large grid environment if one of those nodes is
compromised by one user during his computations, this user may see and
alter the results for the other computations of the other users and at
least Cpushare is designed to detect and react to those conditions since
the first place.
Infact once I add trusted computing to Cpushare, it might become more
secure and reliable than a supercomputer for rent that is missing the
trusted computing in the hardware.
> technical comment: seccomp goes outside the audit/selinux framework,
> which i believe is a bug. Andrea?
I intentionally left it out of audit/selinux. To the less dependencies
it has on other parts of the kernel and the simpler it is, the better
IMHO. Seccomp should be fixed in stone, people shouldn't go hack on it
every day.
Andrea Arcangeli
> let me put it another way: this is a security hole. seccomp is now a way
> to evade the auditing of read/write syscalls done to an opened file.
> Please fix this.
This is not true, the auditing of read/write will work fine on the
seccomp task too. I guess you overlooked something in the code.
Ingo Molnar
* Andrea Arcangeli <and...@cpushare.com> wrote:
> This is not true, the auditing of read/write will work fine on the
> seccomp task too. I guess you overlooked something in the code.
yeah, you are right - it's there. You are driving seccomp off
do_syscall_trace(), which does audit_syscall_entry().
Ingo
Ingo Molnar
* Andrea Arcangeli <and...@cpushare.com> wrote:
> > technical comment: seccomp goes outside the audit/selinux framework,
> > which i believe is a bug. Andrea?
>
> I intentionally left it out of audit/selinux. To the less dependencies
> it has on other parts of the kernel and the simpler it is, the better
> IMHO. Seccomp should be fixed in stone, people shouldn't go hack on it
> every day.
let me put it another way: this is a security hole. seccomp is now a way
to evade the auditing of read/write syscalls done to an opened file.
Please fix this.
Ingo
Ingo Molnar
* Andrea Arcangeli <and...@cpushare.com> wrote:
> > which quite likely wont be provable in the foreseeable future).
>
> Please mention a _single_ bug that could allow you to escape the
> seccomp jail in linux since 2.4.0 on x86 and x86-64 (and with escape I
> don't mean sniffing data with mmx not being backwards compatible, or
> f00f DoS, I mean executing code into the host as user nobody). I'm not
> aware of a _single_ seccomp bug that could allow you to escape the
> seccomp jail since 2.4.0 and probably much earlier.
ugh? Where do i claim any such thing?
while we are at it, please mention a single ptrace bug in the same
timeframe that could allow a bytecode 'client' to escape a ptrace
TRACE_SYSCALL jail at will.
Ingo
Andrea Arcangeli
> ugh? Where do i claim any such thing?
You never said such a thing, but you said you believe it's not provable
that sys_read/write and hardware irq processing is secure in linux, so
I wanted to get some statistical significance about your claim from you
just in case I was missing something. I obviously can't have in memory
every single bug since 2.4.0.
> while we are at it, please mention a single ptrace bug in the same
> timeframe that could allow a bytecode 'client' to escape a ptrace
> TRACE_SYSCALL jail at will.
There was this bug around 2.4.10, IIRC a SIGCONT could let the ptraced
task to continue executing. I don't want to depend on other applications
not to send a signal by mistake to the ptraced task.
http://www.ussg.iu.edu/hypermail/linux/kernel/0109.0/1049.html
An oom killer triggering by mistake on a strace -p would have been
enough too. You said if the ptracer is the group leader then the ptraced
task will be killed at the same time, but I doubt many apps depends on
this to be safe, that code is complex and it may break over time during
development if signal handling changes or if the exit code changes.
The interesting point is that no app out there (except uml) becomes
exploitable if you find some hole in TRACE_SYSCALL (at worse strace will
screwup a bit). I don't think an huge amount of research has been done
in those code paths (unlike it happened in mremap and many other kernel
APIs). So even if there are bugs in ptrace they might not being
considered security related. And UML has no other way than to use ptrace
since it needs much more of what I need and UML cannot be arch
indipendent.
While any seccomp security bug is guaranteed to be a major security
linux bug too, so I'm more confortable that more research has been done
in those core code paths than in TRACE_SYSCALL behaviour.
This below is all the code I had to write to secure the remote bytecode
with seccomp, and it's fully arch indipendent (licence is LGPL). Ok,
the seccomp kernel patch is 500 lines, so we should add 500 lines plus
the below ~50 total ~550 lines, but the end result is much nicer and
more secure IMHO. Plus this is simple enough that perhaps Cpushare won't
be the only project using it.
class seccomp_protocol_class(protocol.ProcessProtocol):
def __init__(self, seccomp, d_start, d_end):
self.seccomp = seccomp
self.d_start, self.d_end = d_start, d_end
self.outReceived = self.enable_seccomp_mode
def connectionMade(self):
self.seccomp.cpushare_protocol.seccomp_protocols.append(self)
self.seccomp.cpushare_protocol.transport.registerProducer(self, 1)
self.transport.closeChildFD(2) # close stderr right away
self.transport.writeToChild(0, self.seccomp.header + self.seccomp.text_data)
def enable_seccomp_mode(self, data):
assert data == MAGIC_ASK_SECCOMP, "didn't ask seccomp"
seccomp_file = '/proc/' + str(self.transport.pid) + '/seccomp'
if file(seccomp_file, 'r').read(1) != '0':
raise 'seccomp already enabled?'
file(seccomp_file, 'w').write('1')
if file(seccomp_file, 'r').read(1) != '1':
assert self.transport.pid is not None
print 'Killing the seccomp-loader before it starts the untrusted bytecode'
self.sigkill()
raise 'seccomp enable failure'
self.outReceived = self.send_to_server
self.transport.writeToChild(0, MAGIC_GOT_SECCOMP)
self.d_start.callback(None) # now the buyer is connected
def send_to_server(self, data):
self.seccomp.cpushare_protocol.sendString(PROTO_SECCOMP_FORWARD + data)
def recv_from_server(self, data):
self.transport.writeToChild(0, data)
def errReceived(self, data):
raise "shouldn't happen"
def processEnded(self, status):
self.seccomp.cpushare_protocol.seccomp_protocols.remove(self)
self.seccomp.cpushare_protocol.transport.unregisterProducer()
if status.value.exitCode or status.value.signal:
if status.value.exitCode == 4:
print 'Failure in setting the stack size to %d bytes.' % self.seccomp.stack
if status.value.signal == signal.SIGKILL:
print 'Seccomp task gracefully killed by seccomp.'
elif status.value.signal == signal.SIGSEGV:
print 'Seccomp task gracefully killed by sigsegv.'
elif status.value.signal == signal.SIGQUIT:
print 'Seccomp task killed by sigquit - should never happen.'
self.d_end.errback(status)
else:
print 'Seccomp task completed successfully.'
self.d_end.callback(None)
def sigquit(self):
if self.transport.pid is not None:
os.kill(self.transport.pid, signal.SIGQUIT)
def sigkill(self):
if self.transport.pid is not None:
os.kill(self.transport.pid, signal.SIGKILL)
Ingo Molnar
* Andrea Arcangeli <and...@cpushare.com> wrote:
> Oe Tue, Mar 15, 2005 at 04:05:26PM +0100, Ingo Molnar wrote:
> > ugh? Where do i claim any such thing?
>
> You never said such a thing, but you said you believe it's not
> provable that sys_read/write and hardware irq processing is secure in
> linux, so I wanted to get some statistical significance about your
> claim from you just in case I was missing something. I obviously
> can't have in memory every single bug since 2.4.0.
in fact, we had bugs on x86 where if userspace set up a specific value
for %ebx the kernel would crash, because the irq entry code was
incorrect. (this might even have been exploitable) So yes, if seccomp
would be backported to that kernel, seccomp would be vulnerable too.
but this is not what i meant, what i meant was this:
> > [...] It is also intentionally simple,
> > and hence maybe even provably secure from a Comp-Sci POV.
> > (assuming sys_read()/sys_write() and hardware-irq processing itself
> > is secure, which quite likely wont be provable in the foreseeable
> > future).
'provable' here means provable mathematically, as done in computer
science. Not 'provable via good track record'. So what i said was in
fact a compliment towards seccomp: i believe that as long as we assume
certain external mechanisms (the whole hardware environment, and all
irq/rest-of-kernel and read/write mechanisms) to be secure, the basic
seccomp code itself (those 100-200 lines of code), _may_ be provably
secure, mathematically. That would be a nice thing to have.
obviously the irq and sys_read/sys_write code is way too complex to be
mathematically provable in the near future.
> > while we are at it, please mention a single ptrace bug in the same
> > timeframe that could allow a bytecode 'client' to escape a ptrace
> > TRACE_SYSCALL jail at will.
>
> There was this bug around 2.4.10, IIRC a SIGCONT could let the ptraced
> task to continue executing. I don't want to depend on other
> applications not to send a signal by mistake to the ptraced task.
sorry, but if an attacker can cause arbitrary signals to be sent to your
secure application (and the signals pass the security checks!) then you
have much bigger problems!
this is what i feel is unfair: you are (unintentionally, i presume)
mixing the security of the 'totality of ptrace APIs' with the security
model that 'untrusted bytecode' is in.
> The interesting point is that no app out there (except uml) becomes
> exploitable if you find some hole in TRACE_SYSCALL (at worse strace
> will screwup a bit). I don't think an huge amount of research has been
> done in those code paths (unlike it happened in mremap and many other
> kernel APIs). [...]
so your solution is to introduce a whole new API that duplicates much of
what ptrace can already do, with just about the same amount of risk? So
your solution is to leave UML out in the cold (and thus increasing risks
altogether), by having a crippled mechanism that UML could never use?
That i call a selfish NIH syndrome, not a security accomplishment.
but, i dont mind your code being in the kernel, for the reasons i
stated, as long as the anti-ptrace fallacy is clearly understood. So you
might have partly succeeded in social engineering your security feature
into the kernel (feel the irony?), but i'm trying to counter what i
believe to be false premises. Ptrace has its fundamental security
problems, but PTRACE_TRACE is not nearly as bad and should not be
confused with the kernel holes caused by other, security-independent
ptrace debug mechanisms.
Ingo
Andrea Arcangeli
> in fact, we had bugs on x86 where if userspace set up a specific value
> for %ebx the kernel would crash, because the irq entry code was
> incorrect. (this might even have been exploitable) So yes, if seccomp
> would be backported to that kernel, seccomp would be vulnerable too.
You said "might have been", so you should as well say "might be
vulnerable" too. Either you go check and you prove it exploitable or you
cannot say it would be vulnerable.
I've never heard of this %ebx bug that could be exploitable from my part.
I'm aware of several DoS but they're not really a problem since they can
even be autodetected.
> 'provable' here means provable mathematically, as done in computer
> science. Not 'provable via good track record'. So what i said was in
> fact a compliment towards seccomp: i believe that as long as we assume
> certain external mechanisms (the whole hardware environment, and all
> irq/rest-of-kernel and read/write mechanisms) to be secure, the basic
> seccomp code itself (those 100-200 lines of code), _may_ be provably
> secure, mathematically. That would be a nice thing to have.
The hardware is not provable mathematically anyway, javascript is not
provable mathematically anyway, JVM security for java applets is not
provable mathematically anyway, jpeg decompression is not provable
methematically anyway, gzip decompression is not provable mathematically
anyway, a mail client decoding mime attachments is not provable
mathematically anyway, the ip_conntrack code of the firewall is not
provable anwyay, the ipsec stack is not math provable anyway, the
compiler that compiled the source is not provale mathematically anyway,
the tcp/ip stack is not provable mathematically anyway, I can go on
forever.
The thing I care about is that seccomp is much more provable than the
above and more provable than ptrace as well. Go ahead and disagree with
this bold statement if you can.
> obviously the irq and sys_read/sys_write code is way too complex to be
> mathematically provable in the near future.
Math provable is irrelevant with real software world since nobody has
enough resources to demonstrate math correctness.
The only places where they truly do the math-provable thing is for the
software avoding airplane mid air collisions or problems with a very
limited scope, where it's simple enough that it's actually possible to
prove it (i.e. obviously no real OS like linux, no paging and perhaps
simpler compiler as well).
> sorry, but if an attacker can cause arbitrary signals to be sent to your
> secure application (and the signals pass the security checks!) then you
> have much bigger problems!
It's not the attacker that sends the signal! It's a buggy application
coming from the CDs, like a videogame hitting a bug.
Like kill(-1, SIGCONT) because the fork failed and for some reason the
pid was set to -1.
> this is what i feel is unfair: you are (unintentionally, i presume)
> mixing the security of the 'totality of ptrace APIs' with the security
> model that 'untrusted bytecode' is in.
What I want is a model that guarantees me that nothing from userland can
ever un-release the bytecode so that it becomes free to execute in the
system.
After I enable seccomp on the bytecode there's nothing that the user can
do to un-seccomp the task (unless it changes the right bit in /dev/mem,
but that can't be an accident unlike the kill(-1, SIGCONT)!).
This is not possible to achieve with ptrace.
> but, i dont mind your code being in the kernel, for the reasons i
> stated, as long as the anti-ptrace fallacy is clearly understood. So you
> might have partly succeeded in social engineering your security feature
> into the kernel (feel the irony?), but i'm trying to counter what i
> believe to be false premises. Ptrace has its fundamental security
> problems, but PTRACE_TRACE is not nearly as bad and should not be
> confused with the kernel holes caused by other, security-independent
> ptrace debug mechanisms.
You're the one that wants to prove mathematically the code. So you
should be aware that the more code that is involved, the harder it is to
prove it mathematically safe. In real life math provable won't be doable
in our lifetime, but still the auditing of the code will be more
reliable the shorter the code is. All I did with seccomp is to reduce
the amount of code that you want to prove mathematically. Spending any
time to prove mathematically ptrace (or more realistically audit it)
when somebody can change it at anytime would not be a good idea (for the
other parts like read/write/pipe I can't avoid to re-audit, but ptrace
I can definitely avoid to re-audit thanks to seccomp). Plus as shown,
the API is an order of magnitude simpler to use and it's arch
indipendent unlike ptrace, so perhaps I won't be the only one using it,
and non-kernel developers may actually be able to use it too to do
decompression and similar stuff.
If you can't see any benefit for my project in using in seccomp instead
ptrace that's your problem because there are several tangible benefits
that I already mentioned several times. So I'm not answering further
emails to avoid repeating the same things over and over again.
Ingo Molnar
* Andrea Arcangeli <and...@cpushare.com> wrote:
> > obviously the irq and sys_read/sys_write code is way too complex to be
> > mathematically provable in the near future.
>
> Math provable is irrelevant with real software world since nobody has
> enough resources to demonstrate math correctness.
(this is becoming tangential, but i'd not be as brave to suggest that
formal provability of real software is irrelevant. It's not feasible
today and probably not feasible in the near future. What tomorrow brings
we cannot know.)
> > sorry, but if an attacker can cause arbitrary signals to be sent to your
> > secure application (and the signals pass the security checks!) then you
> > have much bigger problems!
>
> It's not the attacker that sends the signal! It's a buggy application
> coming from the CDs, like a videogame hitting a bug.
well, for an attack to become possible, it's the attacker that has to be
able to trigger it. By your logic i could say: 'many people use empty
passwords for root, so it could easily happen that a seccomp box gets
compromised that way'. The fact that sending SIGCONT to the seccomp
application _seems_ to be more related to the security of the ptrace
solution does not make it any more relevant in reality than the root
password issue. (But i guess after many years i should be wiser not to
get into such arguments with you.) And i've yet to see applications
sending spurious SIGCONT's to each other 'by accident'.
OTOH, i accept your point that a 'no way back' kernel-enforced kind of
sandbox (which seccomp provides and ptrace doesnt) is a useful concept.
Ingo
Andrea Arcangeli
> password issue. (But i guess after many years i should be wiser not to
Your last emails about math proofs, social engineering and selfish NIH
syndrome were ridiculous, and now you get personal.
After all those emails I never heard a good argument from you that made
me even slightly consider changing my plans and to use ptrace instead of
seccomp, and at the end you are degenerating, so I'll have to take it as
a contrarian indicator.
Drop seccomp from the RH kernels if that makes you feel better. You can
always patch the Cpushare client to use ptrace instead of seccomp if you
want. Put your code where your mouth is, the config option is there,
keep it to N.
Ingo Molnar
* Andrea Arcangeli <and...@cpushare.com> wrote:
> After all those emails I never heard a good argument from you that
> made me even slightly consider changing my plans and to use ptrace
> instead of seccomp, [...]
maybe because i ended up agreeing with you? ;)
Ingo
Andrea Arcangeli
> maybe because i ended up agreeing with you? ;)
ok ;) I'm very happy that we agree.