2.6.3-mm1

2.6.3-mm1

[Andrew Morton]

ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm1/

- Added the dm-crypt driver: a crypto layer for device-mapper.

  People need to test and use this please.  There is documentation at
  http://www.saout.de/misc/dm-crypt/.

  We should get this tested and merged up.  We can then remove the nasty
  bio remapping code from the loop driver.  This will remove the current
  ordering guarantees which the loop driver provides for journalled
  filesystems.  ie: ext3 on cryptoloop will no longer be crash-proof.

  After that we should remove cryptoloop altogether.

  It's a bit late but cyptoloop hasn't been there for long anyway and it
  doesn't even work right with highmem systems (that part is fixed in -mm).

- Added the fbdev cursor API patch.  Not sure what this does apart from
  preventing the rivafb driver from linking.  I'll let others decide if this
  is progress.

- There's a patch here to consolidate the 32->64 compat code for the IPC
  syscalls.  Needs testing on various 64-bit machines.

- Various random fixes to things.





Changes since 2.6.3-rc3-mm1:


 bk-netdev.patch
 bk-input.patch
 bk-acpi.patch
 bk-usb.patch
 bk-i2c.patch
 bk-ieee1394.patch
 bk-scsi.patch

 External trees

-selinux-01-context-mount-support.patch
-selinux-02-nfs-context-mounts.patch
-selinux-03-context-mounts-selinux.patch
-devfs-do_mount-fix.patch
-selinux-enforce-node-fix.patch
-selinux-mark-avc_init-init.patch
-selinux-error-handling-fix.patch
-ide-tape-locking-fix.patch
-platinumfb-update.patch

 Merged

-kgdb-doc-fix.patch

 Folded into kgdb-ga.patch

-get_unmapped_area-fix.patch

 Dropped, no longer needed

-early_printk-use-include.patch

 Folded into early-printk.patch

+ppc64-iseries-irq-fix.patch

 ppc64: iseries IRQ fix

+laptop-mode-simplification.patch

 laptop mode simplification

+process-migration-speedup.patch

 Reduce TLB flushing during process migration

+kthread-affinity-fix-fix.patch

 kthread: build fix for many CPUs

+call_usermodehelper-affinity-fix-fix.patch

 many cpus fix

+kthread-stop-using-signals.patch

 kthreads: avoid using signals

+migrate_to_cpu-dependency-fix.patch

 migrate_to_cpu() dependency fix

+hotplugcpu-core-drain_local_pages-fix.patch

 split drain_local_pages 

+hotplugcpu-rcupdate-many-cpus-fix.patch

 CPU hotplug, rcupdate high NR_CPUS fix

-limit-hash-table-sizes.patch
+limit-hash-table-sizes-boot-options.patch

 New version: Limit hashtable sizes

+limit-hash-table-sizes-boot-options-warning-fix.patch
+limit-hash-table-sizes-boot-options-restore-defaults.patch
+limit-hash-table-size-docco.patch

 Touchups thereto

+pentium-m-support-fixes.patch

 fix Pentium M patch

+vm-dont-rotate-active-list-padding.patch

 vmscan: align scan_page per node

+compat-ipc-consolidation.patch
+compat-ipc-consolidation-fix.patch

 common ipc compat syscalls

+remove-bootmem-warnings.patch

 Disable bootmem warning

+dm-crypt.patch

 dm-crypt

+dm-crypt-remove-bogus-BUG_ON.patch

 dm-crypt: remove bogus BUG_ON

+make-rpm-fix.patch

 Fix make rpm when using RH9 or Fedora..

+sysfs_remove_dir-race-fix.patch

 sysfs_remove_dir-vs-dcache_readdir race fix

+sysfs_remove_subdir-dentry-leak-fix.patch

 Fix dentry refcounting in sysfs_remove_group()

+menuconfig-ncurses-check-fix.patch

 menuconfig: fix the check for ncurses-devel

+tlb-flushing-speedup.patch

 Inefficient TLB flush fix

+fbdev-cursor-1.patch

 fbdev cursor part 1.

+sf16fmr2.patch

 sf16fmr2 radio card driver

+expanded-pci-config-space.patch

 Expanded PCI config space

+CONFIG_IRQBALANCE.patch

 config option for irqbalance

+per-node-rss-tracking.patch

 Track per-node RSS for NUMA

+smp_boot_cpus-BUG-removal.patch

 Remove overenthusiastic BUG in smp_boot_cpus

+CodingStyle-update.patch

 Codingstyle update

+smbfs-loop-support.patch

 smbfs: support the loop driver

+cygwin-cpio-fix.patch

 Fix sprintf modifiers in usr/gen_init_cpio.c for cygwin

+aic7xxx-deadlock-fix.patch

 aic7xxx deadlock fix

+futex_wait-debug.patch

 futex_wait debug

+module_exit-deadlock-fix.patch

 module unload deadlock fix

+4g4g-kill-noisy-printk.patch

 4g/4g: remove printk at boot

+O_DIRECT-vs-buffered-fix.patch

 Fix O_DIRECT-vs-buffered data exposure bug





All 292 patches:


bk-netdev.patch

bk-input.patch

bk-acpi.patch

bk-usb.patch

bk-i2c.patch

bk-ieee1394.patch

bk-scsi.patch

mm.patch
  add -mmN to EXTRAVERSION

i4l.patch
  ISDN udpate

i4l-st5481-old-gcc-fix.patch
  i4l: fix st5481 compile for gcc-2.9x

i4l-sc-adapter-fix.patch
  i4l: rename drivers/isdn/sc:adapter

i4l-fixups.patch
  i4l: more fixes

gcc-35-hysdn.patch
  gcc-3.5: ISDN fixes

i4l-hisax-deadlock-fix.patch
  i4l: hisax deadlock fix

i4l-hisax-deadlock-fix-gcc-35-fix.patch
  gcc-3.5: hisax fix

ppp-active-passive-filter-fix.patch
  Fix for PPP activ/passiv filter

speedo-warning-fix.patch
  eepro100.c warning fix

input-2wheel-mouse-fix.patch
  input: 2-wheel mouse fix

input-2wheel-mouse-fix-fix.patch
  From: Adrian Bunk <bunk@fs.tum.de>
  Subject: [patch] 2.6.2-mm1: fix warning introduced by input-2wheel-mouse-fix

dmapool-needs-pci.patch
  dmapool needs CONFIG_PCI

tulip-warning-fix.patch

r8169-rx-wrap-fix.patch
  r8169 Rx wrap 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)

kgdboe-netpoll.patch
  kgdb-over-ethernet via netpoll

kgdboe-non-ia32-build-fix.patch

kgdb-warning-fixes.patch
  kgdb warning fixes

kgdb-x86_64-support.patch
  kgdb-x86_64-support.patch for 2.6.2-rc1-mm3

early_printk.patch
  ia32 early printk
  generate ia32 early_printk via inclusion

early_printk-tweaks.patch
  early printk tweaks

must-fix.patch
  must fix lists update
  must fix list update
  mustfix update

must-fix-update-5.patch
  must-fix update

psmouse-drop-timed-out-bytes.patch
  psmouse: log and discard timed out bytes

ppc64-prom-warnings.patch
  ppc64: Fix prom.c warnings

ppc64-saved-command-line-length-fix.patch
  ppc64: fix saved_command_line/cmd_line lengths

ppc64-debugger-warning-fixes.patch
  ppc64: fix debugger() warnings

ppc64-iseries-irq-fix.patch
  ppc64: iseries IRQ fix

ppc64-reloc_hide.patch

invalidate_inodes-speedup.patch
  invalidate_inodes speedup
  more invalidate_inodes speedup fixes

cfq-4.patch
  CFQ io scheduler
  CFQ fixes

config_spinline.patch
  uninline spinlocks for profiling accuracy.

ramdisk-cleanup.patch

pdflush-diag.patch

zap_page_range-debug.patch
  zap_page_range() debug

slab-print-name.patch
  slab: print slab name in kmem_cache_init()

ptrace-page-permission-fix.patch
  prevent ptrace from altering page permissions

get_user_pages-handle-VM_IO.patch
  fix get_user_pages() against mappings of /dev/mem

support-zillions-of-scsi-disks.patch
  support many SCSI disks

pci_set_power_state-might-sleep.patch

CONFIG_STANDALONE-default-to-n.patch
  Make CONFIG_STANDALONE default to N

extra-buffer-diags.patch

CONFIG_SYSFS.patch
  From: Pat Mochel <mochel@osdl.org>
  Subject: [PATCH] Add CONFIG_SYSFS

CONFIG_SYSFS-boot-from-disk-fix.patch

slab-leak-detector.patch
  slab leak detector

loop-remove-blkdev-special-case.patch

loop-highmem.patch
  remove useless highmem bounce from loop/cryptoloop

loop-bio-handling-fix.patch
  loop: BIO handling fix

loop-init-fix.patch
  loop.c doesn't fail init gracefully

loop-remove-redundant-assignment.patch
  loop: remove redundant initialisation

acpi-pm-timer-3.patch
  ACPI PM timer version 3

acpi-pm-timer-kill-printks.patch

use-TSC-for-delay_pmtmr-2.patch
  Use TSC for delay_pmtmr()

scale-nr_requests.patch
  scale nr_requests with TCQ depth

truncate_inode_pages-check.patch

local_bh_enable-warning-fix.patch

sched-find_busiest_node-resolution-fix.patch
  sched: improved resolution in find_busiest_node

sched-domains.patch
  sched: scheduler domain support

sched-clock-fixes.patch
  fix sched_clock()

sched-build-fix.patch
  sched: fix for NR_CPUS > BITS_PER_LONG

sched-sibling-map-to-cpumask.patch
  sched: cpu_sibling_map to cpu_mask

p4-clockmod-sibling-map-fix.patch
  p4-clockmod sibling_map fix

p4-clockmod-more-than-two-siblings.patch
  p4-clockmod: handle more than two siblings

sched-domains-i386-ht.patch
  sched: implement domains for i386 HT

sched-find_busiest_group-fix.patch
  sched: Fix CONFIG_SMT oops on UP

sched-domain-tweak.patch
  i386-sched-domain code consolidation

sched-no-drop-balance.patch
  sched: handle inter-CPU jiffies skew

sched-arch_init_sched_domains-fix.patch
  Change arch_init_sched_domains to use cpu_online_map

sched-many-cpus-build-fix.patch
  Fix build with NR_CPUS > BITS_PER_LONG

sched-find_busiest_group-clarification.patch
  sched: clarify find_busiest_group

sched-find_busiest_group-arith-fix.patch
  sched: find_busiest_group arithmetic fix

sched-remove-noisy-printks.patch

sched-directed-migration.patch
  sched_balance_exec(): don't fiddle with the cpus_allowed mask

sched-domain-debugging.patch
  sched_domain debugging

sched-domain-balancing-improvements.patch
  scheduler domain balancing improvements

sched-smt-numa-fix.patch
  sched: fix SMT + NUMA bug

ppc64-cpu_vm_mask-fix.patch
  ppc64: cpu_vm_mask fix

ide-siimage-seagate.patch

ide-ali-UDMA6-support.patch
  IDE: Add support of UDMA6 on ALi rev > 0xc4

fa311-mac-address-fix.patch
  wrong mac address with netgear FA311 ethernet card

laptop-mode-2.patch
  laptop-mode for 2.6, version 6
  Documentation/laptop-mode.txt
  laptop-mode documentation updates
  Laptop mode documentation addition

laptop-mode-2-tweaks.patch

laptop-mode-simplification.patch
  laptop mode simplification

pid_max-fix.patch
  Bug when setting pid_max > 32k

use-soft-float.patch
  Use -msoft-float

DRM-cvs-update.patch
  DRM cvs update

drm-include-fix.patch

process-migration-speedup.patch
  Reduce TLB flushing during process migration

kthread-primitive.patch
  kthread primitive
  Fix race in kthread_stop
  kthread: block all signals
  kthread use-after-free fix

use-kthread-primitives.patch
  Use kthread primitives

module-removal-use-kthread.patch
  Module removal to use kthread
  kthread oops fixes

kthread-affinity-fix.patch
  Affinity of kthread fix

kthread-affinity-fix-fix.patch
  kthread: build fix for many CPUs

call_usermodehelper-affinity-fix.patch
  Affinity of call_usermode_helper fix

call_usermodehelper-affinity-fix-fix.patch
  many cpus fix

kthread-handle-non-booting-CPUs.patch
  kthread: handle CPUs which fail to come up

kthread-stop-using-signals.patch
  kthreads: avoid using signals

remove-kstat-cpu-notifiers.patch
  Remove kstat cpu notifiers

workqueue-cleanup-2.patch
  Minor workqueue.c cleanup

remove-more-cpu-notifiers.patch
  Remove More Unneccessary CPU Notifiers

use-CPU_UP_PREPARE-properly.patch
  Use CPU_UP_PREPARE properly

hotplugcpu-generalise-bogolock.patch
  Atomic Hotplug CPU: Generalize Bogolock

hotplugcpu-use-bogolock-in-modules.patch
  Atomic Hotplug CPU: Use Bogolock in module.c

hotplugcpu-core.patch
  Atomic Hotplug CPU: Hotplug CPU Core

migrate_to_cpu-dependency-fix.patch
  migrate_to_cpu() dependency fix

hotplugcpu-core-drain_local_pages-fix.patch
  split drain_local_pages

hotplugcpu-rcupdate-many-cpus-fix.patch
  CPU hotplug, rcupdate high NR_CPUS fix

limit-hash-table-sizes-boot-options.patch
  Limit hashtable sizes

limit-hash-table-sizes-boot-options-warning-fix.patch

limit-hash-table-sizes-boot-options-restore-defaults.patch

limit-hash-table-size-docco.patch
  hash table size sysctl documentation

slab-poison-hex-dumping.patch
  slab: hexdump for check_poison

pentium-m-support.patch
  add Pentium M and Pentium-4 M options

pentium-m-support-fixes.patch
  fix Pentium M patch

old-gcc-supports-k6.patch
  gcc 2.95 supports -march=k6 (no need for check_gcc)

amd-elan-is-a-different-subarch.patch
  AMD Elan is a different subarch

serial-02-fixups.patch
  serial fixups (untested)
  serial-02 fixes
  serial-02 fixes

serial-03-fixups.patch
  more serial driver fixups
  serial-03 fixes
  serial-03 fixes

nfs-31-attr.patch
  NFSv2/v3/v4: New attribute revalidation code

blk_congestion_wait-return-remaining.patch
  return remaining jiffies from blk_congestion_wait()

vmscan-remove-priority.patch
  mm/vmscan.c: remove unused priority argument.

kswapd-throttling-fixes.patch
  kswapd throttling fixes

vm-dont-rotate-active-list.patch
  vmscan: avoid rotation of the active list

vm-dont-rotate-active-list-padding.patch
  vmscan: align scan_page per node

vm-lru-info.patch
  vmscan: make better use of referenced info

vm-shrink-zone.patch
  vmscan: several tuneups

vm-shrink-zone-div-by-0-fix.patch

vm-tune-throttle.patch
  vmscan: delay throttling a little

page_add_rmap-warning.patch

add-config-for-mregparm-3-ng.patch
  Add CONFIG for -mregparm=3
  arch/i386/Makefile,scripts/gcc-version.sh,Makefile small fixes

use-funit-at-a-time.patch
  Use -funit-at-a-time on ia32

add-noinline-attribute.patch
  Add noinline attribute

dont-inline-rest_init.patch
  use noinline for rest_init()

gcc-35-bonding.patch
  gcc-3.5: bonding

non-readable-binaries.patch
  Handle non-readable binfmt_misc executables

binfmt_misc-credentials.patch
  binfmt_misc: improve calaulation of interpreter's credentials

doc-remove-modules-conf-references.patch
  Documentation: remove /etc/modules.conf refs

more-MODULE_ALIASes.patch
  add some more MODULE_ALIASes

bonding-alias-revert-and-docco-fix.patch
  bonding alias revert and documentation fix

sleep_on-needs_lock_kernel.patch
  sleep_on(): check for lock_kernel

i830-agp-pm-fix.patch
  Intel i830 AGP fix

x86_64-make-xconfig-fix.patch
  Fix make xconfig on /lib64 systems

usb-sddr09-documentation.patch
  add comments to sddr09.c

pcnet32-locking-fix.patch
  pcmet32 locking fixes

nfs-server-in-root_server_path.patch
  Pull NFS server address out of root_server_path

increase-NGROUPS.patch
  NGROUPS 2.6.2rc2 + fixups
  NGROUPS: remove TASK_SIZE usage
  NGROUPS: generalise condition for freeing sub-pages

increase-NGROUPS-nfsd-cleanup.patch
  NGROUPS: nfsd cleanup

increase-NGROUPS-cleanup-and-fix.patch
  NGROUPS: cleanup and fix

intermezzo-NGROUPS-is-broken.patch

compat-signal-noarch-2004-01-29.patch
  Generic 32-bit compat for copy_siginfo_to_user

compat-signal-ppc64-2004-01-29.patch

compat-signal-ia64-2004-01-29.patch

compat-ipc-consolidation.patch
  common ipc compat syscalls

compat-ipc-consolidation-fix.patch

bd_set_size-i_size-fix.patch
  bd_set_size i_size handling

nfs-d_drop-lowmem.patch
  NFS: handle nfs_fhget() error

initramfs-kinit_command.patch
  initramfs: look for /sbin/init

access-permissions-fix.patch
  fix access() POSIX compliance

snprintf-fixes.patch
  snprintf fixes

devfs-race-fix-cleanup.patch
  devfs: race fixes and cleanup

centaur-crypto-core-support.patch
  First steps toward VIA crypto support

enable-largefile-coredumps.patch
  Enable coredumps > 2GB

adaptive-lazy-readahead.patch
  adaptive lazy readahead

mips-new-serial-drivers.patch
  MIPS: New 2.6 serial drivers

add-syscalls_h.patch
  add syscalls.h

add-syscalls_h-fixes.patch

add-syscalls-update.patch
  syscalls.h update1

add-syscalls_h-3.patch
  more syscalls.h stuff

add-syscalls_h-4.patch
  syscalls.h fixes

add-syscalls_h-6.patch
  syscalls.h (updates # 6)

add-syscalls_h-7.patch
  syscalls update ver. 7

add-syscalls_h-8.patch
  syscalls update #8

add-syscalls_h-9.patch
  syscalls.h update #9 (open/close)

add-syscalls_h-10.patch
  syscalls.h #10

stop_machine-warning-fix.patch

ifdef-cleanups.patch
  #if versus #ifdef cleanup

nfsd-01-schedule-in-spinlock-fix.patch
  kNFSd: Fix possible scheduling_while_atomic in cache.c

nfsd-02-sunrpc-cache-init-fixes.patch
  kNFSd: Allow sunrpc/svc cache init function to modify the "key"

nfsd-03-ip_map_init-kmalloc-check.patch
  kNFSd: ip_map_init does a kmalloc which isn't checked...

nfsd-04-convert-proc-to-seq_file.patch
  kNFSd: convert NFS /proc interfaces to seq_file

nfsd-05-no-procfs-build-fix.patch
  kNFSd:fix build problems in nfs w/o proc_fs on 2.6.0-test5

md-01-START_ARRAY-is-deprecated.patch
  md: Print "deprecated" warning when START_ARRAY is used.

md-02-split-end_request-handlers.patch
  md: Split read and write end_request handlers

md-03-discard-r1_bio-cmd-field.patch
  md: Discard the cmd field from r1_bio structure

md-04-r1_bio-cleanup.patch
  md: Remove some un-needed fields from r1bio_s

md-05-avoid-bio-allocation.patch
  md: Avoid unnecessary bio allocation during raid1 resync

md-06-raid1-limit-bio-sizes.patch
  md: Dynamically limit size of bio requests used for raid1 resync

md-07-allow-partitioning.patch
  md: Allow partitioning of MD devices.

dm-01-export-dm_vcalloc.patch
  dm: Export dm_vcalloc()

dm-02-move-to_bytes-to_sectors.patch
  dm: Move to_bytes() and to_sectors() into dm.h

dm-03-remove-dm_deferred_io.patch
  dm: Get rid of struct dm_deferred_io in dm.c

dm-04-maintain-bio-ordering.patch
  dm: Maintain ordering when deferring bios

dm-05-alloc_dev-error-cleanup.patch
  dm: Tidy up the error path for alloc_dev()

dm-07-dm_table_create-GFP-fix.patch
  dm: Correct GFP flag in dm_table_create()

dm-08-zero-size-target-fix.patch
  dm: Zero size target sanity check

dm-09-dec_pending-locking-cleanup.patch
  dm: Remove redundant spin lock in dec_pending()

dm-10-drop-BIO_SEG_VALID.patch
  dm: drop BIO_SEG_VALID bit

nfs-avoid-i_size_write.patch
  NFS: avoid unlocked i_size_write()

ia32-discontig-pfn_valid-fix.patch
  fix pfn_valid on ia32 discontigmem

ia32-pfn_to_nid-fix.patch
  ia32: pfn_to_nid fix

ia32-numa-pcs-dont-work.patch
  ia32: disallow NUMA on PC subarch

8259-timer-ack-fix.patch
  8259 timer ack fix

mce-printk-level-fixes.patch
  Fix printk level on non fatal MCEs

mce-preempt-fixes.patch
  MCE fixes and cleanups

bitmap_snprintf-bitmap_scnprintf.patch
  Rename bitmap_snprintf() and cpumask_snprintf() to *_scnprintf()

oss-cruft-removal.patch
  OSS: remove #ifdef's for kernel 2.0

stallion-decruftery.patch
  remove kernel 2.2 #ifdef's from {i,}stallion.h

external-kbuild-doc.patch
  kbuild documentation fix

adfs-2.2-cruft.patch
  adfs: remove a kernel 2.2 #ifdef

panic-later-if-too-many-boot-params.patch
  defer panic for too many items in boot parameter line

altix-irq-accounting-speedup.patch
  altix: use the pda to count interrupts

altix-simulator-fix.patch
  altix: skip init_platform_hubinfo() if on the simulator

cpufreq_scale-fix-cleanup.patch
  cpufreq_scale() fixes

alsa-vx_core-locking-fix.patch
  alsa/vx_core locking fix

cross-compilation-fixes.patch
  Minor cross-compile issues

proc-thread-visibility-fix.patch
  /proc thread visibility fixes

console-race-fix.patch
  drivers/char/vt possible race

nfsd-needs-loff_t.patch
  off_t in nfsd_commit needs to be loff_t

show_free_areas-online-cpus.patch
  skip offline CPUs in show_free_areas

nbd-proc-partitions-fix.patch
  fix display of NBD in /proc/partitions

use-THREAD_SIZE.patch
  cleanup patch that prepares for 4Kb stacks

3c59x-enable_wol.patch
  3c59x: bring back the `enable_wol' option

oprofile-nmi_timer_int-fix.patch
  Oprofile: fix nmi_timer_int detection

oprofile-arm-support.patch
  oprofile: ARM infrastructure

oprofile-pentium-m-support.patch
  oprofile: add Pentium Mobile support

increase-max_anon.patch
  remove max_anon limit

release_region-race-fix.patch
  Fix __release_region() race

nfs-mount-oops-fix.patch
  nfs mount oops fix

debugging-modules.patch
  Documentation on how to debug modules

sn-setup-cleanup.patch
  SN: cleanup setup.c

jfs-01-sane-filename-handling.patch
  JFS: sane file name handling

jfs-02-sane-filename-handling.patch
  JFS: Don't do filename translation by default

ext3-journalled-quotas.patch
  ext3: Journalled quotas

ext3-journalled-quotas-warning-fix.patch

ext3-journalled-quotas-cleanups.patch

module-headers-cleanup.patch
  Module headers cleanup

dynamic-pty-allocation.patch
  dynamic pty allocation

add-clock_was_set.patch
  add clock_was_set to all architectures

altix-header-cleanups.patch
  Altix header file cleanups

epoll_ctl-race-fix.patch
  Fix race in epoll_ctl(EPOLL_CTL_MOD)

slab-printk-suppression.patch
  slab: remove extraneous printk

do_swap_page-retval-fix.patch
  do_swap_page() return value fix

ide-tape-remove-onstream-support.patch
  ide-tape: remove obsolete onstream support

ide-tape-warning-fixes.patch

remove-bootmem-warnings.patch
  Disable bootmem warning

dm-crypt.patch
  dm-crypt

dm-crypt-remove-bogus-BUG_ON.patch
  dm-crypt: remove bogus BUG_ON

make-rpm-fix.patch
  Fix make rpm when using RH9 or Fedora..

sysfs_remove_dir-race-fix.patch
  sysfs_remove_dir-vs-dcache_readdir race fix

sysfs_remove_subdir-dentry-leak-fix.patch
  Fix dentry refcounting in sysfs_remove_group()

menuconfig-ncurses-check-fix.patch
  menuconfig: fix the check for ncurses-devel

tlb-flushing-speedup.patch
  Inefficient TLB flush fix

fbdev-cursor-1.patch
  fbdev cursor part 1.

sf16fmr2.patch
  sf16fmr2 radio card driver

expanded-pci-config-space.patch
  Expanded PCI config space

CONFIG_IRQBALANCE.patch
  config option for irqbalance

per-node-rss-tracking.patch
  Track per-node RSS for NUMA

smp_boot_cpus-BUG-removal.patch
  Remove overenthusiastic BUG in smp_boot_cpus

CodingStyle-update.patch
  Codingstyle update

smbfs-loop-support.patch
  smbfs: support the loop driver

cygwin-cpio-fix.patch
  Fix sprintf modifiers in usr/gen_init_cpio.c for cygwin

aic7xxx-deadlock-fix.patch
  aic7xxx deadlock fix

futex_wait-debug.patch
  futex_wait debug

module_exit-deadlock-fix.patch
  module unload deadlock fix

list_del-debug.patch
  list_del debug check

print-build-options-on-oops.patch

show_task-free-stack-fix.patch
  show_task() fix and cleanup

show_task-fix.patch
  show_task() is not SMP safe

oops-dump-preceding-code.patch
  i386 oops output: dump preceding code

lockmeter.patch

ia64-lockmeter-fix.patch

lockmeter-2.2-cruft.patch
  lockmeter.h: remove kernel 2.2 #ifdef (i386 + alpha)

4g-2.6.0-test2-mm2-A5.patch
  4G/4G split patch
  4G/4G: remove debug code
  4g4g: pmd fix
  4g/4g: fixes from Bill
  4g4g: fpu emulation fix
  4g/4g usercopy atomicity fix
  4G/4G: remove debug code
  4g4g: pmd fix
  4g/4g: fixes from Bill
  4g4g: fpu emulation fix
  4g/4g usercopy atomicity fix
  4G/4G preempt on vstack
  4G/4G: even number of kmap types
  4g4g: fix __get_user in slab
  4g4g: Remove extra .data.idt section definition
  4g/4g linker error (overlapping sections)
  4G/4G: remove debug code
  4g4g: pmd fix
  4g/4g: fixes from Bill
  4g4g: fpu emulation fix
  4g4g: show_registers() fix
  4g/4g usercopy atomicity fix
  4g4g: debug flags fix
  4g4g: Fix wrong asm-offsets entry
  cyclone time fixmap fix
  4G/4G preempt on vstack
  4G/4G: even number of kmap types
  4g4g: fix __get_user in slab
  4g4g: Remove extra .data.idt section definition
  4g/4g linker error (overlapping sections)
  4G/4G: remove debug code
  4g4g: pmd fix
  4g/4g: fixes from Bill
  4g4g: fpu emulation fix
  4g4g: show_registers() fix
  4g/4g usercopy atomicity fix
  4g4g: debug flags fix
  4g4g: Fix wrong asm-offsets entry
  cyclone time fixmap fix
  use direct_copy_{to,from}_user for kernel access in mm/usercopy.c
  4G/4G might_sleep warning fix
  4g/4g pagetable accounting fix
  Fix 4G/4G and WP test lockup
  4G/4G KERNEL_DS usercopy again
  Fix 4G/4G X11/vm86 oops
  Fix 4G/4G athlon triplefault
  4g4g SEP fix
  Fix 4G/4G split fix for pre-pentiumII machines
  4g/4g PAE ACPI low mappings fix

zap_low_mappings-fix.patch
  zap_low_mappings() cannot be __init

4g4g-locked-userspace-copy.patch
  Do a locked user-space copy for 4g/4g

4g4g-kill-noisy-printk.patch
  4g/4g: remove printk at boot

ppc-fixes.patch
  make mm4 compile on ppc

O_DIRECT-race-fixes-rollup.patch
  O_DIRECT data exposure fixes

O_DIRECT-ll_rw_block-vs-block_write_full_page-fix.patch
  Fix race between ll_rw_block() and block_write_full_page()

blockdev-direct-io-speedup.patch
  blockdev direct-io speedups

O_DIRECT-vs-buffered-fix.patch
  Fix O_DIRECT-vs-buffered data exposure bug

dio-aio-fixes.patch
  direct-io AIO fixes

aio-fallback-bio_count-race-fix-2.patch
  AIO+DIO bio_count race fix

aio-sysctl-parms.patch
  aio sysctl parms

Re: 2.6.3-mm1

[Andrew Morton]

Andrew Morton <akpm@osdl.org> wrote:
>
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm1/

oops, it appears that rmmod hangs in D state all the time.  

root      1381  0.0  0.0     0    0 ?        SW<  23:33   0:00  \_ [kstopmachine]
root      1382  0.0  0.0     0    0 ?        Z<   23:33   0:00      \_ [kstopmachine <defunct>]
root      1380  0.0  0.1  1356  392 pts/0    D    23:33   0:00  |           \_ rmmod 3c59x

Re: 2.6.3-mm1

[Andrew Morton]

Andrew Morton <akpm@osdl.org> wrote:
>
> Andrew Morton <akpm@osdl.org> wrote:
>  >
>  > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm1/
> 
>  oops, it appears that rmmod hangs in D state all the time.  

Fixes:


 kernel/stop_machine.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN kernel/stop_machine.c~hotplugcpu-generalise-bogolock-fix-for-kthread-stop-using-signals kernel/stop_machine.c
--- 25/kernel/stop_machine.c~hotplugcpu-generalise-bogolock-fix-for-kthread-stop-using-signals	2004-02-18 01:14:27.000000000 -0800
+++ 25-akpm/kernel/stop_machine.c	2004-02-18 01:14:54.000000000 -0800
@@ -148,7 +148,7 @@ static int do_stop(void *_smdata)
 	complete(&smdata->done);
 
 	/* Wait for kthread_stop */
-	while (!signal_pending(current)) {
+	while (!kthread_should_stop()) {
 		__set_current_state(TASK_INTERRUPTIBLE);
 		schedule();
 	}

_


 kernel/softirq.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN kernel/softirq.c~hotplugcpu-core-fix-for-kthread-stop-using-signals kernel/softirq.c
--- 25/kernel/softirq.c~hotplugcpu-core-fix-for-kthread-stop-using-signals	2004-02-18 01:19:14.000000000 -0800
+++ 25-akpm/kernel/softirq.c	2004-02-18 01:19:29.000000000 -0800
@@ -349,7 +349,7 @@ static int ksoftirqd(void * __bind_cpu)
 wait_to_die:
 	preempt_enable();
 	/* Wait for kthread_stop */
-	while (!signal_pending(current)) {
+	while (!kthread_should_stop()) {
 		__set_current_state(TASK_INTERRUPTIBLE);
 		schedule();
 	}

_


 ipc/shm.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN ipc/shm.c~add-syscalls_h-shmat-fix ipc/shm.c
--- 25/ipc/shm.c~add-syscalls_h-shmat-fix	2004-02-18 01:22:41.000000000 -0800
+++ 25-akpm/ipc/shm.c	2004-02-18 01:22:41.000000000 -0800
@@ -635,7 +635,7 @@ out:
  * "raddr" thing points to kernel space, and there has to be a wrapper around
  * this.
  */
-long sys_shmat(int shmid, char __user *shmaddr, int shmflg, ulong *raddr)
+asmlinkage long sys_shmat(int shmid, char __user *shmaddr, int shmflg, ulong *raddr)
 {
 	struct shmid_kernel *shp;
 	unsigned long addr;

_

Re: 2.6.3-mm1

[Rusty Russell]

In message <20040218012553.1228ae34.akpm@osdl.org> you write:
> Andrew Morton <akpm@osdl.org> wrote:
> >
> > Andrew Morton <akpm@osdl.org> wrote:
> >  >
> >  > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.
3-mm1/
> > 
> >  oops, it appears that rmmod hangs in D state all the time.  
> 
> Fixes:

[ snip obviously correct fixes ]

Yes.  My bad: I forwarded a replacement kthread implementation to you
and missed the other subs.  It was 1am on a Monday morning, but
nonetheless.

Do you want me to consolidate the patches in your tree?  At the moment
you're carrying:

kthread-primitive.patch
kthread-affinity-fix.patch
kthread-affinity-fix-fix.patch
kthread-handle-non-booting-CPUs.patch
kthread-stop-using-signals.patch

Which are logically a single "kthread-without-signals" patch.

Rusty.
--
  Anyone who quotes me in their sig is an idiot. -- Rusty Russell.

Re: 2.6.3-mm1

[Andrew Morton]

Rusty Russell <rusty@rustcorp.com.au> wrote:
>
> Do you want me to consolidate the patches in your tree?  At the moment
>  you're carrying:
> 
>  kthread-primitive.patch
>  kthread-affinity-fix.patch
>  kthread-affinity-fix-fix.patch
>  kthread-handle-non-booting-CPUs.patch
>  kthread-stop-using-signals.patch
> 
>  Which are logically a single "kthread-without-signals" patch.

Is OK, thanks - that is merely a matter of typing `joinpatch $(nextpatch);
drop-patch $(nextpatch)' four times.

I generally keep these things separated for quite a long time because it
aids in the binary-search-to-see-what-broke-it game.

Re: 2.6.3-mm1

[Sean Neakums]

Using the configuration below (UP+PREEMPT, all user-visible ACPI
configuration options disabled), I get the following errors at link
time:

  arch/i386/kernel/built-in.o(.text+0xc9ab): In function `acpi_apic_setup':
  : undefined reference to `smp_found_config'
  arch/i386/kernel/built-in.o(.text+0xc9b0): In function `acpi_apic_setup':
  : undefined reference to `clustered_apic_check'

This change "fixes" it, in that the link succeeds and the machine
boots and seems to work.


--- S3-mm1/arch/i386/kernel/acpi/boot.c~	2004-02-18 10:07:36.000000000 +0000
+++ S3-mm1/arch/i386/kernel/acpi/boot.c	2004-02-18 10:48:19.000000000 +0000
@@ -576,10 +576,12 @@
 
 #endif /* CONFIG_X86_IO_APIC && CONFIG_ACPI_INTERPRETER */
 
+#ifdef SMP
 	if (acpi_lapic && acpi_ioapic) {
 		smp_found_config = 1;
 		clustered_apic_check();
 	}
+#endif
 
 	return 0;
 }



#
# Automatically generated make config: don't edit
#
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_UID16=y
CONFIG_GENERIC_ISA_DMA=y

#
# Code maturity level options
#
CONFIG_EXPERIMENTAL=y
CONFIG_CLEAN_COMPILE=y
CONFIG_STANDALONE=y
CONFIG_BROKEN_ON_SMP=y

#
# General setup
#
CONFIG_SWAP=y
CONFIG_SYSVIPC=y
# CONFIG_BSD_PROCESS_ACCT is not set
CONFIG_SYSCTL=y
CONFIG_LOG_BUF_SHIFT=14
# CONFIG_IKCONFIG is not set
# CONFIG_EMBEDDED is not set
CONFIG_KALLSYMS=y
CONFIG_FUTEX=y
CONFIG_EPOLL=y
CONFIG_IOSCHED_NOOP=y
CONFIG_IOSCHED_AS=y
CONFIG_IOSCHED_DEADLINE=y
CONFIG_IOSCHED_CFQ=y
# CONFIG_CC_OPTIMIZE_FOR_SIZE is not set

#
# Loadable module support
#
# CONFIG_MODULES is not set

#
# Processor type and features
#
CONFIG_X86_PC=y
# CONFIG_X86_ELAN is not set
# CONFIG_X86_VOYAGER is not set
# CONFIG_X86_NUMAQ is not set
# CONFIG_X86_SUMMIT is not set
# CONFIG_X86_BIGSMP is not set
# CONFIG_X86_VISWS is not set
# CONFIG_X86_GENERICARCH is not set
# CONFIG_X86_ES7000 is not set
# CONFIG_M386 is not set
# CONFIG_M486 is not set
# CONFIG_M586 is not set
# CONFIG_M586TSC is not set
# CONFIG_M586MMX is not set
# CONFIG_M686 is not set
# CONFIG_MPENTIUMII is not set
CONFIG_MPENTIUMIII=y
# CONFIG_MPENTIUMM is not set
# CONFIG_MPENTIUM4 is not set
# CONFIG_MK6 is not set
# CONFIG_MK7 is not set
# CONFIG_MK8 is not set
# CONFIG_MELAN is not set
# CONFIG_MCRUSOE is not set
# CONFIG_MWINCHIPC6 is not set
# CONFIG_MWINCHIP2 is not set
# CONFIG_MWINCHIP3D is not set
# CONFIG_MCYRIXIII is not set
# CONFIG_MVIAC3_2 is not set
# CONFIG_X86_GENERIC is not set
CONFIG_X86_CMPXCHG=y
CONFIG_X86_XADD=y
CONFIG_X86_L1_CACHE_SHIFT=5
CONFIG_RWSEM_XCHGADD_ALGORITHM=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_X86_4G is not set
# CONFIG_X86_SWITCH_PAGETABLES is not set
# CONFIG_X86_4G_VM_LAYOUT is not set
# CONFIG_X86_UACCESS_INDIRECT is not set
# CONFIG_X86_HIGH_ENTRY is not set
# CONFIG_HPET_TIMER is not set
# CONFIG_HPET_EMULATE_RTC is not set
# CONFIG_SMP is not set
CONFIG_PREEMPT=y
# CONFIG_X86_UP_APIC is not set
CONFIG_X86_TSC=y
CONFIG_X86_MCE=y
CONFIG_X86_MCE_NONFATAL=y
# CONFIG_TOSHIBA is not set
# CONFIG_I8K is not set
# CONFIG_MICROCODE is not set
# CONFIG_X86_MSR is not set
# CONFIG_X86_CPUID is not set
# CONFIG_EDD is not set
CONFIG_NOHIGHMEM=y
# CONFIG_HIGHMEM4G is not set
# CONFIG_HIGHMEM64G is not set
# CONFIG_MATH_EMULATION is not set
CONFIG_MTRR=y
CONFIG_HAVE_DEC_LOCK=y
CONFIG_REGPARM=y

#
# Power management options (ACPI, APM)
#
# CONFIG_PM is not set

#
# ACPI (Advanced Configuration and Power Interface) Support
#
# CONFIG_ACPI is not set
CONFIG_ACPI_BOOT=y

#
# CPU Frequency scaling
#
# CONFIG_CPU_FREQ is not set

#
# Bus options (PCI, PCMCIA, EISA, MCA, ISA)
#
CONFIG_PCI=y
# CONFIG_PCI_GOBIOS is not set
# CONFIG_PCI_GOMMCONFIG is not set
# CONFIG_PCI_GODIRECT is not set
CONFIG_PCI_GOANY=y
CONFIG_PCI_BIOS=y
CONFIG_PCI_DIRECT=y
CONFIG_PCI_MMCONFIG=y
CONFIG_PCI_LEGACY_PROC=y
CONFIG_PCI_NAMES=y
CONFIG_ISA=y
# CONFIG_EISA is not set
# CONFIG_MCA is not set
# CONFIG_SCx200 is not set
CONFIG_HOTPLUG=y

#
# PCMCIA/CardBus support
#
# CONFIG_PCMCIA is not set
CONFIG_PCMCIA_PROBE=y

#
# PCI Hotplug Support
#
# CONFIG_HOTPLUG_PCI is not set

#
# Executable file formats
#
CONFIG_BINFMT_ELF=y
# CONFIG_BINFMT_AOUT is not set
# CONFIG_BINFMT_MISC is not set

#
# Device Drivers
#

#
# Generic Driver Options
#
# CONFIG_FW_LOADER is not set

#
# Memory Technology Devices (MTD)
#
# CONFIG_MTD is not set

#
# Parallel port support
#
# CONFIG_PARPORT is not set

#
# Plug and Play support
#
# CONFIG_PNP is not set

#
# Block devices
#
CONFIG_BLK_DEV_FD=y
# CONFIG_BLK_DEV_XD is not set
# CONFIG_BLK_CPQ_DA is not set
# CONFIG_BLK_CPQ_CISS_DA is not set
# CONFIG_BLK_DEV_DAC960 is not set
# CONFIG_BLK_DEV_UMEM is not set
CONFIG_BLK_DEV_LOOP=y
CONFIG_BLK_DEV_CRYPTOLOOP=y
# CONFIG_BLK_DEV_NBD is not set
# CONFIG_BLK_DEV_RAM is not set
# CONFIG_BLK_DEV_INITRD is not set
CONFIG_LBD=y

#
# ATA/ATAPI/MFM/RLL support
#
CONFIG_IDE=y
CONFIG_BLK_DEV_IDE=y

#
# Please see Documentation/ide.txt for help/info on IDE drives
#
# CONFIG_BLK_DEV_HD_IDE is not set
CONFIG_BLK_DEV_IDEDISK=y
CONFIG_IDEDISK_MULTI_MODE=y
# CONFIG_IDEDISK_STROKE is not set
CONFIG_BLK_DEV_IDECD=y
# CONFIG_BLK_DEV_IDETAPE is not set
# CONFIG_BLK_DEV_IDEFLOPPY is not set
# CONFIG_IDE_TASK_IOCTL is not set
CONFIG_IDE_TASKFILE_IO=y

#
# IDE chipset support/bugfixes
#
CONFIG_IDE_GENERIC=y
# CONFIG_BLK_DEV_CMD640 is not set
CONFIG_BLK_DEV_IDEPCI=y
CONFIG_IDEPCI_SHARE_IRQ=y
# CONFIG_BLK_DEV_OFFBOARD is not set
CONFIG_BLK_DEV_GENERIC=y
# CONFIG_BLK_DEV_OPTI621 is not set
CONFIG_BLK_DEV_RZ1000=y
CONFIG_BLK_DEV_IDEDMA_PCI=y
# CONFIG_BLK_DEV_IDEDMA_FORCED is not set
CONFIG_IDEDMA_PCI_AUTO=y
# CONFIG_IDEDMA_ONLYDISK is not set
CONFIG_BLK_DEV_ADMA=y
# CONFIG_BLK_DEV_AEC62XX is not set
# CONFIG_BLK_DEV_ALI15X3 is not set
# CONFIG_BLK_DEV_AMD74XX is not set
# CONFIG_BLK_DEV_CMD64X is not set
# CONFIG_BLK_DEV_TRIFLEX is not set
# CONFIG_BLK_DEV_CY82C693 is not set
# CONFIG_BLK_DEV_CS5520 is not set
# CONFIG_BLK_DEV_CS5530 is not set
# CONFIG_BLK_DEV_HPT34X is not set
# CONFIG_BLK_DEV_HPT366 is not set
# CONFIG_BLK_DEV_SC1200 is not set
CONFIG_BLK_DEV_PIIX=y
# CONFIG_BLK_DEV_NS87415 is not set
# CONFIG_BLK_DEV_PDC202XX_OLD is not set
# CONFIG_BLK_DEV_PDC202XX_NEW is not set
# CONFIG_BLK_DEV_SVWKS is not set
# CONFIG_BLK_DEV_SIIMAGE is not set
# CONFIG_BLK_DEV_SIS5513 is not set
# CONFIG_BLK_DEV_SLC90E66 is not set
# CONFIG_BLK_DEV_TRM290 is not set
# CONFIG_BLK_DEV_VIA82CXXX is not set
# CONFIG_IDE_CHIPSETS is not set
CONFIG_BLK_DEV_IDEDMA=y
# CONFIG_IDEDMA_IVB is not set
CONFIG_IDEDMA_AUTO=y
# CONFIG_DMA_NONPCI is not set
# CONFIG_BLK_DEV_HD is not set

#
# SCSI device support
#
# CONFIG_SCSI is not set

#
# Old CD-ROM drivers (not SCSI, not IDE)
#
# CONFIG_CD_NO_IDESCSI is not set

#
# Multi-device support (RAID and LVM)
#
CONFIG_MD=y
# CONFIG_BLK_DEV_MD is not set
CONFIG_BLK_DEV_DM=y
CONFIG_DM_IOCTL_V4=y
CONFIG_DM_CRYPT=y

#
# Fusion MPT device support
#

#
# IEEE 1394 (FireWire) support (EXPERIMENTAL)
#
# CONFIG_IEEE1394 is not set

#
# I2O device support
#
# CONFIG_I2O is not set

#
# Macintosh device drivers
#

#
# Networking support
#
CONFIG_NET=y

#
# Networking options
#
CONFIG_PACKET=y
# CONFIG_PACKET_MMAP is not set
# CONFIG_NETLINK_DEV is not set
CONFIG_UNIX=y
CONFIG_NET_KEY=y
CONFIG_INET=y
CONFIG_IP_MULTICAST=y
# CONFIG_IP_ADVANCED_ROUTER is not set
# CONFIG_IP_PNP is not set
# CONFIG_NET_IPIP is not set
# CONFIG_NET_IPGRE is not set
# CONFIG_IP_MROUTE is not set
# CONFIG_ARPD is not set
# CONFIG_INET_ECN is not set
# CONFIG_SYN_COOKIES is not set
CONFIG_INET_AH=y
CONFIG_INET_ESP=y
CONFIG_INET_IPCOMP=y
# CONFIG_IPV6 is not set
# CONFIG_DECNET is not set
# CONFIG_BRIDGE is not set
# CONFIG_NETFILTER is not set
CONFIG_XFRM=y
# CONFIG_XFRM_USER is not set

#
# SCTP Configuration (EXPERIMENTAL)
#
CONFIG_IPV6_SCTP__=y
# CONFIG_IP_SCTP is not set
# CONFIG_ATM is not set
# CONFIG_VLAN_8021Q is not set
# CONFIG_LLC2 is not set
# CONFIG_IPX is not set
# CONFIG_ATALK is not set
# CONFIG_X25 is not set
# CONFIG_LAPB is not set
# CONFIG_NET_DIVERT is not set
# CONFIG_ECONET is not set
# CONFIG_WAN_ROUTER is not set
# CONFIG_NET_FASTROUTE is not set
# CONFIG_NET_HW_FLOWCONTROL is not set

#
# QoS and/or fair queueing
#
# CONFIG_NET_SCHED is not set

#
# Network testing
#
# CONFIG_NET_PKTGEN is not set
CONFIG_NETDEVICES=y

#
# ARCnet devices
#
# CONFIG_ARCNET is not set
CONFIG_DUMMY=y
# CONFIG_BONDING is not set
# CONFIG_EQUALIZER is not set
# CONFIG_TUN is not set

#
# Ethernet (10 or 100Mbit)
#
CONFIG_NET_ETHERNET=y
# CONFIG_MII is not set
# CONFIG_HAPPYMEAL is not set
# CONFIG_SUNGEM is not set
CONFIG_NET_VENDOR_3COM=y
# CONFIG_EL1 is not set
# CONFIG_EL2 is not set
# CONFIG_ELPLUS is not set
# CONFIG_EL16 is not set
# CONFIG_EL3 is not set
# CONFIG_3C515 is not set
CONFIG_VORTEX=y
# CONFIG_TYPHOON is not set
# CONFIG_LANCE is not set
# CONFIG_NET_VENDOR_SMC is not set
# CONFIG_NET_VENDOR_RACAL is not set

#
# Tulip family network device support
#
# CONFIG_NET_TULIP is not set
# CONFIG_AT1700 is not set
# CONFIG_DEPCA is not set
# CONFIG_HP100 is not set
# CONFIG_NET_ISA is not set
# CONFIG_NET_PCI is not set
# CONFIG_NET_POCKET is not set

#
# Ethernet (1000 Mbit)
#
# CONFIG_ACENIC is not set
# CONFIG_DL2K is not set
# CONFIG_E1000 is not set
# CONFIG_NS83820 is not set
# CONFIG_HAMACHI is not set
# CONFIG_YELLOWFIN is not set
# CONFIG_R8169 is not set
# CONFIG_SIS190 is not set
# CONFIG_SK98LIN is not set
# CONFIG_TIGON3 is not set

#
# Ethernet (10000 Mbit)
#
# CONFIG_IXGB is not set
# CONFIG_FDDI is not set
# CONFIG_HIPPI is not set
# CONFIG_PPP is not set
# CONFIG_SLIP is not set

#
# Wireless LAN (non-hamradio)
#
# CONFIG_NET_RADIO is not set

#
# Token Ring devices
#
# CONFIG_TR is not set
# CONFIG_RCPCI is not set
# CONFIG_SHAPER is not set
# CONFIG_NETCONSOLE is not set

#
# Wan interfaces
#
# CONFIG_WAN is not set

#
# Amateur Radio support
#
# CONFIG_HAMRADIO is not set

#
# IrDA (infrared) support
#
# CONFIG_IRDA is not set

#
# Bluetooth support
#
# CONFIG_BT is not set
# CONFIG_KGDBOE is not set
# CONFIG_NETPOLL is not set
# CONFIG_NETPOLL_RX is not set
# CONFIG_NETPOLL_TRAP is not set
# CONFIG_NET_POLL_CONTROLLER is not set

#
# ISDN subsystem
#
# CONFIG_ISDN is not set

#
# Telephony Support
#
# CONFIG_PHONE is not set

#
# Input device support
#
CONFIG_INPUT=y

#
# Userland interfaces
#
CONFIG_INPUT_MOUSEDEV=y
CONFIG_INPUT_MOUSEDEV_PSAUX=y
CONFIG_INPUT_MOUSEDEV_SCREEN_X=1024
CONFIG_INPUT_MOUSEDEV_SCREEN_Y=768
# CONFIG_INPUT_JOYDEV is not set
# CONFIG_INPUT_TSDEV is not set
# CONFIG_INPUT_EVDEV is not set
# CONFIG_INPUT_EVBUG is not set

#
# Input I/O drivers
#
# CONFIG_GAMEPORT is not set
CONFIG_SOUND_GAMEPORT=y
CONFIG_SERIO=y
CONFIG_SERIO_I8042=y
# CONFIG_SERIO_SERPORT is not set
# CONFIG_SERIO_CT82C710 is not set
# CONFIG_SERIO_PCIPS2 is not set

#
# Input Device Drivers
#
CONFIG_INPUT_KEYBOARD=y
CONFIG_KEYBOARD_ATKBD=y
# CONFIG_KEYBOARD_SUNKBD is not set
# CONFIG_KEYBOARD_XTKBD is not set
# CONFIG_KEYBOARD_NEWTON is not set
CONFIG_INPUT_MOUSE=y
CONFIG_MOUSE_PS2=y
# CONFIG_MOUSE_SERIAL is not set
# CONFIG_MOUSE_INPORT is not set
# CONFIG_MOUSE_LOGIBM is not set
# CONFIG_MOUSE_PC110PAD is not set
# CONFIG_INPUT_JOYSTICK is not set
# CONFIG_INPUT_TOUCHSCREEN is not set
# CONFIG_INPUT_MISC is not set

#
# Character devices
#
CONFIG_VT=y
CONFIG_VT_CONSOLE=y
CONFIG_HW_CONSOLE=y
# CONFIG_SERIAL_NONSTANDARD is not set

#
# Serial drivers
#
# CONFIG_SERIAL_8250 is not set

#
# Non-8250 serial port support
#
CONFIG_UNIX98_PTYS=y
CONFIG_LEGACY_PTYS=y
CONFIG_LEGACY_PTY_COUNT=256
# CONFIG_QIC02_TAPE is not set

#
# IPMI
#
# CONFIG_IPMI_HANDLER is not set

#
# Watchdog Cards
#
# CONFIG_WATCHDOG is not set
# CONFIG_HW_RANDOM is not set
# CONFIG_NVRAM is not set
# CONFIG_RTC is not set
# CONFIG_GEN_RTC is not set
# CONFIG_DTLK is not set
# CONFIG_R3964 is not set
# CONFIG_APPLICOM is not set
# CONFIG_SONYPI is not set

#
# Ftape, the floppy tape device driver
#
# CONFIG_FTAPE is not set
CONFIG_AGP=y
# CONFIG_AGP_ALI is not set
# CONFIG_AGP_ATI is not set
# CONFIG_AGP_AMD is not set
# CONFIG_AGP_AMD64 is not set
CONFIG_AGP_INTEL=y
# CONFIG_AGP_NVIDIA is not set
# CONFIG_AGP_SIS is not set
# CONFIG_AGP_SWORKS is not set
# CONFIG_AGP_VIA is not set
CONFIG_DRM=y
# CONFIG_DRM_TDFX is not set
# CONFIG_DRM_GAMMA is not set
# CONFIG_DRM_R128 is not set
# CONFIG_DRM_RADEON is not set
CONFIG_DRM_I810=y
# CONFIG_DRM_I830 is not set
# CONFIG_DRM_MGA is not set
# CONFIG_DRM_SIS is not set
# CONFIG_MWAVE is not set
# CONFIG_RAW_DRIVER is not set
# CONFIG_HANGCHECK_TIMER is not set

#
# I2C support
#
# CONFIG_I2C is not set

#
# Multimedia devices
#
# CONFIG_VIDEO_DEV is not set

#
# Digital Video Broadcasting Devices
#
# CONFIG_DVB is not set

#
# Graphics support
#
# CONFIG_FB is not set
# CONFIG_VIDEO_SELECT is not set

#
# Console display driver support
#
CONFIG_VGA_CONSOLE=y
# CONFIG_MDA_CONSOLE is not set
CONFIG_DUMMY_CONSOLE=y

#
# Sound
#
CONFIG_SOUND=y

#
# Advanced Linux Sound Architecture
#
CONFIG_SND=y
CONFIG_SND_SEQUENCER=y
# CONFIG_SND_SEQ_DUMMY is not set
CONFIG_SND_OSSEMUL=y
CONFIG_SND_MIXER_OSS=y
CONFIG_SND_PCM_OSS=y
CONFIG_SND_SEQUENCER_OSS=y
# CONFIG_SND_VERBOSE_PRINTK is not set
# CONFIG_SND_DEBUG is not set

#
# Generic devices
#
# CONFIG_SND_DUMMY is not set
# CONFIG_SND_VIRMIDI is not set
# CONFIG_SND_MTPAV is not set
# CONFIG_SND_SERIAL_U16550 is not set
# CONFIG_SND_MPU401 is not set

#
# ISA devices
#
# CONFIG_SND_AD1848 is not set
# CONFIG_SND_CS4231 is not set
# CONFIG_SND_CS4232 is not set
# CONFIG_SND_CS4236 is not set
# CONFIG_SND_ES1688 is not set
# CONFIG_SND_ES18XX is not set
# CONFIG_SND_GUSCLASSIC is not set
# CONFIG_SND_GUSEXTREME is not set
# CONFIG_SND_GUSMAX is not set
# CONFIG_SND_INTERWAVE is not set
# CONFIG_SND_INTERWAVE_STB is not set
# CONFIG_SND_OPTI92X_AD1848 is not set
# CONFIG_SND_OPTI92X_CS4231 is not set
# CONFIG_SND_OPTI93X is not set
# CONFIG_SND_SB8 is not set
# CONFIG_SND_SB16 is not set
# CONFIG_SND_SBAWE is not set
# CONFIG_SND_WAVEFRONT is not set
# CONFIG_SND_CMI8330 is not set
# CONFIG_SND_OPL3SA2 is not set
# CONFIG_SND_SGALAXY is not set
# CONFIG_SND_SSCAPE is not set

#
# PCI devices
#
# CONFIG_SND_ALI5451 is not set
# CONFIG_SND_AZT3328 is not set
# CONFIG_SND_BT87X is not set
# CONFIG_SND_CS46XX is not set
# CONFIG_SND_CS4281 is not set
# CONFIG_SND_EMU10K1 is not set
# CONFIG_SND_KORG1212 is not set
# CONFIG_SND_NM256 is not set
# CONFIG_SND_RME32 is not set
# CONFIG_SND_RME96 is not set
# CONFIG_SND_RME9652 is not set
# CONFIG_SND_HDSP is not set
# CONFIG_SND_TRIDENT is not set
# CONFIG_SND_YMFPCI is not set
# CONFIG_SND_ALS4000 is not set
# CONFIG_SND_CMIPCI is not set
# CONFIG_SND_ENS1370 is not set
# CONFIG_SND_ENS1371 is not set
# CONFIG_SND_ES1938 is not set
# CONFIG_SND_ES1968 is not set
# CONFIG_SND_MAESTRO3 is not set
# CONFIG_SND_FM801 is not set
# CONFIG_SND_ICE1712 is not set
# CONFIG_SND_ICE1724 is not set
CONFIG_SND_INTEL8X0=y
# CONFIG_SND_SONICVIBES is not set
# CONFIG_SND_VIA82XX is not set
# CONFIG_SND_VX222 is not set

#
# Open Sound System
#
# CONFIG_SOUND_PRIME is not set

#
# USB support
#
# CONFIG_USB is not set

#
# USB Gadget Support
#
# CONFIG_USB_GADGET is not set

#
# File systems
#
CONFIG_EXT2_FS=y
# CONFIG_EXT2_FS_XATTR is not set
CONFIG_EXT3_FS=y
# CONFIG_EXT3_FS_XATTR is not set
CONFIG_JBD=y
# CONFIG_JBD_DEBUG is not set
# CONFIG_REISERFS_FS is not set
# CONFIG_JFS_FS is not set
# CONFIG_XFS_FS is not set
# CONFIG_MINIX_FS is not set
# CONFIG_ROMFS_FS is not set
# CONFIG_QUOTA is not set
# CONFIG_AUTOFS_FS is not set
# CONFIG_AUTOFS4_FS is not set

#
# CD-ROM/DVD Filesystems
#
CONFIG_ISO9660_FS=y
CONFIG_JOLIET=y
# CONFIG_ZISOFS is not set
CONFIG_UDF_FS=y

#
# DOS/FAT/NT Filesystems
#
CONFIG_FAT_FS=y
CONFIG_MSDOS_FS=y
CONFIG_VFAT_FS=y
# CONFIG_NTFS_FS is not set

#
# Pseudo filesystems
#
CONFIG_PROC_FS=y
CONFIG_PROC_KCORE=y
CONFIG_SYSFS=y
# CONFIG_DEVFS_FS is not set
# CONFIG_DEVPTS_FS_XATTR is not set
CONFIG_TMPFS=y
# CONFIG_HUGETLBFS is not set
# CONFIG_HUGETLB_PAGE is not set
CONFIG_RAMFS=y

#
# Miscellaneous filesystems
#
# CONFIG_ADFS_FS is not set
# CONFIG_AFFS_FS is not set
# CONFIG_HFS_FS is not set
# CONFIG_BEFS_FS is not set
# CONFIG_BFS_FS is not set
# CONFIG_EFS_FS is not set
# CONFIG_CRAMFS is not set
# CONFIG_VXFS_FS is not set
# CONFIG_HPFS_FS is not set
# CONFIG_QNX4FS_FS is not set
# CONFIG_SYSV_FS is not set
# CONFIG_UFS_FS is not set

#
# Network File Systems
#
# CONFIG_NFS_FS is not set
# CONFIG_NFSD is not set
# CONFIG_EXPORTFS is not set
# CONFIG_SMB_FS is not set
# CONFIG_CIFS is not set
# CONFIG_NCP_FS is not set
# CONFIG_CODA_FS is not set
# CONFIG_AFS_FS is not set

#
# Partition Types
#
# CONFIG_PARTITION_ADVANCED is not set
CONFIG_MSDOS_PARTITION=y

#
# Native Language Support
#
CONFIG_NLS=y
CONFIG_NLS_DEFAULT="iso8859-1"
CONFIG_NLS_CODEPAGE_437=y
# CONFIG_NLS_CODEPAGE_737 is not set
# CONFIG_NLS_CODEPAGE_775 is not set
# CONFIG_NLS_CODEPAGE_850 is not set
# CONFIG_NLS_CODEPAGE_852 is not set
# CONFIG_NLS_CODEPAGE_855 is not set
# CONFIG_NLS_CODEPAGE_857 is not set
# CONFIG_NLS_CODEPAGE_860 is not set
# CONFIG_NLS_CODEPAGE_861 is not set
# CONFIG_NLS_CODEPAGE_862 is not set
# CONFIG_NLS_CODEPAGE_863 is not set
# CONFIG_NLS_CODEPAGE_864 is not set
# CONFIG_NLS_CODEPAGE_865 is not set
# CONFIG_NLS_CODEPAGE_866 is not set
# CONFIG_NLS_CODEPAGE_869 is not set
# CONFIG_NLS_CODEPAGE_936 is not set
# CONFIG_NLS_CODEPAGE_950 is not set
# CONFIG_NLS_CODEPAGE_932 is not set
# CONFIG_NLS_CODEPAGE_949 is not set
# CONFIG_NLS_CODEPAGE_874 is not set
# CONFIG_NLS_ISO8859_8 is not set
# CONFIG_NLS_CODEPAGE_1250 is not set
# CONFIG_NLS_CODEPAGE_1251 is not set
CONFIG_NLS_ISO8859_1=y
# CONFIG_NLS_ISO8859_2 is not set
# CONFIG_NLS_ISO8859_3 is not set
# CONFIG_NLS_ISO8859_4 is not set
# CONFIG_NLS_ISO8859_5 is not set
# CONFIG_NLS_ISO8859_6 is not set
# CONFIG_NLS_ISO8859_7 is not set
# CONFIG_NLS_ISO8859_9 is not set
# CONFIG_NLS_ISO8859_13 is not set
# CONFIG_NLS_ISO8859_14 is not set
# CONFIG_NLS_ISO8859_15 is not set
# CONFIG_NLS_KOI8_R is not set
# CONFIG_NLS_KOI8_U is not set
# CONFIG_NLS_UTF8 is not set

#
# Profiling support
#
# CONFIG_PROFILING is not set

#
# Kernel hacking
#
# CONFIG_DEBUG_KERNEL is not set
CONFIG_EARLY_PRINTK=y
# CONFIG_DEBUG_SPINLOCK_SLEEP is not set
# CONFIG_FRAME_POINTER is not set

#
# Security options
#
# CONFIG_SECURITY is not set

#
# Cryptographic options
#
CONFIG_CRYPTO=y
CONFIG_CRYPTO_HMAC=y
CONFIG_CRYPTO_NULL=y
CONFIG_CRYPTO_MD4=y
CONFIG_CRYPTO_MD5=y
CONFIG_CRYPTO_SHA1=y
CONFIG_CRYPTO_SHA256=y
CONFIG_CRYPTO_SHA512=y
CONFIG_CRYPTO_DES=y
CONFIG_CRYPTO_BLOWFISH=y
CONFIG_CRYPTO_TWOFISH=y
CONFIG_CRYPTO_SERPENT=y
CONFIG_CRYPTO_AES=y
CONFIG_CRYPTO_CAST5=y
CONFIG_CRYPTO_CAST6=y
CONFIG_CRYPTO_DEFLATE=y
# CONFIG_CRYPTO_TEST is not set

#
# Library routines
#
# CONFIG_CRC32 is not set
CONFIG_ZLIB_INFLATE=y
CONFIG_ZLIB_DEFLATE=y
CONFIG_X86_BIOS_REBOOT=y
CONFIG_PC=y

Re: 2.6.3-mm1

[Jonathan Brown]

When I try to startx with this kernel I get this error:

(EE) RADEON(0): shmat() call retruned errno 1013

No problem with similar .config on 2.6.3. Can post .config if necessary.

Jonathan Brown
http://emergence.uk.net/


Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm1/
> 
> - Added the dm-crypt driver: a crypto layer for device-mapper.
> 
>   People need to test and use this please.  There is documentation at
>   http://www.saout.de/misc/dm-crypt/.
> 
>   We should get this tested and merged up.  We can then remove the nasty
>   bio remapping code from the loop driver.  This will remove the current
>   ordering guarantees which the loop driver provides for journalled
>   filesystems.  ie: ext3 on cryptoloop will no longer be crash-proof.
> 
>   After that we should remove cryptoloop altogether.
> 
>   It's a bit late but cyptoloop hasn't been there for long anyway and it
>   doesn't even work right with highmem systems (that part is fixed in -mm).
> 
> - Added the fbdev cursor API patch.  Not sure what this does apart from
>   preventing the rivafb driver from linking.  I'll let others decide if this
>   is progress.
> 
> - There's a patch here to consolidate the 32->64 compat code for the IPC
>   syscalls.  Needs testing on various 64-bit machines.
> 
> - Various random fixes to things.

Re: 2.6.3-mm1

[Sean Neakums]

Jonathan Brown <jbrown@emergence.uk.net> writes:

> When I try to startx with this kernel I get this error:
>
> (EE) RADEON(0): shmat() call retruned errno 1013
>
> No problem with similar .config on 2.6.3. Can post .config if necessary.


I think you need to apply the third patch below, although all three
should probably be applied.


Date:	Wed, 18 Feb 2004 01:25:53 -0800
From:	Andrew Morton <akpm@osdl.org>
To:	linux-kernel@vger.kernel.org, rusty@rustcorp.com.au
Subject: Re: 2.6.3-mm1
Message-Id: <20040218012553.1228ae34.akpm@osdl.org>

Andrew Morton <akpm@osdl.org> wrote:
>
> Andrew Morton <akpm@osdl.org> wrote:
>  >
>  > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm1/
> 
>  oops, it appears that rmmod hangs in D state all the time.  

Fixes:


 kernel/stop_machine.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN kernel/stop_machine.c~hotplugcpu-generalise-bogolock-fix-for-kthread-stop-using-signals kernel/stop_machine.c
--- 25/kernel/stop_machine.c~hotplugcpu-generalise-bogolock-fix-for-kthread-stop-using-signals	2004-02-18 01:14:27.000000000 -0800
+++ 25-akpm/kernel/stop_machine.c	2004-02-18 01:14:54.000000000 -0800
@@ -148,7 +148,7 @@ static int do_stop(void *_smdata)
 	complete(&smdata->done);
 
 	/* Wait for kthread_stop */
-	while (!signal_pending(current)) {
+	while (!kthread_should_stop()) {
 		__set_current_state(TASK_INTERRUPTIBLE);
 		schedule();
 	}

_


 kernel/softirq.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN kernel/softirq.c~hotplugcpu-core-fix-for-kthread-stop-using-signals kernel/softirq.c
--- 25/kernel/softirq.c~hotplugcpu-core-fix-for-kthread-stop-using-signals	2004-02-18 01:19:14.000000000 -0800
+++ 25-akpm/kernel/softirq.c	2004-02-18 01:19:29.000000000 -0800
@@ -349,7 +349,7 @@ static int ksoftirqd(void * __bind_cpu)
 wait_to_die:
 	preempt_enable();
 	/* Wait for kthread_stop */
-	while (!signal_pending(current)) {
+	while (!kthread_should_stop()) {
 		__set_current_state(TASK_INTERRUPTIBLE);
 		schedule();
 	}

_


 ipc/shm.c |    2 +-
 1 files changed, 1 insertion(+), 1 deletion(-)

diff -puN ipc/shm.c~add-syscalls_h-shmat-fix ipc/shm.c
--- 25/ipc/shm.c~add-syscalls_h-shmat-fix	2004-02-18 01:22:41.000000000 -0800
+++ 25-akpm/ipc/shm.c	2004-02-18 01:22:41.000000000 -0800
@@ -635,7 +635,7 @@ out:
  * "raddr" thing points to kernel space, and there has to be a wrapper around
  * this.
  */
-long sys_shmat(int shmid, char __user *shmaddr, int shmflg, ulong *raddr)
+asmlinkage long sys_shmat(int shmid, char __user *shmaddr, int shmflg, ulong *raddr)
 {
 	struct shmid_kernel *shp;
 	unsigned long addr;

_

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

dmcrypt works well on 2.6.3 WAS: Re: 2.6.3-mm1

[bert hubert]

>   People need to test and use this please.  There is documentation at
>   http://www.saout.de/misc/dm-crypt/.

Works amazingly well. Starting from stock 2.6.3 I applied 'dm*' from the
broken out 2.6.3-mm1, no fuzz or offset, and ran make on the kernel I had
built this morning.

I then turned on the device mapper and its crypto support and loaded the
modules, without rebooting.

Downloaded ftp://ftp.sistina.com/pub/LVM2/device-mapper/device-mapper-latest.tgz
	./configure && make && sudo make install
	sudo ./scripts/devmap_mknod.sh (to create /dev/mapper)
Downloaded http://www.stwing.org/~sluskyb/util-linux/hashalot-0.2.0.tar.gz
	./configure && make && sudo make install	
Downloaded http://www.saout.de/misc/cryptsetup
	ran: cryptsetup -h plain create crypted /dev/hdb1
  		(the -h plain isn't necessary, I didn't have hashalot
		 earlier, and even with -h plain it wants hashalot)
		entered a passphrase (already forgotten though)
	e2fsck /dev/mapper/crypted
	mount /dev/mapper/crypted /mnt

mke2fs proved to be a significant CPU load (all sy) and took a minute or two
to run, which could be forgiven, it had to mke2fs 200G.

I then copied the entire Linux build tree to /mnt, ran make clean, make, and
12 minutes later I had a new kernel. System load was below <10% at all
times, mostly <5%.

Then I did the whole thing again but then with ext3, which worked too. System
load appeared slightly higher, the build however took 12 minutes as well.

Kudos!

Suggestions 
-----------
1) Add a reference to the hashalot location to
   http://www.saout.de/misc/dm-crypt/ and add some units to 'cryptsetup',
   something like this (probably tab/space damaged):

--- cryptsetup  2003-12-26 21:27:08.000000000 +0100
+++ cryptsetup.ahu      2004-02-18 12:46:18.000000000 +0100
@@ -229,10 +229,10 @@
                gettable "$NAME"
                echo "$DMPATH$NAME is active:"
                echo "  cipher:  $CIPHER"
-               echo "  keysize: $[${#KEY}/2]"
+               echo "  keysize: $[${#KEY}/2] bytes"
                echo "  device:  $DEVICE"
                echo "  offset:  $SKIPPED"
-               echo "  size:    $SIZE"
+               echo "  size:    $SIZE sectors"
                [ $SKIPPED -gt 0 ] && echo "   skipped: $SKIPPED"
                unset KEY
        else

  The output can be mighty confusing otherwise.

2) Remove dependence on hashalot for -h plain
3) Add pointer to hashalot on the main page
4) make make install of the device mapper userspace run the mknod script

>   filesystems.  ie: ext3 on cryptoloop will no longer be crash-proof.
(...)
>   After that we should remove cryptoloop altogether.

Big fat warnings might be wise in the meantime. I sincerely hope that 
dm-crypt can be merged sooner rather than later. It feels good and it Just
Works.

Thanks!

-- 
http://www.PowerDNS.com      Open source, database driven DNS Software 
http://lartc.org           Linux Advanced Routing & Traffic Control HOWTO

Re: 2.6.3-mm1

[Ramon Rey Vicente]

[-- Attachment #1: Type: text/plain, Size: 535 bytes --]

Hi,

With ACPI disabled and APM enabled I get this build error.

arch/i386/kernel/built-in.o(.text+0xbf3a): In function `acpi_apic_setup':
: undefined reference to `smp_found_config'
arch/i386/kernel/built-in.o(.text+0xbf43): In function `acpi_apic_setup':
: undefined reference to `clustered_apic_check'
make: *** [.tmp_vmlinux1] Error 1
-- 
Ramón Rey Vicente       <ramon dot rey at hispalinux dot es>
        jabber ID       <rreylinux at jabber dot org>
GPG public key ID 	0xBEBD71D5 -> http://pgp.escomposlinux.org/

[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: 2.6.3-mm1

[Andrew Morton]

Ramon Rey Vicente <rrey@ranty.pantax.net> wrote:
>
> Hi,
> 
> With ACPI disabled and APM enabled I get this build error.
> 
> arch/i386/kernel/built-in.o(.text+0xbf3a): In function `acpi_apic_setup':
> : undefined reference to `smp_found_config'
> arch/i386/kernel/built-in.o(.text+0xbf43): In function `acpi_apic_setup':
> : undefined reference to `clustered_apic_check'
> make: *** [.tmp_vmlinux1] Error 1

The fickle finger of fate points at expanded-pci-config-space.patch

Re: 2.6.3-mm1

[Matthew Wilcox]

On Wed, Feb 18, 2004 at 10:55:55AM -0800, Andrew Morton wrote:
> Ramon Rey Vicente <rrey@ranty.pantax.net> wrote:
> >
> > Hi,
> > 
> > With ACPI disabled and APM enabled I get this build error.
> > 
> > arch/i386/kernel/built-in.o(.text+0xbf3a): In function `acpi_apic_setup':
> > : undefined reference to `smp_found_config'
> > arch/i386/kernel/built-in.o(.text+0xbf43): In function `acpi_apic_setup':
> > : undefined reference to `clustered_apic_check'
> > make: *** [.tmp_vmlinux1] Error 1
> 
> The fickle finger of fate points at expanded-pci-config-space.patch

It does indeed.  The patch I posted earlier today
(http://www.ussg.iu.edu/hypermail/linux/kernel/0402.2/0770.html) fixes it.
I've got some more updates for this patch coming shortly, BTW.  If anyone
wants a quick workaround, you can just turn on Local APIC and the problem
will disappear.

-- 
"Next the statesmen will invent cheap lies, putting the blame upon 
the nation that is attacked, and every man will be glad of those
conscience-soothing falsities, and will diligently study them, and refuse
to examine any refutations of them; and thus he will by and by convince 
himself that the war is just, and will thank God for the better sleep 
he enjoys after this process of grotesque self-deception." -- Mark Twain

Re: 2.6.3-mm1

[Bill Davidsen]

Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm1/
> 
> - Added the dm-crypt driver: a crypto layer for device-mapper.
> 
>   People need to test and use this please.  There is documentation at
>   http://www.saout.de/misc/dm-crypt/.
> 
>   We should get this tested and merged up.  We can then remove the nasty
>   bio remapping code from the loop driver.  This will remove the current
>   ordering guarantees which the loop driver provides for journalled
>   filesystems.  ie: ext3 on cryptoloop will no longer be crash-proof.
> 
>   After that we should remove cryptoloop altogether.
> 
>   It's a bit late but cyptoloop hasn't been there for long anyway and it
>   doesn't even work right with highmem systems (that part is fixed in -mm).

What definition of "stable kernel" do you use which includes removal of 
features which were reasons to migrate to 2.6 from 2.4? This change 
would mean having to add dm to the kernel which otherwise doesn't use 
it, carry dm utilities on the system whcih are otherwise unneeded, and 
train people to use and not use dm.

I expect major things to change in a development series, but less major 
things than this have been pushed to 2.7, why is this being forced in?

-- 
bill davidsen <davidsen@tmr.com>
   CTO TMR Associates, Inc
   Doing interesting things with small computers since 1979

Re: 2.6.3-mm1

[Brandon Low]

On Wed, 02/18/04 at 11:16:40 -0500, Bill Davidsen wrote:
> Andrew Morton wrote:
> >ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm1/
> >
> >- Added the dm-crypt driver: a crypto layer for device-mapper.
> >
> >  People need to test and use this please.  There is documentation at
> >  http://www.saout.de/misc/dm-crypt/.
> >
> >  We should get this tested and merged up.  We can then remove the nasty
> >  bio remapping code from the loop driver.  This will remove the current
> >  ordering guarantees which the loop driver provides for journalled
> >  filesystems.  ie: ext3 on cryptoloop will no longer be crash-proof.
> >
> >  After that we should remove cryptoloop altogether.
> >
> >  It's a bit late but cyptoloop hasn't been there for long anyway and it
> >  doesn't even work right with highmem systems (that part is fixed in -mm).
> 
> What definition of "stable kernel" do you use which includes removal of 
> features which were reasons to migrate to 2.6 from 2.4? This change 
> would mean having to add dm to the kernel which otherwise doesn't use 
> it, carry dm utilities on the system whcih are otherwise unneeded, and 
> train people to use and not use dm.
> 
> I expect major things to change in a development series, but less major 
> things than this have been pushed to 2.7, why is this being forced in?
>
I must add my voice here in strong opposition of the removal of
cryptoloop from the 2.6 series of kernels.  This is no longer a
development series kernel, I (and others, I'm sure) have been working on
developing technologies which depend on this functionality and which
would be _very_ annoying to do with DM (liveCD-on-cryptoloop-on-iso).

Please do not drop cryptoloop!

Thanks,
--
Brandon Low
Release Coordinator
Ribstone Systems
http://www.ribstonesystems.com

Re: 2.6.3-mm1

[Andrew Morton]

Brandon Low <blow@rbsys.com> wrote:
>
> I must add my voice here in strong opposition of the removal of
>  cryptoloop from the 2.6 series of kernels.  This is no longer a
>  development series kernel, I (and others, I'm sure) have been working on
>  developing technologies which depend on this functionality and which
>  would be _very_ annoying to do with DM (liveCD-on-cryptoloop-on-iso).

Why is it problematic?

>  Please do not drop cryptoloop!

ho-hum.  Why should we retain crypto capabilities which have widely
understood vulnerabilities?

We mainly want to remove the bio remapping stuff from the loop driver
because it's horrid and deadlocks under heavy memory pressure.  Maybe we
can leave crytoloop there with big "kindergarten crypto - do not use"
labels all over it.

Re: 2.6.3-mm1

[Brandon Low]

On Wed, 02/18/04 at 12:22:16 -0800, Andrew Morton wrote:
> Brandon Low <blow@rbsys.com> wrote:
> >
> > I must add my voice here in strong opposition of the removal of
> >  cryptoloop from the 2.6 series of kernels.  This is no longer a
> >  development series kernel, I (and others, I'm sure) have been working on
> >  developing technologies which depend on this functionality and which
> >  would be _very_ annoying to do with DM (liveCD-on-cryptoloop-on-iso).
> 
> Why is it problematic?
> 
Involves taking up precious CD space with the DM tools and modules...

Besides, this isn't really the point, the point is that the new dmcrypto
is only in -mm and cryptoloop is in both trees, those of us developing
applications based on cryptoloop don't have a mainline kernel to even
start testing dmcrypto against in the 2.6 series, so it is more a
political issue than a technical issue which makes the removal of a
feature like this from the 2.6 series a bad thing...  (In my humble
never contributed to the kernel opinion)

Technically speaking there is no doubt that you are correct to want to
remove cryptoloop... but if people are depending on that support to stay
in a stable kernel and are developing based on it and don't have the
time to learn dm or dmcrypto and redesign whatever may need redesigning
to use it, it strikes me as rude to pull that support.

> >  Please do not drop cryptoloop!
> 
> ho-hum.  Why should we retain crypto capabilities which have widely
> understood vulnerabilities?
> 
> We mainly want to remove the bio remapping stuff from the loop driver
> because it's horrid and deadlocks under heavy memory pressure.  Maybe we
> can leave crytoloop there with big "kindergarten crypto - do not use"
> labels all over it.
> 
DEPRECATED would probably do...

--
Brandon Low
Release Manager
Ribstone Systems
http://www.ribstonesystems.com

Re: 2.6.3-mm1

[Andrew Morton]

Brandon Low <lostlogic@gentoo.org> wrote:
>
> but if people are depending on that support to stay
>  in a stable kernel and are developing based on it and don't have the
>  time to learn dm or dmcrypto and redesign whatever may need redesigning
>  to use it, it strikes me as rude to pull that support.

This is actually an argument for removing cryptolooop.  People are
developing against a crypto infrastructure which has well-known weaknesses.

Pulling it out is an excellent way of communicating this fact.  Right now,
we're just deluding people.

Re: 2.6.3-mm1

[Brandon Low]

On Wed, 02/18/04 at 12:52:27 -0800, Andrew Morton wrote:
> Brandon Low <lostlogic@gentoo.org> wrote:
> >
> > but if people are depending on that support to stay
> >  in a stable kernel and are developing based on it and don't have the
> >  time to learn dm or dmcrypto and redesign whatever may need redesigning
> >  to use it, it strikes me as rude to pull that support.
> 
> This is actually an argument for removing cryptolooop.  People are
> developing against a crypto infrastructure which has well-known weaknesses.
> 
> Pulling it out is an excellent way of communicating this fact.  Right now,
> we're just deluding people.

Unfortunately, you have a valid point... I don't like it, because it
means work for me, but it is a valid point... 

I am just reading up on dm now, but correct me if I am wrong, I will
need to do losetup, dmcreate, mount in that order in order to use
dmcrypt on loop where with cryptoloop, I could just do "mount"... there
must be an easier way to handle this!

Thanks,

Brandon

Re: 2.6.3-mm1

[Andrew Morton]

Brandon Low <lostlogic@gentoo.org> wrote:
>
> I am just reading up on dm now, but correct me if I am wrong, I will
> need to do losetup, dmcreate, mount in that order in order to use
> dmcrypt on loop where with cryptoloop, I could just do "mount"... there
> must be an easier way to handle this!

See Bert's email from eariler today:



Date: Wed, 18 Feb 2004 13:14:16 +0100
From: bert hubert <ahu@ds9a.nl>

>   People need to test and use this please.  There is documentation at
>   http://www.saout.de/misc/dm-crypt/.

Works amazingly well. Starting from stock 2.6.3 I applied 'dm*' from the
broken out 2.6.3-mm1, no fuzz or offset, and ran make on the kernel I had
built this morning.

I then turned on the device mapper and its crypto support and loaded the
modules, without rebooting.

Downloaded ftp://ftp.sistina.com/pub/LVM2/device-mapper/device-mapper-latest.tgz
	./configure && make && sudo make install
	sudo ./scripts/devmap_mknod.sh (to create /dev/mapper)
Downloaded http://www.stwing.org/~sluskyb/util-linux/hashalot-0.2.0.tar.gz
	./configure && make && sudo make install	
Downloaded http://www.saout.de/misc/cryptsetup
	ran: cryptsetup -h plain create crypted /dev/hdb1
  		(the -h plain isn't necessary, I didn't have hashalot
		 earlier, and even with -h plain it wants hashalot)
		entered a passphrase (already forgotten though)
	e2fsck /dev/mapper/crypted
	mount /dev/mapper/crypted /mnt

mke2fs proved to be a significant CPU load (all sy) and took a minute or two
to run, which could be forgiven, it had to mke2fs 200G.

I then copied the entire Linux build tree to /mnt, ran make clean, make, and
12 minutes later I had a new kernel. System load was below <10% at all
times, mostly <5%.

Then I did the whole thing again but then with ext3, which worked too. System
load appeared slightly higher, the build however took 12 minutes as well.

Kudos!

Suggestions 
-----------
1) Add a reference to the hashalot location to
   http://www.saout.de/misc/dm-crypt/ and add some units to 'cryptsetup',
   something like this (probably tab/space damaged):

--- cryptsetup  2003-12-26 21:27:08.000000000 +0100
+++ cryptsetup.ahu      2004-02-18 12:46:18.000000000 +0100
@@ -229,10 +229,10 @@
                gettable "$NAME"
                echo "$DMPATH$NAME is active:"
                echo "  cipher:  $CIPHER"
-               echo "  keysize: $[${#KEY}/2]"
+               echo "  keysize: $[${#KEY}/2] bytes"
                echo "  device:  $DEVICE"
                echo "  offset:  $SKIPPED"
-               echo "  size:    $SIZE"
+               echo "  size:    $SIZE sectors"
                [ $SKIPPED -gt 0 ] && echo "   skipped: $SKIPPED"
                unset KEY
        else

  The output can be mighty confusing otherwise.

2) Remove dependence on hashalot for -h plain
3) Add pointer to hashalot on the main page
4) make make install of the device mapper userspace run the mknod script

>   filesystems.  ie: ext3 on cryptoloop will no longer be crash-proof.
(...)
>   After that we should remove cryptoloop altogether.

Big fat warnings might be wise in the meantime. I sincerely hope that 
dm-crypt can be merged sooner rather than later. It feels good and it Just
Works.

Re: 2.6.3-mm1

[Christophe Saout]

Am Mi, den 18.02.2004 schrieb Brandon Low um 21:52:

> I am just reading up on dm now, but correct me if I am wrong, I will
> need to do losetup, dmcreate, mount in that order in order to use
> dmcrypt on loop where with cryptoloop, I could just do "mount"... there
> must be an easier way to handle this!

You don't need to know everything about dm to set up encrypted devices.

Basically dmsetup is something like losetup, only that it's much more
flexible.

To set up a device basically:

echo 0 `blockdev --getsize /dev/bla` crypt <cipher> <key> 0 /dev/bla 0 |
dmsetup create <newname>

is enough. And it's just temporary, because no special tool has been
written yet. dmsetup is the most low-level dm tool, mostly for
developers. I've written a shell script named cryptsetup for the
meantime, it asks for a passphrase and does all the magic you need.

"cryptsetup create test /dev/hda5" will ask for a passphrase and set up
/dev/mapper/test. Voila. "cryptsetup remove test" removes it and
"cryptsetup status test" shows some status information.

mount -o loop is basically a hack. mount uses parts of losetup to do an
ioctl. The encryption support as mount argument is an additional patch.
Even worse, some do passphrase hashing, some don't... it works but it's
not a very clean solution either.

BTW: dmsetup is NOT a big program. It has two parts: a libdevmapper.so
in /lib and the dmsetup binary itself. Every part is 16k in size (if
compiled statically into one binary it's just 27k), and it's still
linked against glibc. If linked against dietlibc or klibc it would be
even smaller. Nobody needs LVM tools or something. It's just a small
client for the dm ioctl, just like losetup is a client for the loop
ioctl.

There are some plans to write a unified plugin based key management
tool. You might want to have your key stored on a USB stick. Or
encrypted in the first sector of your device and you want to unlock it
using a password (so you can change your password without needing to
reencrypt your data). This would be much more flexible than most of the
crap floating around.

So, you see. NO NEED TO PANIC. Cryptoloop won't disappear over night.
There will be some nice to user interface. At the moment dm-crypt is
only a *kernel implementation* and not meant to be used by every end
user immediately. Nobody will force you to drop cryptoloop until there
is a clean solution for everybody out there.

Re: 2.6.3-mm1

[Brandon Low]

On Wed, 02/18/04 at 23:15:37 +0100, Christophe Saout wrote:
> Am Mi, den 18.02.2004 schrieb Brandon Low um 21:52:
> 
> > I am just reading up on dm now, but correct me if I am wrong, I will
> > need to do losetup, dmcreate, mount in that order in order to use
> > dmcrypt on loop where with cryptoloop, I could just do "mount"... there
> > must be an easier way to handle this!
> 
> You don't need to know everything about dm to set up encrypted devices.
> 
> Basically dmsetup is something like losetup, only that it's much more
> flexible.
> 
> To set up a device basically:
> 
> echo 0 `blockdev --getsize /dev/bla` crypt <cipher> <key> 0 /dev/bla 0 |
> dmsetup create <newname>
> 
> is enough. And it's just temporary, because no special tool has been
> written yet. dmsetup is the most low-level dm tool, mostly for
> developers. I've written a shell script named cryptsetup for the
> meantime, it asks for a passphrase and does all the magic you need.
> 
> "cryptsetup create test /dev/hda5" will ask for a passphrase and set up
> /dev/mapper/test. Voila. "cryptsetup remove test" removes it and
> "cryptsetup status test" shows some status information.
> 
What I can't figure out yet is how to do that easily for a loopback...
use losetup first, and then cryptsetup?  I guess that's ok, just more
steps than I would prefer.

> mount -o loop is basically a hack. mount uses parts of losetup to do an
> ioctl. The encryption support as mount argument is an additional patch.
> Even worse, some do passphrase hashing, some don't... it works but it's
> not a very clean solution either.
> 
> BTW: dmsetup is NOT a big program. It has two parts: a libdevmapper.so
> in /lib and the dmsetup binary itself. Every part is 16k in size (if
> compiled statically into one binary it's just 27k), and it's still
> linked against glibc. If linked against dietlibc or klibc it would be
> even smaller. Nobody needs LVM tools or something. It's just a small
> client for the dm ioctl, just like losetup is a client for the loop
> ioctl.
> 
I was under the mistaken impression that I would need lvmtools as well
in order to use dmcrypt... cool.

> There are some plans to write a unified plugin based key management
> tool. You might want to have your key stored on a USB stick. Or
> encrypted in the first sector of your device and you want to unlock it
> using a password (so you can change your password without needing to
> reencrypt your data). This would be much more flexible than most of the
> crap floating around.

That sounds very cool, saw mention of putting it in the first part of
the device elsethread.
> 
> So, you see. NO NEED TO PANIC. Cryptoloop won't disappear over night.
> There will be some nice to user interface. At the moment dm-crypt is
> only a *kernel implementation* and not meant to be used by every end
> user immediately. Nobody will force you to drop cryptoloop until there
> is a clean solution for everybody out there.
> 
Ok ok, I'll quit panicking... this just makes it hard to decide which to
use now as I'm preparing to deploy soon... If I use cryptoloop, it is
now guaranteed to be obsolete soon, but if I use dmcrypt, it is more
work right now, but more forward looking... 

Can you point me to some useful readings related to dmcrypt,
devicemapper for loopback, etc.? Thanks!

--Brandon

Re: 2.6.3-mm1

[Christophe Saout]

Am Do, den 19.02.2004 schrieb Brandon Low um 01:33:

> > To set up a device basically:
> > 
> > echo 0 `blockdev --getsize /dev/bla` crypt <cipher> <key> 0 /dev/bla 0 |
> > dmsetup create <newname>
> > 
> > is enough. And it's just temporary, because no special tool has been
> > written yet. dmsetup is the most low-level dm tool, mostly for
> > developers. I've written a shell script named cryptsetup for the
> > meantime, it asks for a passphrase and does all the magic you need.
> > 
> > "cryptsetup create test /dev/hda5" will ask for a passphrase and set up
> > /dev/mapper/test. Voila. "cryptsetup remove test" removes it and
> > "cryptsetup status test" shows some status information.
> > 
> What I can't figure out yet is how to do that easily for a loopback...
> use losetup first, and then cryptsetup?  I guess that's ok, just more
> steps than I would prefer.

Yes. Block->File and Block->Crypto->Block are two different things and
should be separated out. But it would be an easy one to make cryptsetup
also call losetup if your specified backend happens to be a file. Like
mount -o loop does. The only thing I'm not sure about: How would it know
when to remove the loop device on "cryptsetup remove" and when now.
mount stores it in the mtab.

I've got some free time, I think I'm going to rewrite cryptsetup as a
small C program today.

> I was under the mistaken impression that I would need lvmtools as well
> in order to use dmcrypt... cool.

Yes, there's some FUD going around...

> > There are some plans to write a unified plugin based key management
> > tool. You might want to have your key stored on a USB stick. Or
> > encrypted in the first sector of your device and you want to unlock it
> > using a password (so you can change your password without needing to
> > reencrypt your data). This would be much more flexible than most of the
> > crap floating around.
> 
> That sounds very cool, saw mention of putting it in the first part of
> the device elsethread.

Yes, for example.

> Ok ok, I'll quit panicking... this just makes it hard to decide which to
> use now as I'm preparing to deploy soon... If I use cryptoloop, it is
> now guaranteed to be obsolete soon, but if I use dmcrypt, it is more
> work right now, but more forward looking... 
> 
> Can you point me to some useful readings related to dmcrypt,
> devicemapper for loopback, etc.? Thanks!

For dm-crypt I've set up a small page:
http://www.saout.de/misc/dm-crypt/

For device-mapper and loopback there's nothing. The loop device provides
block devices, device-mapper can use them. Nothing special here.

Re: 2.6.3-mm1

[James Simmons]

> - Added the fbdev cursor API patch.  Not sure what this does apart from
>   preventing the rivafb driver from linking.  I'll let others decide if this
>   is progress.

Oops. Missed updating the rivafb driver. That is a easy fix. The current 
cursor api is focused on teh sofftware cursor. When I begain to program 
different hardware cursors I begain to realize it was a really bad design.
This patch breaks up the total cursor changes because it is quite big. 

P.S There is another bug I missed as well. 

I will send patches soon.

Re: 2.6.3-mm1

[William Lee Irwin III]

[-- Attachment #1: Type: text/plain, Size: 1831 bytes --]

On Tue, Feb 17, 2004 at 11:21:30PM -0800, Andrew Morton wrote:
> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm1/
> - Added the dm-crypt driver: a crypto layer for device-mapper.
> - Added the fbdev cursor API patch.  Not sure what this does apart from
> - There's a patch here to consolidate the 32->64 compat code for the IPC
>   syscalls.  Needs testing on various 64-bit machines.
> - Various random fixes to things.

Everything's happy here using things "in production" so to speak. I
couldn't think of much else to be more informative/useful, so I just
ran dbench 16 on 6 spindles simultaneously. cfq io scheduler, ext3 fs's,
768MB/600MHz Athlon, 5 47GB 10Krpm U160 disks, 1 73GB 10Krpm U160 disk,
Adaptec 39160 dual channel U160 HBA. No idea if these numbers are good,
bad, or what, but things certainly seem to be doing well. There's also
some heavy NFS usage which isn't really performance-oriented things are
doing well with also (cross-mounted /home/ and a number of nfsroot fs's).
The earlier NFS problem report is being blamed on hardware (a potentially
dead PMAD-AA ethernet controller in a distinct client machine, not
anything in this machine) for now.

vmstat log attached.

==> /local/dbench/dbench.log.6 <==
   0     62477  10.82 MB/sec
Throughput 10.8175 MB/sec 16 procs

==> /mnt/d/dbench/dbench.log.6 <==
   0     62477  9.85 MB/secc
Throughput 9.84865 MB/sec 16 procs

==> /mnt/e/dbench/dbench.log.6 <==
   0     62477  9.58 MB/secc
Throughput 9.57926 MB/sec 16 procs

==> /mnt/f/dbench/dbench.log.6 <==
   0     62477  9.62 MB/sec
Throughput 9.61646 MB/sec 16 procs

==> /mnt/h/dbench/dbench.log.6 <==
   0     62477  9.64 MB/sec
Throughput 9.63958 MB/sec 16 procs

==> /share/mp3/dbench/dbench.log.6 <==
   0     62477  9.62 MB/sec
Throughput 9.62277 MB/sec 16 procs


-- wli

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: dbench.vmstat.log.6.gz --]
[-- Type: text/plain; charset=unknown-8bit, Size: 15615 bytes --]

\x1f‹\b\0?½5@\0\x03՝Y’¥Éqß±Š»\x01šÅ<,‡\x02A\x13\x1e(ÀآѸ{ùùü¿÷†G6e¢øR\rkdUVfzÆàãñ!þþ¯\x7fûóo¯\x7føþï_þò/\x7fû×ÿø~®¯ýöïÿøwÿÛ?üÃ_ÿöüëoÿñÛÿþË¿<ÿüç¿ÿ›þøÓë__¯ÿñz½~û÷¿ÿ“ýñÏÿú—¿Ø\x1fÿãßþùŸ_¯?ÿãŸÿ§>ûí¯úð·—¾ðW>êï\x7fý_ú«­åß~{ýö\x1f¯¿þÓëßÿñO¯üz¥×«ÍÖÇëUö.Íþ\x18¥—×(©Ù\x1f/¾á¥o´ïkúÛÔÇÕíCÕ?\x14ý·«}ö'}k —G 7>äøðù˜Ó°/後Ö~½úkÙ§é¿C®ˆ\²ö=õµó\x7f\³Eå¢EuÈ\x15‘³ßÑê‡\m¹%‘«öGß{.ýøhoBµô7¹œuj¥ŽW^/ûný\ýSNõ¥ßóÐk;±Ê1×zõ¹Eö\^NK\x1fmí9×÷nmC«ñõdôŒrþÐë©\r­oVû¦>[›%Ò^[F¯¥m‹ÊI۝v\x19%¿æþг\x1f˜\x1fzsV§7¦Ñk­°žƒžÑ·C]Ú/—»ls‘^沝^.iëXËÒÆšÝM¹èÙÊJëSëk7û%¯U\x1fzÛ>ý\‡ýÎ¥\x05•Õt|ÉÎèº]»™5§h”nßXkv¦¯\x1erv\x1cù³Û’Rç6ÖÒ}å9îÝfýΩÛh¶¯lÇ;u»bhÈ-Û|ÿ›yOX°\x1aÚÆî?/£Ô:´¥f_Zst#êbÁfǹº}u{ÙÏÕ²úŽ›-ڌݼŽYl”›l¹¯µ³ûHF\x19{ë´jÒ®jÛóº
û\x15¯VF\x12\r]§mÆöÝQ	NÎîa}Èõ´6äŠýQÇ*÷U\x18ùVªÝSnúR®uKn÷›“÷Éx¥Mce‘ëö\x13ÕNrµH.\x17»Mã'ûK\x15£¸Œ\x1c›ÍˆñCN|$ùKÒ\x06-µv]6.·ë€QÄ_v&=0
{ûðÝà\x0e^•^[1b»]«³ƒ±K×Ù•"1\x1a½ÇÕutíC®Í¡íÕb¢dÿ–ç\x1c?6k<Þt\x15=#%+2J?W—öd¹e™rн”t­Î~Kêv¿v~SRaK\v›ÕÁ}tÀh\x19r5K\a؏­åÜq0Š‰\x18â-ea¤#¹¿ÿÒÆQRña\x14;Ú4٬~ß·½°›­h¥V&âSÂfM#”¯>~¹Æ4™5¾^[yÌ\x1cUÀ˾IJILP¸³Y\x03£Ì~h\x14­[3‰ÐïY³²_uOcõl\x7f\x18¹F”Ù.^ú’Ã\x1e˜*°ý\fi«Èƶ¦Wí››•Ñ2ш7kËÌÇf«xÊô^3Y·Õ囍e\x16‹Ô–ñ\x1dÆOäÊKüääÖ¡ ´YV7g[Z]\x1d¿#df±\x03Eg7Z\]9Ô§\x0e\x03S¶d2G^}\RÁ\x19dÉl•éF
ƒÌJã\x1cä$ÞFά„ýÜ”¬…³³ÏM\0—Èé\x06ëèº\x15Sòï›m§#`\x1aØ•»œ-#7.[a\x12f¿}I\x05—.\x16\x11\aœ«3ºí¸Ù‚±©)ùêÚíWØW\x1f\x05¥\x03ÔêÆ­ ê±ºÒÑw&Ù°ñ¸Ý
±qoÆ깊׊.$°q}ÕÀÆ8Si\x15­®Í\x15MV[¦”ª^[Æn‡\x13ôjiÇÙ%\x14TÖiÜëm¶í«m,\x19ˆ:¦VÇ­|¯Â~ý)dUÞ„‘+Æ›ZÝ%d¦\0_½È1\a\0wÁ¶fkíãK®\x1el\‹¯n:¹¼~gufä\x02¤ÜQ\x0e©0~®AȸŠ’·ÈÕúüŽ7¹a~ŽÎÎh´Qñ|WܬÝì¸5ŠÝ,äšìý±:;ƒñx“yˆûË퐍ì|·\yÔ.ýb\x06¥éfû~{\x01™KÁ@\x18çr\x15¦«ŒÇ´ºCA™§\x11È-Ìvv¾ë÷ٍ‰“ ¢zêL;ð\0Þûgu…³K	FIÑ0ÚÞì¨eŒßRÑœoÇ{uÆ=U.Ï’:—úÄG±#Öfëüz\x01\x12>¼¿º*çïÒx9d¿¶a´c\v®\x10EÜUä\x1d‰™÷p™ý\x1c›n</\x1c27=²	ÝüÝÀw}\x13\x02µ±­@®bÉrY_™E/K3TN4K­Ë\x16´\x10XØÍÃ(fºô“æü®·Ù¶«X\x1f $°¨Ë®bVä~fÖ¼ƒU9^"ç?Y;\x0eYËð]Í\x1fõÉ¿¿t\x06ÕÂ\x1e”»ý«ùc5((Û›dÙ|X'÷\x04\x03¾³ ïMÎÅmØ·^[\x135ùïf¶sŸ¹E\x15Ðí<\\x1e,¤âF˜Ï¾d\x18[*ím\9E	\x7fÅ\x16Ûê¦|Œ•ÃUlS`ýK.ˬ`¼EÎ..ª\03t&Dú%ÆÆ™ß;£S¡ÐõX]\x11k˜ßPQP=š\x1eó-®\x18\x15\x15@x4Ëå¹\x0f\x18åC\x0e÷µÂ!fzJ‰«Û¨Oñ ‘“ËSÚåT˜a\x1c_r\rÛU&*À´x\ÑiR†È¬|”RæŠäJØl\x19˜mç;)‚  ª4ŠùØRPx\x01¦µs`\x143\x14ÒÒ\x1frKܬ0Éþ½ô\x19ƒ¨*“X=ÔibW3Ë=hcs\r†ø®¤ìlŒËcü&‡Ì$òM®ú+®€™ÌôرN\x19`gíÇtvŠŸ^¨u]kr•ÌãÏorÙ%Û~™é\aIE×ÙuÙ³óìlió$‡\x16µÈQ\x0eY©GĈj\x10¡2ê&@ÊîõF6Žäš{P½C®ä\x16¯b¸<(b\x1c8d]ž\x7f¼
±ô›œY=m¶+–²Õ•N;k‘¿P,|ã.\x13c>Q4Œ¶Lñãwu\0\x1ffD…C™Ý\x0e7;í»LÈPP#uY6Ýì±Yó\x15Wþ’ËÓ=÷!§BL\x1aØØN"›\v(ÌË”	\b‰ic“³ù¾Š¼øûMî}v9¬ŽÀXú_7\vüRìBN\x15`\x17­í}È¡Eːþ¶Í^QÏN[|\a³TYî\bŒòk^[FÓÆÂ>>lœÙ!ÑUL\x16#ÆÉÙ\r‰·©>í~Ëô\x1c ‘™\x1e\x19•7¹ñhÅ„aœ×U,Á4v¼’Ù.ÍÑd<NDÐ8AªôºŠ)ÏË®bEõÙºX„ ÃdV\x06°§èj›ÁÝý\a£Ì„
(éÚ¬ ¶Rˆg±”ÆžQß\x19Ó­Cf»«€Y0Û7àÖ·\x14TÆ]·ˆÍÁ*Ó§/qûÛ7^õçê:\x01¨Û—su~j
3%ü&Äö}'¹RÁ£nrƒ³K;F=\vW¸n°\0ýØ\x06h<Ù\x16d¶`É\x1cK5r—÷¹ÐÉ› vèŒZ¿|c£~*¨*óÿ^]Þ‘\6ÎÑÞ¶	´E²¶
ó÷{4Û9¬®U7Œ\x13¾[=\x04\x02ÙÔ³­k£>—nvŽºî˜,¬®nç;Ç\x02JŒ¶\x1aŒOäò,·§Ò(\a^[›î<\x19¥e,ÙXxŸ»GÀm.𻮘xN9­Ë ›Ü!\x15vó\Eu![‘Ü *)3±é’—zªO[÷)\x15­€\x05ÌÂꌧãê°³Ž\x05\fÑÊ×U˜ Ÿ««È	\x19ÀÇš\x17ß)r*Ø\x13;´JŒ\x16‘Y‹ZΛÝèß2„\x1aâjG¾C*ì t`’ƹz´dvT§roå¹
ø\x0eUtÞle]€Åc\x10?˜§\x12LO\a¢ù*(WŸÒ\x17&³9FÛCGa>ŸV×u¬f‡/\x1f¥ ¿Ÿ³ëŽI±\x19£ÈÛ<5
Áüì\r\x15°!×ä\x1föOBÅ5ó×åqè0ÛÈEõiᲤu‰}òJ‚epâC~&ªO\x0eßd|ã\x05\2\vØ­hCç?Å9{E©øµ\rã\x03¾}7ëW±p*Ò…ß\x01R;~az\x16èJ>Ê¡{ôQª§ŽÆ\x06ZX\ÌÁ(U`Öx\x14”Ã~E\x18ÖÈ_\x1f%øw^[™\x1dûÑ(‘ÜRÔc6L̬ÐÖ\x18dEånŸžþ]%•e~Ñ\0J½ü;‹è„¤\x0fÝìN\x04 ë‡aœûÇÙÍŽ\a•"ðaÚ\x18©\x10>j¿
tÑL×éT˜6=¥¢=\x1aE‘ސ\x1fò;ê³ËS0r‚ý¤O™]Q£44\™~vsDK6'GÕY\x1di7aê'9;ª\x15¼ÏNR°¸%›‘Ü\x16‚Uj&^[&™mëBµmSû¸ŠÒ¸Šå\x1eÔ\x1a1u´»Îίbm)÷­xöôÜ\x13n÷÷*6(_vrW&Š@Ò~#2+ñ]Kþ]\x7f_Eý“qõ8\x03\x01„¾¬\x0eh4ö¥ïˆÅ' ùØ\x0e¸Í \x15+Þlm¾º\r¹\x1fWQH¸uÔ”Ð\x1c;â\x11ȉïN6vT{W@ò1£úÜ
ôäCjŸ¬nË¿;Î._fÛ=¨=Æï ³™(Ȭ\x04YXݦqi\x0fl,\`œ2ÛŸ”%l\x1c‘Š\fˆj\¡5nmÖ4ŒI…\aN~vû5Oϝd¹`9­®a\x02Ó\ax_Y®°yÅJq‹uG2l\x06`¾e¶§ÀÆuyBu<°LŒÉæD¼„|‹G@¹×µÙ\x16èµ\x04¦™\x1d­$8\fW+÷dè{L\x13d¡H&\x1c'Z©Ÿá6°SÍu8Z\x19œãœ”ô'¤»P8¿RŽˆÛå~6O\x1fg\a?\x1fÀáC®ŠÌ9Ö‘.Àõ¡$ã\x19öìÀǝã2r¬Îeî[X±\x15cË#“o!\x1cz4åž\x0eÆûµ-£ÝÉy³¥dO	\x10ö”\x18Xä,hß\x0e‡³\x13\x1f÷n\x1aÊ\x14ü|ƒ\x01ö•ŸaOÍ\x0e‘Õ\x14É%¡Ff~u!rRÌ”Õè~Ú_Î\b´\x02ZV‹ã$ei߁…T]ëèϱÉÎD)\x13^[×[CYü€íI-ò]\x176e–L\x16hJ¦1\x03ßÕèàµîxà”T(Ÿ\x1f…¤Â"?²\x142ý[	‘“ï\x04BlÜaã¢PÓÔODÜr¢þÁ]äÕµ©1J4\x161 \x05§&¥ëä¢Ï³¤\x03d6EC0O5\x0f/œ]ñl§!\x15U\x17<RÏ—ëN‚tãªL%±Í\0Ì\x18ö$%\x0e¿ä\btjÓg¿CN\x17.AÆ‘\x1aŽ0‡³3Wvœä&ù&ŒÎÈÕ¨ðžT\x10>­.Á¸^^o%…òæ»~n¶Âƍ|¯‘«%ž\x1d†V¹Áì>>•3§vŸ\x11­ÜŽáoÙžÔ{ôÈ°¿eUð@€Ãf¿6”.í\x18Ð.lO'³•z‹ðâlœš#\x1fuê\x1fZ¬\r\x12˜wê;¿Ù^!g’t9Ç^R\x05QÎH\bCp\x03jÜl÷Õa{Ìñ‰\x0eÞÆÔìŠr—oSZ.·Ï3O¨b‘°ê›«¨Ñ\r°°Å¾]™@	™P£"PÝ8f~@¨\x15øîI§°ç‘.x1“¶P>PQ¬¢¥Ò0•ÇÍ® \x15UÛ\x119ñS*»ÆÕQ\x1f•åñš­˜XÐ\x1eÈY\x12„\f…igfäl‰—\vµÈ|\fÿˆÏ3[t¡\x14	\x1cgGDaädní\0¯Àb6P…MFUÎHQbà"7N¨‚2
%èEn\U_K›¯d¬=Ü.KXê±Ù_Û0š‚:Ù¸“-ªxç:»\x18öx±M^[œ ’:Í\x04.œÉÜ\x19E=\x1aeH¹^[g]¦'Ë\x7f4ëûQPæj÷ \x02Vñì̇Q$ôuʃ·{ÈÁ!Ë	ç\x18°En½‡ù\x11^L1a‘pȦ
÷lu\x11ÃÏä\x1f
^–)wB†\x15“=#ò]¥‚¯Î\x06^[\x11\r#õtJî½qèÚÌ£87»³ýØq\x15Ã7ëW\x01>tòÝH¸ÈÈì"A+ ¥“XôՍÀÆ•\x1f0\x13T¤\x15}\x14\v \x12  ¨\x11›ÝíV\x01ýëA©pM2»Šýîn\x1f//@e/Õ\J0-’=)nvy½Æ×VàT,Å)\x16ô_(ùÀ©0ÖÔ	"³r¸/³=\x0e[a¦JúniYÝ>Äb\x1eªqJjŽ¸%ò}‘ïDî\bÊ:¾º}SÒ!à>\x1c©¨=åálÊR‡²3UeZ'ßÕè\x05<–l	_¶«Hñì–|Ó\fŒ–›x­¥\x1dƒ²6‚úì^[!CošÀΈ¥.\x05ERè:;°\x05\x11=Á\0sçƒCæ™ü5\x11²ÔCÞ-󹪂ÒãõZÔ\x131|»Ÿ\x19âŠä«Ûƒ|BD+»×ŸP:ÛA8ª\x17´ôOÎr\x06r<m]^[™u^}}*g·`\x1e±¦Ã)
\x06S	«“\x1f\x17phìì–ÏeB–/³M\x0e\x7fS.ãÉ\x1e) @n\.\x0fl¼\v7Û<\x05úa”Õ¨¡ >VÆÍÈ­\x11]í\x146KþÎÈi\x19v\x159âЪޖ+†Ìjá­]P…±aPîTrÔ=!×Z,8žhºQPP´Œ“"9;3z\x7fnvSåºûŠ™üMž¿cgé8h)·?PÄhš=l\x16ÈÎÎna+FðÜÕ	!d¢–CÖI6œþ]\x0e–Ì}c\x19 ‘›#&\x19)Û2i%Q\x06€SKtyÊ•;¢\0ÚÈuLO‹ä¶Š=jFr©klmŒhÉ.ˆ¬&'\a^[ÏÔ/—GF‡dš\x1cnjCfÀe´Ù#Ú\x1eÝW'ýý‘ŠïÙ	Ø5Oßc²áot\x17k°³®[êT\b×^[^tLë9;rå5nvF™\x05`¢Ö\x15™½JÉé(ļYH ¢Ç\bÍö[AQ\x19‰\x13,÷ý^j\x1d^[Å£ä?Ìyža³v8A^[?WáÎlïÑ’m•Þ™B#³¥3jù\x0ekô ˆ	^[g®Õ\x05§B\x0e™ YAZ\x16ÈÂ\x10s\x05àÃ6^[aíE?KÃ7n·T\b5·;\x159âY‚¶\x19!Ä#匿\x17°³Ã‹_;›”µ+\x1eè\x15b²B¿Ç<\x13´Á!cu9¡ÜÓŠ¦‡ÐÞü\bÌ6•ÀeD³=£÷éêS%iØÙrÅd\x19KV9»²ŸœdðQFpyÜ7nd¬Ìå¹|”-ÐƼ;œYm°¨\x1cê"7N;K¡]Ë4\x1e­Ý#4›È¸ÕAÉG}œ™èòÄR£N\0*YÅ!k×fU´j\x1e2\b(Á{‘Tœ`å¾6\v^[^[3`¶¯¢ŠI–¼»•olg\x17Û¢LàNÒɨ6@O9\x15QAõLCŒ;\x15\b·ôé…ߍ3\0Uµ#Š\x02¾»Ê¡Mß-ò£â]1hO9EünÅ@€Œªñ©®b—}«\0yŸµ ³TTû#EŒ½Æ\x10
>;;\x1aòÊŠ ‘{P´8Ù¥l¯çŠ|—/õ)Ö0K
ß­ÛåE<7¨ú\a³jmDT»„œe£®U’-—’\x12€ ÜAP\x06–LÚ¸6ûx^…iüS£t`ñF±k÷ƶS}z½Wr߸P\x05\x11•{‰ù…dZlI£h}auD²Þ²5Ô\x16¨\x1aú˜ ä&Üiä<ê\x19—%£±¦	è2\x17TùŠ¼"ª-;^[\x15”n¶ê3]EÌ\x1d%9&J	KȲÃßÑ]´‹\f5\x1aTõ7zÆluûÂ\x02¨»™4”Í¢\x04C)ñ*j,\f\x18`Püµ1K¿øŽles\fJwfÊ%V}Íx³\x13üζ܈gK» …Aë\fN…b¯:ï›]\x01ÂïÀЭz<Ûf\x04Ü\x12\x06;M²¾`\x01)E©0«\x16ùŽ»C±\x18¹z3
\x1a	ì“ÍNEŒ‡\x15\x02{:d\x18êF끑^[1\x10PH*|ß«¾”ɯô+~ÑEó\x15ƒ6NNŽ¨g\x01öœ›%+[å麐Yœ\x17ƒwûÇ3xïÔ۴֐Ù~kcBEr›Dõì\x16¬˜œÎ\x7f—½BøÃw8dM˜¦]àˆÐ”ú2\x0fÁ=wð;[ÝÙMb‹éçê¨3h J\x1d£Ñ7V\r·Œ!þ»ŠµS0´Ý쁣¼¨Â”l\0\x1a¥}±±ìné^7'!³¿Fr?ÂcÔgÛŽT\ ÑT´«\x02]ݬŠf»œÙó*¨Pú¹YWP”'\a!ÓÀ\v˜ƒÚßü³;úÔPJéÅéù]|“ŒMN\x04Íœ\x190î‡Ïók[F;‚ìI(¼Þš›²ëð\x06\x19†é
ÎŽ\x15](E\x02ÇÕV\x0fSt\x02RÖª±>0Q‘º\x1a	Ú®»ÎWÃÆUü=
\x11h\a[0¡B\a|\x14\fm¡ßmÈ@4z\x18΢´z•}¡¡º"ˆßá”I\x1a/9â6ññ¯ÍæX­M‚¶á…\x1a9\x1a`¿«\x03ê2×TR¶TybÂÝ¢)K! }ÎN%\vR)Þ\x15õÝ,äinÊŽ\x7fï\x1acåÝöÕŠ:¾‹p×RŒÇX\a¡3On莏O»\rÌn1¹âcSÝQ\x1d/Dv§œÝöß^[M™ÈÞ¬[Ʊ\x1fíÎU\x1c7«\x18¯Ðÿ±AÉ×¼ ²\bkû\fƒF\x18''%æ,7I(J$ŸdOª1>\x1e\x17Z‰—Ó(`îRã‘\x1cqÊ&tê	LbrêÏ\x1dÜÏ‘žÕá‘õ«åuáí´
â\x06–&ë\x1d6Û#¹ÉÙÍ\f^[W/\fø€Ÿ€1\x16ö`ÊH\x1f\x0e»Ç\x10XÔÀÆ£øf=ÆkWOþ 5-=IFʾòÕÉX¢
 ƒÖÈmd¶\Þ,Áø“\x12˜\x1e½Å«°(7\b\x19ƒEdÉXÝ•\x12ÀÁËd\x0e³ç\x0e\x04 \x05\f?¢•={kså*\ûî'%sTB\r—
õ\x1dÉíô»›íè»v\x17¥Ia©Ý­=
ª¶\x1a3ùŠ\x04òÏÍŽÇ_Œ«ó\x0e\vìœÉ,v{Æè½Æ\x04m\x03éý¬®Dä£&<²B\x15™£\x06WÙ—‰pLbhébf³\x17\x0e­SË\x1e½\x17'\x17k4~mÃ8¯ ì‘
Wî­ì\x18	à,wü2Ê7ø†àà•+R‰µ\x12aO»ê\fèÆ/^Ë?\x1d‡¬±\x10j\YAWî+3\x11æ.þžD󳃒{×ûNÁ›}6»T–mÊ=¢FfÉôUZë³úŽM™ì|—^[\x06ÓãÀñ\x02qS›qôfå6U/M'>\x06ƒ\b2›c&Ÿ\x1cNÝV§ULE‘a-kŠ¢;a_Ed*\x11\x1e?\ž•1=)Ž4Ét\”D™ë¤\x1d}åX5«
’S^[#Vm’>6ÃØ£‚\x02ª^[\x10Š\x14X½\rã]£2'BV~\0xÚaÞý-dµ_†Q…\x01§¾c¤‰­\x0eõ™Êe\x18uþjP^ï\x16°<£Ìöh\x18ßl,gÄ6{•\a\x16ûŸÌ\x13åÕdT…{\aäã\x02ðÈe5¦-XÄu5F.Õgú`\x1c»
ª~R\x04Ýí~~æʍ\x1c›-—@³^¦E
ÔØ.‚\x01vÖgôî\x03\bL*ÐÆ4‘žWa«V¢,µwê]ãÝwtöláÑ\x19^[ËxΕ¯\btÓz8ÐÆ21$·O³­^Á  \0ð–r>v³ûrf•Q5\x05\f9Z€\x142žþƒQÚr©PñlW…gôÜ¥a,Ð\x11ß5'7âÍšš9ë¡ÛpF\x11Žkäú\x1dzM\x1a*\0~WizÈ\x1dm&u}ù\x0e%»”©‚ŠU\x10‰Ú 5¼Ôˆß{egæU4Kœc\x01hv6¾¢w’14Âf•™™R¿ŠpWl:˜îßmµ\x1d÷‰\x13q®®«Ufy
tWWŒ!%ðk^[Æ•#–ê*`7—Y\x0f\x04¾écÕ\x17\x15or£´²	\f* vÐzñwÛ\x13!Ó\x1c¢hÉdè”ð¸¢{o¨%H¯T@O	¾Ûõæ;º4PŸ”V\x1a£DKÖb\x1déXnç\vQϨ—a„qº#½L~¿âŠ\x15B¼éùfO”M/ž9\x1d2\x11¢C:«\x10Z]1\x11ùÐßçÍwFNhå\x1c銶™¶°\x13©ÆI‰SÅ‹=6FVlWOÝ…,ß	Z\x06_QëŠÞ_Â\x03\x03Z\x19\x03\x01OãuϨÊ<\x06Óã\x15ø…¸b)ˆšjG¾\fc\b\x04ž›\x1dð]Ši¼Ç
ãÀx&ß\”\x1e»Sî*ˆÊÍ.\0¼tc\x01¤Æ;sƒ†ŒšwX\x1c2kWq’ó*W\x15Ë"\x15WJ`0©‚"\x1a÷\x1ckM\x118VAûþq³4º™úÜWÎR\x1c§r\x19ü»L\x18ruö´\0/v¦?Øê&›M7\x0e-\x19ÆÌyÞ­0=謫\x1a1êÁGµÐ×íìˆä†\x18Øœ0Â\x149\x0f\x16¼_9Ë\x19Ã\x14¿Ù¬\x02*õ\x17ÅJÍìqöp<2\vÃWmPPî俘Îbä®dÏäìF~\x12ð:»váÐQßÑ¿¤Ù\vØŠþÃôÈwJÞÉHN\æ1€FÑGy„\fìÐdv\\x01h‡½„‘mý¡å.ž7KäÖé4WðjÅ™ÄÙí©\r’6®WfKˆù)dË7+soww5	0^Ã\x1cJWP^åx5
Ūþ†Ý\x17h¥ÕýH	ˆ\x7fjòBwæ¡å«Qè×6Œ5Vø$².k…r¿ÜEdx4\x0fñ\x16\x19ŒX¿<#ºè9…žñïf»ûÊ'ó[¼à\x18ÏÝñ££]¸D6Fv:8 1J½à@¢1ïˆèê2.ê\f\x0f
ê\x1aËáê³P\x0e=©ß;e–œe\x1aí\x03¥.a\x01gí÷Ž¶"}ÁAÕ¸âT|–hΡ`bï¶\x1cà(æ¿Ÿu¤w9´›žB²gâ„ú¼\x10¿
Od%ºÞ›CZQ*”°è?d¶¸çNoà)d²æ¥m\íNLv¥Sf´d3ûÙu6;b\x13ýk(ý`q‘Çd•*ˆ­¹Cý„\x16Æ\x0f}W˜¾j.Ïu³ô»?Ù\x19¦iÕËÕž±bŽÁªŠ^[AÈRÕÕ©2Õˆ–W¯\x10Þ;Ý)Ð\0-¬g³\x1e¼ß­3ÅSß^}3\x1fT;\x14Bµ°Ù^qÈ4H\x03rW“\0—м…ÁKMò\x05¥–x\x15Õ›Ö;\x1eÔŠ2«:\x7fŠfq*è \x15_‡ºª\b\x1aÍí
Œê¤`óTŸùmÛëH¹Ù\x1cmÅŒ=\ao!ó\yÞwáçdšf{Oª¨æìÅ\0´Æx¶bg‹T‡Âãè^[ƒúX€í…Ÿ\bÓ5Fx\ý½¥?7«\0\x14\x1d\x7f’s\0Úý(\x1dùÔìßÛ¿\vUý•µ6LϾÚ6\x13–í)Ó\x1a$gÖOÐ(\x14U`ÉJåìÒ¼¢íá‰cice*|ÐOH\x1f·XDÆ\b/I\x05›½Ù¥béòÌ\r¢~UUÌ¡h¶Ç‰\x01”|˜r\a$Ïûʦ¨‹³\0\x1d¹6nj*ýãä\x18ë¾ÚÝÜ¿Û$\x18òí\x05(\x13¤É!‘.ÃX.à㹊„»˜¯ÂObúLNÃn\x164]úî\0>ìNB#ãrœÖõ]ŽHEN™Ñ\x038³øj\x16\x1c]Ùè\x16ìì\x1anz(æ™t|\x05™\x15\x1c7ñï†n\x16F\buó—\aµ\x1dÍó\x1aœîVAÅ\x15ŒR5Q##P/rÑ\vðhÛT€kãvÇd\x15k\v´£ðØÈG[±b&ª5×(ÝC¼\vè\x1d\fú£ŸÛ!­:îÊ¥\x12{£‡«\0¯«\x02¼:®‚Âw³\x17>†Hg´.[ñCf]}zAJ\x1a×ÍvÚÝ(­Äûì\f®=ô]끍½Ž¿“Yëë*éµ0E\x13=\x19\x7fì³ ªfD‡dt¾Z\x05}³³¸ú¼oV¿ŒÁ&^è>ÆŽÅ<ãò ºßì¿›WIï'”©»|:^)\x03‹!Þi¶)¨2k›\x1c¬Lw\x13¨œIoñG\x15Ö®ª¯\x03¬œQ*¼›¤Wê\x02渆Mï'UžÞ\x1d\x11…IX§\x17\x10íl\x05&z“[±_ü+M¥LT¹\x02Ë\x10¼‡Y\x101#P'l\É€N&7+RèÊ}ª\åžžÞ§­.È,\x03ú;\rˆv\x15WLÆHœ¼)…\x18Ý;\x0f£r§ %${¸Zš£t\x17±^\x06»mn\x0e@
\x03ú’\x06</špýjc‹!œ¿&¯Ý2æ+=…¤\x1d>ÞÊÌÏ\x0f€\x17{òë\x03‚=*%ES¶\x17˜\x161¼C\x15R{!\x025\x1aƒ	S¬¶EQûwRQÅù¸ã¢§\x1e'›ýÚ–ÑœŒ³N«’0îxðê\x18@,>xÅАòdTéÙÒhÍÓ”Éö\x1cgçýƝ¼…IÙ5\bwcJ¦wöd\x1arë\x15§D˜§åç*€*.S&©\x10\x1eèæV$ʺJ„MÜF \a^[Óªjä.÷sy®\x1cŸv4È͈i=ÙÕ¯sì\x13w芚\0ÅÁ”ñ&Aöä¶lO»\x1aÁMôÎÕ1ÜZRáþ⺪µ½f‰¤J×êF\x12¦u\x16ó´k€‹\v™wãå~iw"\x03\x06ždbËšíB΢
ó•[À´€\x17+é”åód¿ä˜³`\x1e\a¢\x06ø©\x14g\b\x19¯ö9ÒÙF®xÞíêz÷ùHØmºñjÙ±LK½Ò\x01ú€7L\a€/–kd\0‡Wh\x13Ïš½lëÝz\€ó÷Ý^œÒ\¥x`‰™2o\x16´€ ùü Š4bå¼:rϸ\aD±3IT³\x04¯d9ž'à·EYø\x1e§†˜†	\x11-=iFÎÑ€«\rt±Íæ1#Ó\Û•Žž1áûˆEuý/?`¶‰ù`ÔæöF—Ì\x0eã´´^ýmg×\¥\mïšs`×ûERÆe|vL€xq¥êù\0µb/ŽíƒÌ=…U^”Æü…#@Þ±Nk\x13ïwŠŒú̱ŠL\00	\x10ÚÒ\x18][.§Ç"Ú`Ê(Õ4îÇöÐL\x11LÙä¡\v&_R\x15ê~%|c³àðŽFz&²±£Ÿ™\x16,ÓÉôDÜáûEîQÇÕ\x11¼X\x1c”3\x1eÞ\x1eø\x01lvæ˜O1¾\vEiÓ\x15\x1e*E£:\x039Ò,¹ù¼TÕ¦›~¬\x7f¤ò›ÛÅÿô
æYǝ±hšbäÓ\r¥ä˜\v|ZF¡î§Ã8	ù\x18Ó/ úÂf'¸6ýÂŒ[0-\x11Ç\x11Úïð˜\x11Íôò§a:ðvÀµéësÜ3gÐOòusESfßåq“ó^œÞ\£ôØÄ \x17J9h\x1ai)4˜¹Æš\x0f\r¿éÇêüì £ÕEFñ\x06LÙ׬îfD\x10_‘ÅAî1´Æ£Ù®‰¤Sò`Ê\vÌç¥ö|×\x1a­ñ%W<\x17Ũ\x15³öwî]~qiOå¼4Ǿ¼ŠùÆyœ\gÒOïÓ\x13 ד\x18^	å\x16C#Ä•þÉ?êeö—\x1c‘¾™aš¶Lʯ<\x1eÂËqm&L­öc,\?VçÛ냳^[ûšË1\x01y±í>\x1fZ-E÷àµqð]e¤^\x1f\x0eD×\v9ž\x02ÛšW/6渕r¥Tßøâ›ï0=d'ÉöhußVF.a1d\x06Ï´Ê	\r\x01ò{ºáC®`+˜HÚÅ\x17Q^[Ór´|B"h\0%sçUì°:oRí>ù®÷r?iO}&ê`gÕ¤r5Ïœ7ëÝÌF\bÔ½×»\x02Ï\v«Ù,UdtÓ^Ãoγ›¾Y\x0fÊú5ÍuÉè´âuZry@çCØ3ÃÙyak÷'Ô¦¼ÚKßÉ›MóÄ›ê\x16Žtô'÷þVPÕ[l<Šjéw®"y½\fÅ¸r znŽS¥Àx˝írõ§h¶\x06#añÝ•ñµãŒs>꓏~ß\x05\x1eÙ\x02œe>.ó©¡ì\b	\x05x Oýx·^[p\x1e\x1e~\x04n6Vò
£¤p*\a,ß‚È"¶¨ýÚ–±–p\x15n\x1e:ŠÒä¨\ñ¶\x10rã\x0ePK^"ê×\x10§ÞâÍ¢ÏßW‘óe\x19å
åÌ\x04{¯¬\x1aãJ•E¡íÀbT\aku—”1÷#S7‡g@ÊU \x187Û\x1cs[ŽU¤~ÍÀãm¢úTÎoŒÁ\x0e|¬
æ\x15„–Õ16d\x16\x7fuâÃË[¸]ÞžÞö^Œ\x14+\ræÛ×~VÇDçþ”~Þóe–7ª\x0f¿ŠùÔ¦‡ˆ¶ÆÕÑЧH^[C^[g&g\x7fƒ§'¢˜ó‘ëÒ€ò:l\x0f?0=—Ÿ÷ÕÞG\x14Co~žÌ_m×4\béσ\ñ¶bb`壯Á\x1c"ô\x1e.A)Ô¼Çj¾c¼‡ÜruìàB¯q\\rgP\x12ðg÷±pò\v\x0elö¨ÝÉSvÂ%©ã«Ž‘+Ó;¿*éíž\x7f\x14W惜çò§×¹ö\x1f\x13ú0±îBq\x15 ð§ë\x1eoÖgššl°ºz=à	\x16[ÜX€À·–ãìÅÏœ·^[à\r”t©Î~½=EñÝk9ôÑ@¢gt¡z
Wáuý¬ÄOlæöL\x14xÑh¯Š\x16°Šò†ŽßRÑüìpÝǺl\x0fï\N/L\x05Ž^[†?\x13\œ\x1c£†$^˜ž|\rÀÊý)Y\0çÙ\x0f–{9ǧÌú»]Ý{ql³W|¬ÂÔ’< eÊÿ¾f/Žü”Í>þ¢'\x19¡k\x1fó]¥Áè‹æUi›Ùµë‡Ïs:ÇŽ“\x03ƒý¸Šìoð€z\x04Zg‰ÚXsÎ\x0f6\x1ež*{œ”2î\x02A…=‡^½Û…K>Øø×6Œs‡À¢W—ÙU\x1e\x7f1Å›•¶¬Õ]¨\x17Ð~ä¶BŒ—Ý#Û¿ãB½(\x055ëõ…+¥\x10Ï\x19ñ¯\x15V÷\x162wðÚ¥y
-{Kî€ï˜þ\x1f]ž3dl۝ãU<\x12¸P#&¥v"=X\x02À`¶{ÔwÙ…Ì\vµ4'lv\x7fÉ©$U\r )¢Ÿ9ú(­¹»HÍÜýÊ\x0eSçJó\x12<ŠÉ÷ˆcÓUL~^\x05]\x10}y@[Ú\x05\x06ø¼…ì]V‰*Ük¨I\x7fÊfß*ÀŠ\fÌsÕõ\v&o”º\x7fÊfy\x06ì4Œ=¬Žžv€E­.ßSæ\x18.1¼ä˜¢ÞÕ.¾[ñ*ÜlÃZ¦¦b°\x1e\0\x19ô—/Ú-yÝçz±#ªÏ'=³\x1eõy\x0f\x0fË˧̽'\x1a¸\x15:sªéÁ\x03ãf‹»Úw%i«d{p9\x19¼Ö®\x14ƒyiÁl'w\x17i\x164\aó
ÊdV\x05ÿò~Âbðy$§ö”\x1an–Í6¿Ùr™mZ\x19\aCk\x06Ho»b<=w=\x0fŸÇ§8\x19=Ü€t\r#Û*\x17’(\bA\x05…Òò4\0þ­\x03JDR|Úw_\x0eWÖ\výd`j}œÄô¶Û×Ä¿“\wôsU\aSï\x02ë
JļòéµÎ%š2E\x02çêÜö,·ó¾\fma\x04³O^£ùÌöücH|97›|³ŽàÕ;?£9•\fyÍÏ3+}Ç2\x14L™\x12åD\x02®RbK®WD»×¨ ^ú³Äòïú~|*8)<âm«ËWmÀ3Ë\x19r\bg.±\x16ê׶Œ¦\x12ÎÍ>9՝–‹Et\x03* å\x13'ê^[\a#žÏÎò÷kQoȍÜÖ~øîn {ẄïxÛeÍuW.ìÓXÐ"Ü\x01ÇLÈâø›§…)Íô.ÿ‘­¨Ý™"ÉÀ%ŒÅ5‚ÀŸÃx²–Ž˜¬ˆºï\x15\wÜXPHGð®lL[MÀ3>6{\\x13¨6à\f\x19)\x1eí[rÔõBx4\x16ƒRÒáBÆ@­\x11ßPk3’£’¢ÓçbäÚ5\x11†¹ÿ^b„v§ÙúdãÒ¢)\x03>íÛ+SSŽ`*mz™\x1c¤Ù\x1eú±fì,ï#\x04\x16Ž\vu:Gú˜óª›\x1dÞùƒW!¨—\x02Ÿ`·cô>\x1du§ÑØþ\x7f½kÍ\x182ï‘öŠ\x192jÁ”Ë«ð›Õñ¨Å¿ÇH`xÕ\a#çuÈzYö\x1eC\x12\0A†\x05iN¢ÈÍñ£\x0e‚—¶ê^["«z7;<Éö\x1e\x7fó¬\x0eK=|¼¡Ú\x02£=¯t8>E$²\x18¡¾\aõù$@ö^î\x06DËا¿e…¾£HØôAðf…/\x1e›Ýn+6\x13NÇý ðò)?¼~ì3\x03HŸŸ\x03\x04Ë“\x03}_\x05qR*o!‹›å\x1d°œ?UnFîÊÐò­\x02œ\\x05HIñqÑœ©ä™\f7ï›G“÷U\aÑ#\b…íú» ²Ì\b·ê	€¸í\x15ÃíÖN´2³K#'Ï®\x0f\x7fQ-œ`6¼F&`µT/÷³=#˜ßf»4\x7fv$á/^ÕFÀä\x05¨‚‡¨59ߘ\v\x12®\x02JðÈ\¬FÚ¨€\.¨B0†°óœ\x1d\x05‡WI߯m\x18g\v0y\x7f„l;¼x?z&Q¨´by\x02Ä\x02½\x11áÅ\x12\x14”?Ä0rvhvÇZ÷Œ÷W¼Ž\f}'u}O¿9ñ@jZÔªäaOTP…÷T·¿Ê$Ùl?šÀÖ3Áåñ\x02¨L\x1e<í"[q¯–a,4æúÍRd\x12\x1eð¢÷”éE\x1c6^[‹æl\x1f\0ÇÐè^åf†Õ¼ÿ~Ž†<ù®úSÌùÐ+tQAñv€^[ïî	ß\x1dÝŝ/r®³i\x02^[?:|I¦VŸ\x7f‹÷©êÊg°±_E\rA™×º\x0fÕ(¢>o;ËØ\x10\x1f®éóè´ºÓ0®ˆiñxÎ\0¼êcÔ89hc%Zó\a2\x15nsfÏÕõ\x12‚2oÙ\x18Ù»gn¾£\x17Vå<¤¶àw\x05}—­8Éá¹Ûf·\x03ÇQ}Bî\x19\0¹êãâ\x0f©èA^[{\x0fíàý®>vlòWË\x11\x1eŒ—ÎS\x11-Ky¾\x03\x16³ÛþÈ®ŠÛ`ã8úÂ̶ÖU&8ôô«¸†º÷(³ÔË\foï^[+¾\x19ù(÷öT“\x03àå+êIa³dÜD\x0eÃØï™z:µâCœž"\x15Á\0Í®?…Ìk>îÆM^˜/þ˜2iAÕêݳ*Î,cÇ£^[ڐÎîê)£/ÉÂ,ÜE\a!®×Ìnœ TÇåµÕ15vÝ@
¼¿\x06êR¡yⱌ,f\x19û£¡º'߯æí¹|æ<\x1e™,£$'\x16º†\bTéRç\x14ññð‘)Çá1g.9ãñªm»\x1c¼\x1e£÷N‹ñÀé²ÕÅÑAÙ³ÆÛÅ‚\x16_\x1a¯þ0–q˜v•RžÂ…ëQ\f\0òÂÀG¯ƒ¨eÆ&‹\x15K\x03\x1a¥P£8ä–î>úJ¿15sÃG\Þ­å9ªcªÒFqP‹–¡@NÚ=ñ܉ÏsUÇðï–à½ÉmÂ^Ïö\OÅøÔÍÌÓ*¦ÿý!›ˆÍŽË”=êx<©­\vêe”™^[Z‡+ûýtBŠ \x16úÜì³w”¬+(SÝWñ\x11}£â`´è\x06ô\x1d’åþ ºžN¢Õ2_­GÛ7‹þô>«v½±‘‚Wñ^·€¬\x1c›{¨¿Éù)tÕfóŒ›-1Šzn6Mo\x04­—GƐ\x14\x1f¸à>O»Þ:P5ä¡¡VscAãûtxðX\x1d1\x1eÓ\x18¼¿o0Ðé*6:µ;^Ž9)\E+\x17âÆ4ÃEØI¥\x1e2‰Ú½E0Õ½J½›Lžöò*¼’”Ör\x15@h4àu³\x11"{Ø8{…Ë\x1cÑ\r \x033?Ù\x1e<²z\r‰\x7f^\x1aýÚm?»æ\x19‹zMħR›J:†ö{¡Vð*Ú\x15”=Q´GQó‚yŠ\x03\x19t”€\x1aÑ\x13rÊl4´>paPÜ-äøv\x03ÈwtWî\bYŽÏ2ŽÈ(cºeœXÆr?ô
\x1e˜˜yóè»\x12\v\x04ç¥ï†;x2‰fzz\x04ñ7O\x14òü›'Ú¼\x1eŸê\x17Lî>Oanúhå\x06ñ5=,¯Ìþx0®\aåž½\x15jPBj’Þ¢M¢wògÙß½«9F úû	\x1c¿ßX! ýÑ£¦ð»<•V@ˆkèç¯m\x18/äcÀ\x1a£bÉäCÅpÛ+«\x1d„êÉ¡¹\x1fã¾\x0eõ9Ýå\x17zï×8ˆÊ¤É\x02èNUEÑ»Àga\x7fOAA-Ú\x0e\x06hJ,¯VK`\x1fî‘T€á×~7E\x1cñqö7ôŒAäAužw?\x19…\aÏyš"wž\x02Ì«ÜÞìqv\x16:x:œêo/Q?W—žÞ\x1eT<m[3Îr\x14\x10zFQ¸\&]\x12²Þî±Ä^‹\x02²Õ\x01¡Æ%dµ=s„\x1fL\v\n4y5]µÛ1>\x06­ôN5j„ýµ¢ÓV¤³V3ûœ¬Ñ)Òèå~Y\x10ûÏ<+ŸƒI‡çõÜI;m…Cój;ÐSŸ±\x12Jë]* §Æ)Ç:›æUw¾ºñ<£ø\x0e,P\x01½£\x02V¾]žÅ@-YÛæïÏ]e³
oBP†\x7f×™L®g{\x02ßÑDà/Þ{/8/\vžÓ\x12V?Øxo?;†óôzU‘\r2\x0eƒþ¾®òÅÂkʧ\aÕ‘/.£íAõbŸW_T£"ÅÕg£V³ßmª=lÖßØ\x18£ ³w˜R™å˜&¨à\x1aï\x1a·\x13­œïü\r#'åÞï\x06\x10¯,å™joOqÐý´³)à2
\x19ã¦Äf÷Uª™Ÿ*#¹\x16m?݇¡Ô½KÁ|ؘ§LÄýòQÚ¾Þ+öa\x06u»é\x11\x18 ŽáËûlgEŠ[²á
ª]…¤¥û4\x1dÆßÐD«çìÎBRÍ+l?Ô'®ŠÔgôIgXŒ ³SÅ‚ñÝ=°D¾#\x01­Â9—Ù¸ºê\x0fª\x0f_\x1dé”ë½MÉܹ:*ç\a#‡zgZhd\x14†¤1…•ù\r¼\x19ù‡1Œz\x03- äÏÙ\x11\x1e—\x1e\x13\x16 ­\x05«™…¢¾|Tlj’§ ï†;\x15“$£üÂ@.·æ/“\fjzžº„+\x108ØX•ûÕÉ¿ëûê\x01ëô§úk Mf»¥¹C‡š	r; \x05O”	¼hÿ\x183[Õ‹(º4XTÏ¥\0º›—V\x0f2\£ÌáÊýB*¼ð¦8*HˆWÕxt´äv\rz;£m„ŒªGsÈ®·JK¡Àŧÿ>­å±®¿«Bï`cŒÍ˜Ò¢f+îÖH\x1f•º|òJ!&+·
¨\a£x3ù`\0¦©€ë)@\x10[uFhuLH¨×Ìd5^žž;ÅAc=BvMæÀ0e=\x01É\\x18ªy®ÉºS–è\0?±dŒÍéJ`^2ËÌ\x15
I*A\x14³„ÎáÚàȇTxV²azÖUºDQz%G+¥éµF6Vz9Ÿgçe0à½]­å\rGqÎÏ\x13”ͧõ\x1dNE~•\x13p\x03P4r¸<óò>yîúåSkÈ¡•9w`ãN;ÝW}zˆ\a,©q.—¾#	UýÑ\x13ñZ\x01鍵äù`ãÁ\0WÇ\x15\x15¦D©(d\x18hüÊ°@f–ãI\x0eKtÄd\Å®n\x18¯^œ†\b®çåH1¢R\x02Wð~2
)ü—çQl³×SÏEL^]6ªb²¢1Å×^[jõ4ÛîAáØu^\x01:É\rïÕ`$)
Š¾÷0Ëq…Õué²×à‰hÛl£p\x19ì–ýmÆæ3$Sœ¼&w2\x14\x06 >·jô®`ä;Jǽ©Ø”;Sëj\vþÝàéÒƒï\0Ý÷æìÆ…CW\x1f\x1dä*€\fÃý|ç/n\x18ÃUxm§¦2ÀwéjŽ\x1e\x14¶OêR«w•Ö}×C\x1fW¡y¹Ógfa®q_õy$ƽO\x1a®w^¥üÇ)³úlâ¯öž¯ÑßO?¯0G!Q\x14ÆG!“é9„ÌÇIL\x1e\x0fêºæK\x05`É0Œ®wŠÉ\x1eó(NÃèE\x1dÓ³Ñ=]…ó\x03¯˜ç¼rw£r•^[ªYå0ÛîLÏŒÒjDÈÔvÈÌ€ú–
ó⯗TgÔw\x14¶NGÈÚþ\x11WxðŽrW"Á4@lÝnauÞ\x1dcäÈä·=£3‹¡,™§íõλ\x06DGF©ôp]™|µ0`+®áÚ^³ÑHEa•*Ó&"£œ\x1aűةæqµªŽ¨Q\x18IÞŸùkÓ\x1fŒ‹ƒ9F4ÛŒ\x1f¡ùÞù.BZ\x04Q™Ù8Yï\x1e+2¨7BVö)dð]áéS3º±\x7f®\x14^_ \x10«þžÈU¦ÕyeìM®Ð°iê\v/ÀBó\b’7u}â/>Øgi;"\x15²ßÍVÀLõžj³y_¯ÐšÑפ Þ³wßx®\x12:,4à+\x15>Ss\a¥ÜË=v©P6JÁ‘\aï\fÄ\r¦g\x04mìóþ'q¨Ý5Ð \x0f÷ï€e@sæ5\x14j0çè{\x15Tº[,#KÖî©u\x0f¤åØvCAÝõífZ
6K“•*{ÂÙ5
£H£ÚfyO=Å÷6)ªú®ÎǘÌNiº\x1e½	ärñ'¨Ç{\M1é\x0e9FÙòu’ƒyÍÑÈÅÂ\0Zr• uÿŽ\x127Ÿ\x13R\x0f, \x7fùNØibF‹Â”–o‡\fül’ɯtãé5°S}þ↱œ›}&_Xt\x01´°"„ÿr£³™áPA*Ò¼ž¶W—ý	-  \x1er£Å³^[•ÒJàÀFñw¾«ojPŸ^[”iöÁU”\vG¡Jßt\x0ePùða:×ó=xŸþ\x14àä­éÞî¹F•Î\x05æŽ'ibsá(ýTPFN§5ý±¨†]\rŒâe\v¬N¢îSCâ»\x0e‡%ËÏ+uƒ6¦Z¯æ¾–ý¥züw)wóVrŒgǹٌ7¡‘³òïêU]Mø,Ì\x0e\x05Åã¢\x1a×ß\x01z>äN!ó¹\x1c“ihÝ\x13l§Ì
;7÷š-k\x15`­A\x05¤ d“‡b\x15l‹\¿\x1eSÎÉ'`zk~Efcx,F©§\aEÄêÐB-±£ŒY?σ€*ÅRF°’G8\x0fÓ\x03´0y\x16¯«†%j\x14º¢\x13³k\veZû\x1a®M®÷´\x15°1ã\x7f»J\x1fƒ¾S2F=\aNn:ŠµßZÝW¹—\x02B6'5\x15Òí:O`VôVÊË[q€Eë¼Þ‹SÌ|˜íEg¤¼Uãz#^[+”\x14/\x13D\x01Cç{ˆÓ
ä¼\abzÿGÙåºY\x10”í7[}\x16YìwSâ1(w<(ž×é¥^\x0f³ª¦W\a‚S1ÁܯW'zÐ(Ù{ ¦Ç³¥^õËŠñTG‘ÅKW³\vFé ‡¡ž›¾#3úQf_ÝbùSÏz\v\x15èù#\x15\a¹AÓ—]¿¼Ï¼<ÁpXGr^[Ý\x112ùÆ\x1a¾¨>úþ]]°³4¦OZxôâYL¨ÊÒÒü¥³c\x16™\x12—a\0V\rä\x18\x0eÏ|ݦ³«\x17£¼èÕÃG)
35\x15\x7f˜â^[	Ùy³Œµš^[!+éÂQšÏ\vd:¬ž>\x17âSÿo\x1a%ù\x10”„»˜Ë}\x15øWËí¬B9Ú·ÎQ¸3zPô²i^›¢\x1e½B\x14¥B¿Ú„%ãMŒ¥*Z²ž¿ã^[k\x06Ô"qÉêî|Å«øУ´\x1e¼èMð³ŽTäNX&;¹áBæ•éß”
ïMÐKœ\x05*ü,¾‘Cv\x18ÆÄï\x17ì&!Ë\x17RñâýÄå…iŠg-ÎÈwæý$7˜¸²¼BØ\x1cÖˆ\x05¼<Çø€F^ñ1\x7f¨ÏS^[“sQ\rO\x12¦RÇ}\x15ëÑè\x16\x1eIß­\x1ak¿#¹êÓ\x16\x16\x1dTmëÙCÈ\x15¯Ò*(¨ZbÅGÔÆ•L‰‘ÓÄ€¶×56ýiye\x10sõÔÑúQ\x04qnvñ]‹2ÛžÊõ\fØ‹î¹Å¸4Œ\Ñf¯dô±:ûżzÁ$üžêUZé^@u\x1cÅ\v—ò¸Wwܬ	"gÇ8ncþ\vGyQÖT鱂\ᵓÈ(‡
0\r·JzòS+7ßál:„C¦\v	ä‚Ù®Þ¤µ€d›Ú{.mL¾‚±\x1c¥ß9prÞìa+ŒhD§ò·­¹oFám\x02Š\
“!\x19Ev8dužÀ‡æ\x185T‰¥ÅyW»ð\vH«Ð«Ù\x12«ë±×¥·\x13s¯dÕõ\x16LÖ\x10EúŒÃê
c„q
•À*\x1alrÍ];`h=*[¨³Ûƒ‡#ûOr™.ëL¯YÙwŸP:}ãFÿïK.JÓ3oõÚ,ÝsÃ_¶Å©€gΛ\ráñ`踑“ŸØú¼FBù#
•rh)=={0ÿ@Pj\x0f\x11ãðçiV“#×ú¾FÎ3?¤<(?ó™æ\r|\x1cl¬iò:»®”D\x13ÑŸ\x1a%ûè¥Ê°\x1a\x181ÎÑøª\0Ó\x18þ¶).{S	K”Y\x12\f“Þh½¢l,Û®Õ5wc\x1er\vÿnñ\b1ß¾¥\x02/ zúƒºù+ý!Þþ°±¹E¼-º†þP€wi\x14’‰/,Y¡2}^¯\x15Ë7þœà6´1œj*tþ
¥7x—µv^N¸F×jàT>W÷Œ¶ÐÏ™\r¿¼\0†¡ò,ªYŒÍ$Ç¢„l\x7f«€zJ…Ý>µ‹‹æͺê…òÈ\x0e«¼…¨‡Ä\x16¯–Èì\x19€jôŽÄÈ‚\x15EK3_‰|6ûTVV¦Ë\ffÙ~]\x1e<¬\x0f¹§\x1dei6Šž2¹fu¿üGž:(* ¡{ëlÆÃKû›¼;gä$\x15µÖ~›\x1e\x12\f”àT\x01\x1fæŒÏp³>‚éC.QS!îÓج\x1cK¿u\x15Ÿç˜*-ª\x14FŸeU§\x7fg\x1cJ
uÑCovhÝäX\x17½.\x1aöiêÓ¤âd\x14¥\x03>–Ì‚AwÈ–üDc‚y)wvÈ`\x1c9ºŠ0¯&P^\x05ù’ã\x05lU=«Ÿ2ÍuA©’©wR\x10\x18z\sÎ\x05L}¥b/Ÿ½Ãë‹æøŽè\x11<—î-ùíݏk^[\x1c\x1fÃ\x18\x18e{n{ã„Ö|¿éÉ\x1a\x7f/®úÓ.æÌv¹‚ï›==¨’ýÉ^\vÚ\x01ˆ\x19õ\x10®‚b4*ÜÜVô\vÒR•ÕGA•Â›Ì*Û\x13˜dÜw{\x01\f2 $­2ÂIs&¯ÎïÌ*¦Ói™ùWKŒ\x06ê\äÐ0“t>v¶Õ˜y\x17¹6–\x7f%\x02›f’ÒF|L€bDYXJƒx9a¤?Ò¸T©èïÍ\x0e’¥Š}”{¬cßúŽä\x18®vÆ!£‹)>\x03v[È£’ob\0sÇ.r/|c2Q¥¸%Kñq¼v˜má\x18^[rèïµËAI^[\x02cÐnåÃzO‡ÌÌØAN\x0fˆh³\f¹VpqeS@•É£?Éh=X~Ƴù”Yû*³\x12·—c/Ÿ[ò:\x1cd¼b&~UǍW<»|ÚŠªñàâ»ê]Æ×^[RHÚ!\x13¡
›Ò8ñÓôdW|\x0f¹êÍÐzmS6¦\¥AÙ¦ûCcjŒR_ñ™×3\x10¨­ð®ÎöAmmæËVh'Ù++Ý
ß=\x02ép*ªÞΓ‚¢\x02\	â^[\v\07v!\x03èÃi9+É\x05ê}È\r/\x19ÙÝõ7­'Ñ’g C.*PÊûÊ€êZ?äÚ\x13mK·7’È—
pfÿÎëRc¥Ñ«\x1dWÑÌ<%V\a`Üwº£íå¢Æ„C‚ý\x1a5ÊKpí‡\o$)÷ ©]ǝ:"bôÔQ–Y0\a#\x06\x020û—\%#°ýÒzOq{>>iUX‰)ü§\x01½¬î»Y\v±tØ\x1aQŸ¼ÀãÒ(8·t\x7fPË‘û™\x1d0J®¬î»ÙQAŠ\x1c3Ìg½\ž—›qü^Ù\a[£\véB¿oÈ¥ƒ\x1c@¯Èß%÷|ä%\vz™ÓƒtÐ]™ÿ3rÏ$šß'Ç(L½!­˜{âEð¾VþIŽÉ\x12SüŸ®ŽÁî\…?\x7f"Šú´ýÿ‘{Ñö¢Õ1þYa\x1fO(§\x1fäÈ\x17ÿ?‘ó³£LI¼¦Ç‹\x7fuÃ\x18Ùø¿²Y\x01ã&\x15î25ï{ÿyvû¿t\x15äý\x17Œò»ä€´¶\v«Ï§ü¡\x02\0á}v@V™Á\v\aVqÁOF\x01b»È\x1dƶ\x1c«“©JëYØðOÿ\aöV¬{¡È\0\0

Re: 2.6.3-mm1

[Andi Kleen]

Andrew Morton <akpm@osdl.org> writes:

> ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm1/
> 
> - Added the dm-crypt driver: a crypto layer for device-mapper.
> 
>   People need to test and use this please.  There is documentation at
>   http://www.saout.de/misc/dm-crypt/.
> 
>   We should get this tested and merged up.  We can then remove the nasty
>   bio remapping code from the loop driver.  This will remove the current
>   ordering guarantees which the loop driver provides for journalled
>   filesystems.  ie: ext3 on cryptoloop will no longer be crash-proof.
> 
>   After that we should remove cryptoloop altogether.
> 
>   It's a bit late but cyptoloop hasn't been there for long anyway and it
>   doesn't even work right with highmem systems (that part is fixed in -mm).

Is it guaranteed that this thing will be disk format compatible to cryptoloop? 
(mainly in IVs and crypto algorithms)

While 2.3 and 2.4 have broken the on disk format of crypto loop several
times (each time to a new "improved and ultimately perfect format")
I don't think that's acceptable for a mature OS anymore.

-Andi

Re: 2.6.3-mm1

[Andrew Morton]

Andi Kleen <ak@suse.de> wrote:
>
> Andrew Morton <akpm@osdl.org> writes:
> 
> > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm1/
> > 
> > - Added the dm-crypt driver: a crypto layer for device-mapper.
> > 
> >   People need to test and use this please.  There is documentation at
> >   http://www.saout.de/misc/dm-crypt/.
> > 
> >   We should get this tested and merged up.  We can then remove the nasty
> >   bio remapping code from the loop driver.  This will remove the current
> >   ordering guarantees which the loop driver provides for journalled
> >   filesystems.  ie: ext3 on cryptoloop will no longer be crash-proof.
> > 
> >   After that we should remove cryptoloop altogether.
> > 
> >   It's a bit late but cyptoloop hasn't been there for long anyway and it
> >   doesn't even work right with highmem systems (that part is fixed in -mm).
> 
> Is it guaranteed that this thing will be disk format compatible to cryptoloop? 
> (mainly in IVs and crypto algorithms)

Allegedly.  Of course, doing this will simply retain crypto-loop's security
weaknesses.

> While 2.3 and 2.4 have broken the on disk format of crypto loop several
> times (each time to a new "improved and ultimately perfect format")
> I don't think that's acceptable for a mature OS anymore.

Well I guess people are free to do that sort of thing with out-of-kernel
patches.

One question which needs to be adressed is whether dm-crypt adequately
addresses crypto-loop's security weaknesses, and if so, how one should set
it up to do so.

Re: 2.6.3-mm1

[Andi Kleen]

On Wed, 18 Feb 2004 02:55:49 -0800
Andrew Morton <akpm@osdl.org> wrote:

> Andi Kleen <ak@suse.de> wrote:
> >
> > Andrew Morton <akpm@osdl.org> writes:
> > 
> > > ftp://ftp.kernel.org/pub/linux/kernel/people/akpm/patches/2.6/2.6.3/2.6.3-mm1/
> > > 
> > > - Added the dm-crypt driver: a crypto layer for device-mapper.
> > > 
> > >   People need to test and use this please.  There is documentation at
> > >   http://www.saout.de/misc/dm-crypt/.
> > > 
> > >   We should get this tested and merged up.  We can then remove the nasty
> > >   bio remapping code from the loop driver.  This will remove the current
> > >   ordering guarantees which the loop driver provides for journalled
> > >   filesystems.  ie: ext3 on cryptoloop will no longer be crash-proof.
> > > 
> > >   After that we should remove cryptoloop altogether.
> > > 
> > >   It's a bit late but cyptoloop hasn't been there for long anyway and it
> > >   doesn't even work right with highmem systems (that part is fixed in -mm).
> > 
> > Is it guaranteed that this thing will be disk format compatible to cryptoloop? 
> > (mainly in IVs and crypto algorithms)
> 
> Allegedly.  Of course, doing this will simply retain crypto-loop's security
> weaknesses.
> 
> > While 2.3 and 2.4 have broken the on disk format of crypto loop several
> > times (each time to a new "improved and ultimately perfect format")
> > I don't think that's acceptable for a mature OS anymore.
> 
> Well I guess people are free to do that sort of thing with out-of-kernel
> patches.
> 
> One question which needs to be adressed is whether dm-crypt adequately
> addresses crypto-loop's security weaknesses, and if so, how one should set
> it up to do so.

AFAIK the two big security weaknesses in most version of cryptoloop are:
(note that some versions have it fixed with various hacks) 

- Weak IV 
- Extremly bad key management

The first can be addressed in an crypto API module e.g. with an hashed IV, but it needs a 
stable IV format from dm-crypto (that is one of the things I asked for) 

The second one is more a user space problem. However to solve it you need metadata. 
It would be much nicer if it was possible to store it on the block device directly  
(with a special losetup flag for compatibility). Otherwise you get into nasty 
chicken and egg problems with fully encrypted systems.

Supporting metadata can be quite simple - e.g. a standard header on the first blocks that
has a length and a number of records with unique IDs. And the kernel driver would need
to skip over these headers.

-Andi

Re: 2.6.3-mm1

[Joe Thornber]

On Thu, Feb 19, 2004 at 07:37:34AM +0100, Andi Kleen wrote:
> Supporting metadata can be quite simple - e.g. a standard header on the first blocks that
> has a length and a number of records with unique IDs. And the kernel driver would need
> to skip over these headers.

The target already takes an offset into the device, so you have what you want.

- Joe

Re: 2.6.3-mm1

[Andi Kleen]

On Wed, 18 Feb 2004 13:45:58 +0000
Joe Thornber <thornber@redhat.com> wrote:

> On Thu, Feb 19, 2004 at 07:37:34AM +0100, Andi Kleen wrote:
> > Supporting metadata can be quite simple - e.g. a standard header on the first blocks that
> > has a length and a number of records with unique IDs. And the kernel driver would need
> > to skip over these headers.
> 
> The target already takes an offset into the device, so you have what you want.

Ok fine. The only requirement would be compatible IVs then.

-Andi

Re: 2.6.3-mm1

[Andrew Morton]

Andi Kleen <ak@suse.de> wrote:
>
> On Wed, 18 Feb 2004 13:45:58 +0000
> Joe Thornber <thornber@redhat.com> wrote:
> 
> > On Thu, Feb 19, 2004 at 07:37:34AM +0100, Andi Kleen wrote:
> > > Supporting metadata can be quite simple - e.g. a standard header on the first blocks that
> > > has a length and a number of records with unique IDs. And the kernel driver would need
> > > to skip over these headers.
> > 
> > The target already takes an offset into the device, so you have what you want.
> 
> Ok fine. The only requirement would be compatible IVs then.
> 

Would it be correct to say that until someone does this development,
dm-crypt has the same vulnerabilities as cryptoloop?  Or is there some
different way of using dm-crypt which is incompatible with cryptoloop, but
is more secure?

Re: 2.6.3-mm1

[Andi Kleen]

On Wed, 18 Feb 2004 15:27:45 -0800
Andrew Morton <akpm@osdl.org> wrote:

> Andi Kleen <ak@suse.de> wrote:
> >
> > On Wed, 18 Feb 2004 13:45:58 +0000
> > Joe Thornber <thornber@redhat.com> wrote:
> > 
> > > On Thu, Feb 19, 2004 at 07:37:34AM +0100, Andi Kleen wrote:
> > > > Supporting metadata can be quite simple - e.g. a standard header on the first blocks that
> > > > has a length and a number of records with unique IDs. And the kernel driver would need
> > > > to skip over these headers.
> > > 
> > > The target already takes an offset into the device, so you have what you want.
> > 
> > Ok fine. The only requirement would be compatible IVs then.
> > 
> 
> Would it be correct to say that until someone does this development,
> dm-crypt has the same vulnerabilities as cryptoloop?  Or is there some

It all depends on what the crypto API module and the user space utils implement.
That is why calling it dm-crypt is misleading, dm-filter or somesuch would be 
better.

> different way of using dm-crypt which is incompatible with cryptoloop, but
> is more secure?

More secure will be incompatible.

-Andi

Re: 2.6.3-mm1

[Bill Davidsen]

Christophe Saout wrote:
> Am Mi, den 18.02.2004 schrieb Brandon Low um 21:52:
> 
> 
>>I am just reading up on dm now, but correct me if I am wrong, I will
>>need to do losetup, dmcreate, mount in that order in order to use
>>dmcrypt on loop where with cryptoloop, I could just do "mount"... there
>>must be an easier way to handle this!
> 
> 
> You don't need to know everything about dm to set up encrypted devices.
> 
> Basically dmsetup is something like losetup, only that it's much more
> flexible.
> 
> To set up a device basically:
> 
> echo 0 `blockdev --getsize /dev/bla` crypt <cipher> <key> 0 /dev/bla 0 |
> dmsetup create <newname>
> 
> is enough. And it's just temporary, because no special tool has been
> written yet. dmsetup is the most low-level dm tool, mostly for
> developers. I've written a shell script named cryptsetup for the
> meantime, it asks for a passphrase and does all the magic you need.
> 
> "cryptsetup create test /dev/hda5" will ask for a passphrase and set up
> /dev/mapper/test. Voila. "cryptsetup remove test" removes it and
> "cryptsetup status test" shows some status information.
> 
> mount -o loop is basically a hack. mount uses parts of losetup to do an
> ioctl. The encryption support as mount argument is an additional patch.
> Even worse, some do passphrase hashing, some don't... it works but it's
> not a very clean solution either.
> 
> BTW: dmsetup is NOT a big program. It has two parts: a libdevmapper.so
> in /lib and the dmsetup binary itself. Every part is 16k in size (if
> compiled statically into one binary it's just 27k), and it's still
> linked against glibc. If linked against dietlibc or klibc it would be
> even smaller. Nobody needs LVM tools or something. It's just a small
> client for the dm ioctl, just like losetup is a client for the loop
> ioctl.
> 
> There are some plans to write a unified plugin based key management
> tool. You might want to have your key stored on a USB stick. Or
> encrypted in the first sector of your device and you want to unlock it
> using a password (so you can change your password without needing to
> reencrypt your data). This would be much more flexible than most of the
> crap floating around.
> 
> So, you see. NO NEED TO PANIC. Cryptoloop won't disappear over night.
> There will be some nice to user interface. At the moment dm-crypt is
> only a *kernel implementation* and not meant to be used by every end
> user immediately. Nobody will force you to drop cryptoloop until there
> is a clean solution for everybody out there.

Could you give an example of the one line I put in /etc/fstab to replace 
the one now which includes "noauto,user" so users can mount when they 
need the secure data?

You *can* do that so you don't need to train users, give them special 
permissions, or use privileged scripts or programs, right?

Re: 2.6.3-mm1

[Christophe Saout]

Am Do, den 19.02.2004 schrieb Bill Davidsen um 22:58:

> Could you give an example of the one line I put in /etc/fstab to replace 
> the one now which includes "noauto,user" so users can mount when they 
> need the secure data?
>
> You *can* do that so you don't need to train users, give them special 
> permissions, or use privileged scripts or programs, right?

That's not possible at the moment. What you want to do relies on the
feature that the mount command itself does the required setup. The would
require to have some dedicated C code fot the device setup and make
mount use that (through a patch). mount currently only knows about the
loop device. And BTW the key management sucks if you use an unpatched
mount because it uses the unhashed passphrase unhashed key.