Help!

mmotm 2009-11-01-10-01 uploaded

 
  

Post new topic   General Reply to Topic (not reply to a specific post)    Forums Home -> Kernel RSS
Next:  [gentoo-user] X crashes with nvidia-173 driver  
Author Message
akpm
External


Since: Apr 25, 2007
Posts: 20



PostPosted: Sun Nov 01, 2009 2:10 pm    Post subject: mmotm 2009-11-01-10-01 uploaded
Archived from groups: linux>kernel (more info?)

The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to

http://userweb.kernel.org/~akpm/mmotm/

and will soon be available at

git://git.zen-sources.org/zen/mmotm.git

It contains the following patches against 2.6.32-rc5:

origin.patch
maintainers-asus-acpi-extras-remove-f-arch-x86-kernel-acpi-bootc.patch
maintainers-brocade-bfa-use-single-line-m-and-tabs.patch
maintainers-server-engines-10gbps-iscsi-use-single-line-m.patch
maintainers-vmware-vmxnet3-quote-name-with-comma-and-period-use-tabs.patch
get_maintainer-fix-usage-comment.patch
page-allocator-always-wake-kswapd-when-restarting-an-allocation-attempt-after-direct-reclaim-failed.patch
page-allocator-do-not-allow-interrupts-to-use-alloc_harder.patch
vmscan-force-kswapd-to-take-notice-faster-when-high-order-watermarks-are-being-hit.patch
proc-fix-stack_start-in-compat-mode.patch
uml-irq-register-race-condition.patch
fb-remove-fb_save_state-and-fb_restore_state-operations.patch
savagefb-fix-blanking-mode-on-crt-display.patch
xfs-free-temporary-cursor-in-xfs_dialloc.patch
memcg-fix-wrong-pointer-initialization-at-page-migration-when-memcg-is-disabled.patch
nommu-dont-pass-null-pointers-to-fput-in-do_mmap_pgoff.patch
alpha-fix-f_setown_ex-and-f_getlk64-conflict.patch
alpha-move-thread_size-definition-outside-ifndef-assembly.patch
linux-next.patch
next-remove-localversion.patch
i-need-old-gcc.patch
include-linux-compiler-gcc4h-gcc-402-doesnt-understand-__builtin_object_size.patch
hardware-latency-detector-remove-default-m.patch
crypto-nfg.patch
kernel-core-add-smp_call_function_any.patch
arch-x86-kernel-cpu-cpufreq-acpi-cpufreqc-avoid-cross-cpu-interrupts-by-using-smp_call_function_any.patch
dell_laptop-when-the-hardware-switch-is-disabled-dont-actually-allow-changing-the-softblock-status.patch
cmpc_acpi-add-support-for-classmate-pc-acpi-devices.patch
cmpc_acpi-add-support-for-classmate-pc-acpi-devices-fix.patch
cmpc_acpi-add-support-for-classmate-pc-acpi-devices-depends-on-acpi.patch
acpi-annote-acpi_processor_add-with-__cpuinit.patch
fujitsu-laptop-fix-tests-of-acpi_evaluate_integer-return.patch
eeepc-laptopc-dont-enable-camera-at-startup-if-its-already-on.patch
acpi-remove-nid_inval.patch
acpi-remove-nid_inval-checkpatch-fixes.patch
thermal-sysfs-apitxt-reformat-for-improved-readability.patch
thermal-sysfs-apitxt-document-passive-attribute-for-thermal-zones.patch
acpi-thermal-display-forced-passive-trip-points-in-proc.patch
thermal-add-sanity-check-for-the-passive-attribute.patch
thermal-only-set-passive_delay-for-forced_passive-cooling.patch
thermal-disable-polling-if-passive_delay-and-polling_delay-are-both-unset.patch
acpi-reintroduce-acpi_device_ops-shutdown-method.patch
cs5535-gpio-add-amd-cs5535-cs5536-gpio-driver-support.patch
cs5535-gpio-request-function-mask-names-added.patch
alsa-cs5535audio-free-olpc-quirks-from-reliance-on-mgeode_lx-cpu-optimization.patch
agp-correct-missing-cleanup-on-error-in-agp_add_bridge.patch
omap-fix-unlikelyx-y.patch
avr32-convert-to-asm-generic-hardirqh.patch
powernow-k8-fix-test-in-get_transition_latency.patch
powerpc-sky-cpu-redundant-or-incorrect-tests-on-unsigned.patch
mm-add-notifier-in-pageblock-isolation-for-balloon-drivers.patch
powerpc-make-the-cmm-memory-hotplug-aware.patch
drm-via-add-pci-id-for-via-vx800-chipset.patch
radio-add-support-for-tef6862-tuner.patch
konicawcc-possible-buffer-overflow-while-use-strncat.patch
quickcam_messengerc-possible-buffer-overflow-while-use-strncat.patch
i2c-mpc-do-not-generate-stop-after-read.patch
genirq-switch-proc-irq-spurious-to-seq_file.patch
timer-stats-fix-del_timer_sync-and-try_to_del_timer_sync.patch
wistron_btnsc-add-dmi-entry-for-medion-wim2030-laptop.patch
input-bcm5974-retract-efi-broken-suspend_resume.patch
input-bcm5974-report-abs_mt-events.patch
kbuild-generate-modulesbuiltin.patch
kbuild-rebuild-fix-for-makefilemodbuiltin.patch
kconfig-cross_compile-option.patch
mtdpart-memory-accessor-interface-for-mtd-layer.patch
isdn-hisax-fix-lock-imbalance.patch
hfc_usb-fix-read-buffer-overflow.patch
misdn-fix-reversed-if-in-st_own_ctrl.patch
isdn-eicon-use-offsetof.patch
isdn-eicon-return-on-error.patch
hisax-fix-test-in-waitforxfw.patch
3x59x-fix-pci-resource-management.patch
bluetooth-fix-for-acer-bluetooth-optical-rechargeable-mouse.patch
sunrpc-use-formatting-of-module-name-in-sunrpc.patch
serial-fit-blackfin-uart-over-sport-driver-into-common-uart-infrastructure.patch
serial-copy-uart-properties-of-upf_fixed_type-ports-provisioned-using-early_serial_setup.patch
pci-populate-subsystem-vendor-and-device-ids-for-pci-bridges.patch
pci-dmar-add-__init-annotation-to-dmar_ir_support.patch
include-trace-events-lockdeph-fix-do_div-warning.patch
scsi-add-__init-__exit-macros-to-ibmvstgtc.patch
drivers-scsi-fnic-fnic_scsic-clean-up.patch
ibmmca-buffer-overflow.patch
scsi-eata-fix-buffer-overflow.patch
drivers-scsi-gdthc-fix-buffer-overflow.patch
drivers-scsi-u14-34fc-fix-uffer-overflow.patch
drivers-scsi-lpfc-lpfc_vportc-fix-read-buffer-overflow.patch
osst-fix-read-buffer-overflow.patch
scsi-fix-func-names-in-kernel-doc.patch
gdth-unmap-ccb_phys-when-scsi_add_host-fails-in-gdth_eisa_probe_one.patch
zfcp-test-kmalloc-failure-in-scsi_get_vpd_page.patch
st-fix-test-of-value-range-in-st_set_options.patch
drivers-scsi-libsas-use-sam_good.patch
ncr5380-bit-mr_dma_mode-set-twice-in-ncr5380_transfer_dma.patch
bfa-fix-test-in-bfad_os_fc_host_init.patch
scsi-add-hpsa-driver-for-hp-smart-array-controllers.patch
scsi-add-hpsa-driver-for-hp-smart-array-controllers-fix-hpsa_allow_any-test-for-vendor-id.patch
scsi-add-hpsa-driver-for-hp-smart-array-controllers-fix.patch
hpsa-fix-use-of-unallocated-memory-for-msa2xxx-enclosure-device-data.patch
drivers-block-dac960c-use-dac960_v2_controller.patch
vfs-fix-vfs_rename_dir-for-fs_rename_does_d_move-filesystems.patch
raw-fix-rawctl-compat-ioctls-breakage-on-amd64-and-itanic.patch
vfs-improve-comment-describing-fget_light.patch
ecryptfs-another-lockdep-issue.patch
fs-remove-unneeded-dcache_unhashed-tricks.patch
fs-improve-remountro-vs-buffercache-coherency.patch
vfs-make-real_lookup-do-dentry-revalidation-with-i_mutex-held.patch
vfs-clean-up-real_lookup.patch
xtensa-use-generic-sys_pipe.patch
xtensa-convert-to-asm-generic-hardirqh.patch
xtensa-includecheck-fix-vectorss.patch
percpu-avoid-calling-__pcpu_ptr_to_addrnull.patch
mm.patch
__generic_block_fiemap-fix-for-files-bigger-than-4gb.patch
rtc-disable-hpet-emulation-on-suspend.patch
fcntl-rename-f_owner_gid-to-f_owner_pgrp.patch
speedstep-ich-use-correct-cpu-in-speedstep_get.patch
dma-debug-allow-dma_bidirectional-mappings-to-be-synced-with-dma_from_device-and.patch
drivers-gpu-drm-i915-i915_dmac-fix-unused-var.patch
drm-make-sure-page-protections-are-updated-after-changing-vm_flags.patch
x86-_end-symbol-missing-from-symbolmap.patch
scsi_libc-avoid-calling-scsi_device_put-from-under-host_lock.patch
nommu-ignore-the-address-parameter-in-the-file_mmap-security-check.patch
hrtimers-remove-the-timer_stats_active-check-when-setting-the-start-info.patch
itimers-fix-racy-writes-to-cpu_itimer-fields.patch
posix-cpu-timers-optimize-and-document-timer_create-callback.patch
amd5536udc-fixed-shared-interrupt-bug-and-warning-oops.patch
hso-fix-debug-routines.patch
hso-fix-soft-lockup.patch
oom-dump-stack-and-vm-state-when-oom-killer-panics.patch
readahead-add-blk_run_backing_dev.patch
mm-warn-once-when-a-page-is-freed-with-pg_mlocked-set.patch
page-types-constify-read-only-arrays.patch
page-types-trivial-typo-fixes.patch
page-types-unsigned-cannot-be-less-than-0-in-add_page.patch
mmap-dont-return-enomem-when-mapcount-is-temporarily-exceeded-in-munmap.patch
mmap-dont-return-enomem-when-mapcount-is-temporarily-exceeded-in-munmap-checkpatch-fixes.patch
mm-vsmcan-check-shrink_active_list-sc-isolate_pages-return-value.patch
dev-mem-remove-redundant-test-on-len.patch
dev-mem-introduce-size_inside_page.patch
dev-mem-cleanup-unxlate_dev_mem_ptr-calls.patch
dev-mem-cleanup-unxlate_dev_mem_ptr-calls-fix.patch
dev-mem-cleanup-unxlate_dev_mem_ptr-calls-fix-fix.patch
dev-mem-make-size_inside_page-logic-straight.patch
dev-mem-remove-the-written-variable-in-write_kmem.patch
dev-mem-remove-the-written-variable-in-write_kmem-fix.patch
dev-mem-remove-redundant-parameter-from-do_write_kmem.patch
mm-move-inc_zone_page_statenr_isolated-to-just-isolated-place.patch
nodemask-make-nodemask_alloc-more-general.patch
hugetlb-rework-hstate_next_node_-functions.patch
hugetlb-add-nodemask-arg-to-huge-page-alloc-free-and-surplus-adjust-functions.patch
hugetlb-add-nodemask-arg-to-huge-page-alloc-free-and-surplus-adjust-functions-fix.patch
hugetlb-factor-init_nodemask_of_node.patch
hugetlb-derive-huge-pages-nodes-allowed-from-task-mempolicy.patch
hugetlb-add-generic-definition-of-numa_no_node.patch
hugetlb-add-per-node-hstate-attributes.patch
hugetlb-update-hugetlb-documentation-for-numa-controls.patch
hugetlb-use-only-nodes-with-memory-for-huge-pages.patch
mm-clear-node-in-n_high_memory-and-stop-kswapd-when-all-memory-is-offlined.patch
hugetlb-handle-memory-hot-plug-events.patch
hugetlb-offload-per-node-attribute-registrations.patch
mm-add-gfp-flags-for-nodemask_alloc-slab-allocations.patch
vmalloc-adjust-gfp-mask-passed-on-nested-vmalloc-invocation.patch
swap_info-private-to-swapfilec.patch
swap_info-change-to-array-of-pointers.patch
swap_info-include-first_swap_extent.patch
swap_info-miscellaneous-minor-cleanups.patch
swap_info-swap_has_cache-cleanups.patch
swap_info-swap_map-of-chars-not-shorts.patch
swap_info-swap-count-continuations.patch
swap_info-note-swap_map_shmem.patch
swap_info-reorder-its-fields.patch
mm-vmscan-change-comment-generic_file_write-to-__generic_file_aio_write.patch
rmap-fix-the-comment-for-try_to_unmap_anon.patch
oom_kill-use-rss-value-instead-of-vm-size-for-badness.patch
tpm_tis-tpm_sts_data_expect-workaround.patch
frv-duplicate-output_buffer-of-e03.patch
frv-duplicate-output_buffer-of-e03-checkpatch-fixes.patch
cris-convert-to-use-arch_gettimeoffset.patch
cryptocop-fix-assertion-in-create_output_descriptors.patch
floppy-add-an-extra-bound-check-on-ioctl-arguments.patch
floppy-add-an-extra-bound-check-on-ioctl-arguments-fix.patch
timecompare-fix-half-y2k38-problem-in-timecompare_update-while-calculating-offset.patch
warn_once-use-bool-for-boolean-flag.patch
dynamic_debugh-kernelh-remove-kbuild_modname-from-dynamic_pr_debug.patch
ad525x_dpot-new-driver-for-ad525x-digital-potentiometers.patch
qnx4fs-remove-remains-of-the-defunct-write-support.patch
generic-ipi-cleanup-for-generic_smp_call_function_interrupt.patch
drivers-misc-add-driver-for-texas-instruments-dac7512.patch
drivers-misc-add-driver-for-texas-instruments-dac7512-update.patch
init-mainc-fix-symbol-shadows-noise.patch
kernelh-remove-initialization-of-bool-in-printk_once.patch
rwsem-spinlock-remove-useless-function-exports.patch
rwsem-fix-rwsem_is_locked-bugs.patch
rwsem-fix-rwsem_is_locked-bugs-fix.patch
kallsyms-remove-deprecated-print_fn_descriptor_symbol.patch
errh-add-helper-function-to-simplify-pointer-error-checking.patch
errh-add-helper-function-to-simplify-pointer-error-checking-fix.patch
vt-introduce-and-use-vt_kmsg_redirect-function.patch
always-print-panic-message-on-current-console.patch
scripts-get_maintainerpl-add-roles-and-rolestats.patch
scripts-get_maintainerpl-fix-non-with-git-blame-and-cleanups.patch
scripts-get_maintainerpl-support-multiple-vcss-add-mercurial.patch
lib-vsprintfc-add-%pu-to-print-uuid-guids.patch
fs-xfs-xfs_log_recoverc-use-%pu-to-print-uuids.patch
randomc-use-%pu-to-print-uuids.patch
drivers-firmware-dmi_scanc-use-%pub-to-print-uuids.patch
drivers-md-mdc-use-%pu-to-print-uuids.patch
fs-gfs2-sysc-use-%pub-to-print-uuids.patch
fs-ubifs-use-%pub-to-print-uuids.patch
efih-use-%pul-to-print-uuids.patch
drivers-media-video-uvc-use-%pul-to-print-uuids.patch
compat_ioctl-remove-vt-specific-ioctl-handlers.patch
compat_ioctl-do-not-hold-bkl-in-handlers.patch
firmware-only-allow-edd-on-x86.patch
atmel-mci-change-use-of-dma-slave-interface.patch
mmc-atmel-mci-new-mci2-module-support-in-atmel-mci-driver.patch
mxcmmc-fix-error-path-in-mxcmci_probe.patch
sdio-rework-cis-tuple-parsing.patch
davinci-mmc-mmc-sd-controller-driver-for-davinci-family.patch
davinci-mmc-modify-data-types-of-edma-related-variables.patch
sdio-recognize-io-card-without-powercycle.patch
scripts-checkpatchpl-add-warn-on-sizeof.patch
checkpatch-trivial-fix-for-trailing-statements-check.patch
checkpatchpl-allow-80-char-lines-for-logging-functions-not-just-printk.patch
hwmon-driver-for-texas-instruments-amc6821-chip.patch
lis3lv02d-axis-remap-and-resource-setup-release.patch
lis3lv02d-i2c-support.patch
hwmon-w83627ehf-updates.patch
hwmon-w83627ehf-updates-checkpatch-fixes.patch
xilinx_spi-split-into-generic-of-and-platform-driver-add-support-for-ds570.patch
atmel_spi-fix-dma-addr-calculation-for-len-buffer_size.patch
spi-controller-driver-for-designware-spi-core.patch
spi-add-pci-interface-driver-for-designware-spi-core.patch
spi-add-pci-interface-driver-for-designware-spi-core-fix.patch
spi-controller-driver-for-designware-spi-core-fix.patch
kprobes-sanitize-struct-kretprobe_instance-allocations.patch
autofs4-use-helper-functions-for-active-list-handling.patch
autofs4-use-helper-functions-for-expiring-list.patch
autofs4-use-helper-function-for-need-mount-check.patch
autofs4-use-autofs_info-for-pending-flag.patch
autofs4-renamer-unhashed-to-active-in-autofs4_lookup.patch
autofs4-cleanup-active-and-expire-lookup.patch
autofs4-eliminate-d_unhashed-in-path-walk-checks.patch
autofs4-rename-dentry-to-active-in-autofs4_lookup_active.patch
autofs4-rename-dentry-to-expiring-in-autofs4_lookup_expiring.patch
autofs4-always-use-lookup-for-lookup.patch
rtc-fix-driver-data-issues-in-several-rtc-drivers.patch
rtc-cmos-convert-rtc_aie-rtc_uie-to-rtc-irq-api.patch
rtc-ds1511-fix-races-around-device-registration.patch
rtc-tx4939-fix-races-around-device-registration.patch
rtc-ds1553-fix-races-around-device-registration.patch
rtc-ds1742-fix-races-around-device-registration.patch
rtc-stk17ta8-fix-races-around-device-registration.patch
rtc-do-not-use-container_of-macro-as-an-argument-for-to_platform_device.patch
rtc-set-wakeup-capability-for-i2c-and-spi-rtc-drivers.patch
gpio-fix-test-on-unsigned-in-lnw_irq_type.patch
gpio-add-gpio-driver-for-the-timberdale-fpga.patch
gpiolib-add-names-file-in-gpio-chip-sysfs.patch
fbdev-bfin-lq035q1-fb-new-blackfin-landscape-lcd-ez-extender-driver.patch
fbdev-bfin-lq035q1-fb-new-blackfin-landscape-lcd-ez-extender-driver-v4.patch
fbdev-bfin-t350mcqb-fb-handle-all-resources-in-suspend-resume.patch
fbdev-bfin-t350mcqb-fb-fix-lcd-dimensions.patch
fbdev-tv_paln-bit-set-twice-in-sisfb_detect_vb_connect.patch
intelfb-fix-setting-of-active-pipe-with-lvds-displays.patch
const-constify-remaining-pipe_buf_operations.patch
hfsplus-identify-journal-info-block-in-volume-header.patch
hfsplus-fix-journal-detection.patch
reiserfs-remove-proc-fs-reiserfs-version.patch
reiserfs-dont-compile-procfso-at-all-if-no-support.patch
reiserfs-truncate-blocks-not-used-by-a-write-v2.patch
fatfs-use-common-time_to_tm-in-fat_time_unix2fat.patch
memcg-coalesce-uncharge-during-unmap-truncate.patch
memcg-coalesce-charging-via-percpu-storage.patch
memcg-coalesce-charging-via-percpu-storage-fix.patch
memcg-coalesce-charging-via-percpu-storage-fix-2.patch
memcg-make-memcgs-file-mapped-consistent-with-global-vm.patch
ptrace-cleanup-ptrace_init_task-ptrace_link-path.patch
signals-send_sig_noinfo-should-be-considered-as-si_fromuser.patch
signals-send_signal-use-si_fromuser-to-detect-from_ancestor_ns.patch
signals-cosmetic-collect_signal-use-si_user.patch
signals-kill-force_sig_specific.patch
signals-check-group_stop_count-after-tracehook_get_signal.patch
utrace-core.patch
do_wait-optimization-do-not-place-sub-threads-on-task_struct-children-list.patch
ipc-ns-fix-memory-leak-idr.patch
ipc-semc-sem-optimise-undo-list-search.patch
ipc-semc-sem-use-list-operations.patch
ipc-semc-sem-preempt-improve.patch
ipc-semc-optimize-if-semops-fail.patch
ipc-semc-add-a-per-semaphore-pending-list.patch
ipc-semc-optimize-single-semop-operations.patch
ipc-semc-optimize-single-sops-when-semval-is-zero.patch
drivers-char-ipmi-use-kcs_idle_state.patch
elf-kill-use_elf_core_dump.patch
cyclades-allow-overriding-isa-defaults-also-when-the-driver-is-built-in.patch
char-mxser-remove-unnecessary-tty-test.patch
isicomc-use-pr_fmt-and-pr_level.patch
hvc_console-fix-test-on-unsigned-in-hvc_console_print.patch
edac-i5100-clean-controller-to-channel-terms.patch
edac-i5100-add-scrubbing.patch
edac-i5100-add-6-ranks-per-channel.patch
dma-mapping-fix-off-by-one-error-in-dma_capable.patch
irq-fix-test-in-__exit-parport_mfc3_exit.patch
aio-dont-zero-out-the-pages-array-inside-struct-dio.patch
aio-dont-zero-out-the-pages-array-inside-struct-dio-fix.patch
bitmap-introduce-bitmap_set-bitmap_clear-bitmap_find_next_zero_area.patch
iommu-helper-use-bitmap-library.patch
isp1362-hcd-use-bitmap_find_next_zero_area.patch
mlx4-use-bitmap_find_next_zero_area.patch
sparc-use-bitmap_find_next_zero_area.patch
ia64-use-bitmap_find_next_zero_area.patch
genalloc-use-bitmap_find_next_zero_area.patch
sound-core-pcm_timerc-use-lib-gcdc.patch
net-netfilter-ipvs-ip_vs_wrrc-use-lib-gcdc.patch
net-netfilter-ipvs-ip_vs_wrrc-use-lib-gcdc-fix.patch
vfs-take-2add-set_page_dirty_notag.patch
reiser4-vfs-add-super_operationssync_inodes-2.patch
reiser4-export-remove_from_page_cache.patch
reiser4-export-remove_from_page_cache-fix.patch
reiser4-export-find_get_pages.patch
reiser4.patch
reiser4-adjust-to-the-new-aops.patch
reiser4-adjust-to-the-new-aops-fixup.patch
reiser4-remove-simple_prepare_write-usage.patch
reiser4-remove-simple_prepare_write-usage-checkpatch-fixes.patch
fs-symlink-write_begin-allocation-context-fix-reiser4-fix.patch
reiser4-handling-error-returned-by-d_obtain_alias-fixup.patch
reiser4-update-names-of-quota-methods.patch
reiser4-use-set_page_dirty_notag.patch
fs-reiser4-add-parenths-around-x-y.patch
fs-reiser4-contextc-current_is_pdflush-got-removed.patch
reiser4-fix.patch
reiser4-rename-psched-to-dispatch.patch
reiser4-drop-journal-info.patch
reiser4-fix-compile-warnings.patch
reiser4-reduce-frame-size-of-reiser4_init_super_data.patch
reiser4-reduce-frame-size-of-reiser4_init_super_data-fixup.patch
reiser4-disable.patch
make-sure-nobodys-leaking-resources.patch
journal_add_journal_head-debug.patch
releasing-resources-with-children.patch
make-frame_pointer-default=y.patch
mutex-subsystem-synchro-test-module.patch
mutex-subsystem-synchro-test-module-add-missing-header-file.patch
slab-leaks3-default-y.patch
put_bh-debug.patch
add-debugging-aid-for-memory-initialisation-problems.patch
keep-track-of-network-interface-renaming.patch
workaround-for-a-pci-restoring-bug.patch
prio_tree-debugging-patch.patch
single_open-seq_release-leak-diagnostics.patch
add-a-refcount-check-in-dput.patch
getblk-handle-2tb-devices.patch
getblk-handle-2tb-devices-fix.patch
undeprecate-pci_find_device.patch
notify_change-callers-must-hold-i_mutex.patch
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.RemoveThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top
Jiri Slaby
External


Since: Nov 04, 2006
Posts: 645



PostPosted: Sun Nov 01, 2009 5:10 pm    Post subject: vga_arb warning [was: mmotm 2009-11-01-10-01 uploaded] [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On 11/01/2009 07:07 PM, akpm.TakeThisOut@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to

Hi, I got the following warning while booting an image in qemu-kvm:

WARNING: at fs/attr.c:158 notify_change+0x2da/0x310()
Hardware name:
Modules linked in:
Pid: 1, comm: swapper Not tainted 2.6.32-rc5-mm1_64 #862
Call Trace:
[<ffffffff81038008>] warn_slowpath_common+0x78/0xb0
[<ffffffff8103804f>] warn_slowpath_null+0xf/0x20
[<ffffffff810d32ba>] notify_change+0x2da/0x310
[<ffffffff810c5b88>] ? fsnotify_create+0x48/0x60
[<ffffffff810c6d2b>] ? vfs_mknod+0xbb/0xe0
[<ffffffff812487b6>] devtmpfs_create_node+0x1e6/0x270
[<ffffffff811170d0>] ? sysfs_addrm_finish+0x20/0x280
[<ffffffff811175d6>] ? __sysfs_add_one+0x26/0xf0
[<ffffffff81117b6c>] ? sysfs_do_create_link+0xcc/0x160
[<ffffffff81241cf0>] device_add+0x1e0/0x5b0
[<ffffffff8124adb1>] ? pm_runtime_init+0xa1/0xb0
[<ffffffff81248f05>] ? device_pm_init+0x65/0x70
[<ffffffff812420d9>] device_register+0x19/0x20
[<ffffffff81242290>] device_create_vargs+0xf0/0x120
[<ffffffff812422ec>] device_create+0x2c/0x30
[<ffffffff810c0516>] ? __register_chrdev+0x86/0xf0
[<ffffffff81245599>] ? __class_create+0x69/0xa0
[<ffffffff814326e9>] ? mutex_lock+0x19/0x50
[<ffffffff811d4e23>] misc_register+0x93/0x170
[<ffffffff818994a0>] ? vga_arb_device_init+0x0/0x77
[<ffffffff818994b3>] vga_arb_device_init+0x13/0x77
[<ffffffff818994a0>] ? vga_arb_device_init+0x0/0x77
[<ffffffff810001e7>] do_one_initcall+0x37/0x190
[<ffffffff8187d6ce>] kernel_init+0x172/0x1c8
[<ffffffff81003c7a>] child_rip+0xa/0x20
[<ffffffff8187d55c>] ? kernel_init+0x0/0x1c8
[<ffffffff81003c70>] ? child_rip+0x0/0x20
---[ end trace 4eaa2a86a8e2da22 ]---

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


Since: Jun 15, 2006
Posts: 897



PostPosted: Mon Nov 02, 2009 6:10 pm    Post subject: Re: [PATCH] hugetlb: offload per node attribute registrations fix [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Mon, 02 Nov 2009 16:50:15 -0500 Lee Schermerhorn wrote:

>
> Against: 2.6.32-rc5-mmotm-091101-1001
>
> Fix build failure when MEMORY_HOTPLUG_SPARSE and !HUGETLBFS:
>
> drivers/base/node.c:484: error: implicit declaration of function 'init_node_hugetlb_work'
> drivers/base/node.c:582: error: 'node_memory_callback' undeclared (first use in this function)
>
> Reported-by: Randy Dunlap <randy.dunlap DeleteThis @oracle.com>
> Signed-off-by: Lee Schermerhorn <lee.schermerhorn DeleteThis @hp.com>

Ack. That works_for_me. Thanks.


> drivers/base/node.c | 6 +++++-
> 1 file changed, 5 insertions(+), 1 deletion(-)
>
> Index: linux-2.6.32-rc5-mmotm-091101-1001/drivers/base/node.c
> ===================================================================
> --- linux-2.6.32-rc5-mmotm-091101-1001.orig/drivers/base/node.c 2009-11-02 15:51:43.000000000 -0500
> +++ linux-2.6.32-rc5-mmotm-091101-1001/drivers/base/node.c 2009-11-02 16:41:36.000000000 -0500
> @@ -445,8 +445,12 @@ static int node_memory_callback(struct n
> }
> #endif /* CONFIG_HUGETLBFS */
> #else /* !CONFIG_MEMORY_HOTPLUG_SPARSE */
> +
> static int link_mem_sections(int nid) { return 0; }
> +#endif /* CONFIG_MEMORY_HOTPLUG_SPARSE */
>
> +#if !defined(CONFIG_MEMORY_HOTPLUG_SPARSE) || \
> + !defined(CONFIG_HUGETLBFS)
> static inline int node_memory_callback(struct notifier_block *self,
> unsigned long action, void *arg)
> {
> @@ -455,7 +459,7 @@ static inline int node_memory_callback(s
>
> static void init_node_hugetlb_work(int nid) { }
>
> -#endif /* CONFIG_MEMORY_HOTPLUG_SPARSE */
> +#endif
>
> int register_one_node(int nid)
> {
>
>


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


Since: Nov 04, 2006
Posts: 645



PostPosted: Mon Nov 02, 2009 7:10 pm    Post subject: kdump fails to load and crashes [was: mmotm 2009-11-01-10-01 uploaded] [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On 11/01/2009 07:07 PM, akpm.DeleteThis@linux-foundation.org wrote:
> The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to

Hi, kdump loading crashes:
BUG: unable to handle kernel paging request at ffff8800010a7000
IP: [<ffffffff8101cd8b>] machine_kexec_prepare+0x16b/0x13e0
PGD 1806063 PUD 180a063 PMD 10001e1
Oops: 0003 [#1] SMP
last sysfs file: /sys/firmware/memmap/10/type
CPU 1
Modules linked in: fuse ath5k ath
Pid: 3250, comm: kexec Tainted: G W 2.6.32-rc5-mm1_64 #869 To Be
Filled By O.E.M.
RIP: 0010:[<ffffffff8101cd8b>] [<ffffffff8101cd8b>]
machine_kexec_prepare+0x16b/0x13e0
RSP: 0018:ffff8801c95d1e88 EFLAGS: 00010206
RAX: 00000000000001e3 RBX: ffff8801ca2aac00 RCX: 0000000040000000
RDX: 0000000000200000 RSI: ffff8800010a7000 RDI: ffff8800010a7000
RBP: ffff8801c95d1ee8 R08: 00000000000010a7 R09: 00000000010a7fff
R10: 0000000000000fff R11: 0000000004ffffff R12: 0000000000000000
R13: ffff8800010a6000 R14: 0000008000000000 R15: ffff880000000000
FS: 00007f4f97b4c6f0(0000) GS:ffff880028280000(0000) knlGS:0000000000000000
CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
CR2: ffff8800010a7000 CR3: 00000001c8cf2000 CR4: 00000000000006e0
DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
Process kexec (pid: 3250, threadinfo ffff8801c95d0000, task
ffff8801ca116700)
Stack:
ffff8801c95d1ee8 ffff8800010a6000 ffff8800010a4000 ffff8800010a4000
<0> 0000000000000000 00000001cc000000 ffff8801c95d1ee8 0000000000000006
<0> ffff8801ca2aac00 0000000000000000 0000000000000000 000000000146eae0
Call Trace:
[<ffffffff8106d32c>] sys_kexec_load+0xec/0x5e0
[<ffffffff814365b5>] ? do_page_fault+0x185/0x350
[<ffffffff81002e6b>] system_call_fastpath+0x16/0x1b
Code: 00 40 48 c1 e6 0c 4c 01 fe 48 39 ca 73 21 48 89 f7 0f 1f 80 00 00
00 00 48 89 d0 48 81 c2 00 00 20 00 48 0d e3 01 00 00 48 39 d1 <48> ab
77 e9 48 89 f7 49 81 c4 00 00 00 40 e8 e2 93 00 00 4c 89
RIP [<ffffffff8101cd8b>] machine_kexec_prepare+0x16b/0x13e0
RSP <ffff8801c95d1e88>
CR2: ffff8800010a7000
---[ end trace 4eaa2a86a8e2da24 ]---

ffff8800010a7000 should be OK, as crashkernel=64M@16M was passed to the
kernel.

It's here:
static void init_level2_page(pmd_t *level2p, unsigned long addr)
{
unsigned long end_addr;

addr &= PAGE_MASK;
end_addr = addr + PUD_SIZE;
while (addr < end_addr) {
here -> set_pmd(level2p++, __pmd(addr | __PAGE_KERNEL_LARGE_EXEC));
addr += PMD_SIZE;
}
}

Corresponding -fverbose-asm with -g:
.loc 1 65 0
addq $2097152, %rdx #, addr
..LVL31:
..LBB416:
.loc 5 77 0
orq $483, %rax #, tmp140
..LBE416:
.loc 1 63 0
cmpq %rdx, %rcx # addr, end_addr
..LBB417:
.loc 5 77 0
stosq
..LVL32:
..LBE417:
.loc 1 63 0
ja .L26 #,



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


Since: Sep 13, 2006
Posts: 59



PostPosted: Mon Nov 02, 2009 7:10 pm    Post subject: [PATCH] hugetlb: offload per node attribute registrations fix [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Against: 2.6.32-rc5-mmotm-091101-1001

Fix build failure when MEMORY_HOTPLUG_SPARSE and !HUGETLBFS:

drivers/base/node.c:484: error: implicit declaration of function 'init_node_hugetlb_work'
drivers/base/node.c:582: error: 'node_memory_callback' undeclared (first use in this function)

Reported-by: Randy Dunlap <randy.dunlap.TakeThisOut@oracle.com>
Signed-off-by: Lee Schermerhorn <lee.schermerhorn.TakeThisOut@hp.com>

drivers/base/node.c | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)

Index: linux-2.6.32-rc5-mmotm-091101-1001/drivers/base/node.c
===================================================================
--- linux-2.6.32-rc5-mmotm-091101-1001.orig/drivers/base/node.c 2009-11-02 15:51:43.000000000 -0500
+++ linux-2.6.32-rc5-mmotm-091101-1001/drivers/base/node.c 2009-11-02 16:41:36.000000000 -0500
@@ -445,8 +445,12 @@ static int node_memory_callback(struct n
}
#endif /* CONFIG_HUGETLBFS */
#else /* !CONFIG_MEMORY_HOTPLUG_SPARSE */
+
static int link_mem_sections(int nid) { return 0; }
+#endif /* CONFIG_MEMORY_HOTPLUG_SPARSE */

+#if !defined(CONFIG_MEMORY_HOTPLUG_SPARSE) || \
+ !defined(CONFIG_HUGETLBFS)
static inline int node_memory_callback(struct notifier_block *self,
unsigned long action, void *arg)
{
@@ -455,7 +459,7 @@ static inline int node_memory_callback(s

static void init_node_hugetlb_work(int nid) { }

-#endif /* CONFIG_MEMORY_HOTPLUG_SPARSE */
+#endif

int register_one_node(int nid)
{


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


Since: Mar 12, 2009
Posts: 46



PostPosted: Tue Nov 03, 2009 10:10 am    Post subject: Re: kdump fails to load and crashes [was: mmotm 2009-11-01-10-01 uploaded] [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Tue, Nov 03, 2009 at 12:11:58AM +0100, Jiri Slaby wrote:
> On 11/01/2009 07:07 PM, akpm.DeleteThis@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to
>
> Hi, kdump loading crashes:
> BUG: unable to handle kernel paging request at ffff8800010a7000
> IP: [<ffffffff8101cd8b>] machine_kexec_prepare+0x16b/0x13e0
> PGD 1806063 PUD 180a063 PMD 10001e1
> Oops: 0003 [#1] SMP
> last sysfs file: /sys/firmware/memmap/10/type
> CPU 1
> Modules linked in: fuse ath5k ath
> Pid: 3250, comm: kexec Tainted: G W 2.6.32-rc5-mm1_64 #869 To Be
> Filled By O.E.M.
> RIP: 0010:[<ffffffff8101cd8b>] [<ffffffff8101cd8b>]
> machine_kexec_prepare+0x16b/0x13e0
> RSP: 0018:ffff8801c95d1e88 EFLAGS: 00010206
> RAX: 00000000000001e3 RBX: ffff8801ca2aac00 RCX: 0000000040000000
> RDX: 0000000000200000 RSI: ffff8800010a7000 RDI: ffff8800010a7000
> RBP: ffff8801c95d1ee8 R08: 00000000000010a7 R09: 00000000010a7fff
> R10: 0000000000000fff R11: 0000000004ffffff R12: 0000000000000000
> R13: ffff8800010a6000 R14: 0000008000000000 R15: ffff880000000000
> FS: 00007f4f97b4c6f0(0000) GS:ffff880028280000(0000) knlGS:0000000000000000
> CS: 0010 DS: 0000 ES: 0000 CR0: 0000000080050033
> CR2: ffff8800010a7000 CR3: 00000001c8cf2000 CR4: 00000000000006e0
> DR0: 0000000000000000 DR1: 0000000000000000 DR2: 0000000000000000
> DR3: 0000000000000000 DR6: 00000000ffff0ff0 DR7: 0000000000000400
> Process kexec (pid: 3250, threadinfo ffff8801c95d0000, task
> ffff8801ca116700)
> Stack:
> ffff8801c95d1ee8 ffff8800010a6000 ffff8800010a4000 ffff8800010a4000
> <0> 0000000000000000 00000001cc000000 ffff8801c95d1ee8 0000000000000006
> <0> ffff8801ca2aac00 0000000000000000 0000000000000000 000000000146eae0
> Call Trace:
> [<ffffffff8106d32c>] sys_kexec_load+0xec/0x5e0
> [<ffffffff814365b5>] ? do_page_fault+0x185/0x350
> [<ffffffff81002e6b>] system_call_fastpath+0x16/0x1b
> Code: 00 40 48 c1 e6 0c 4c 01 fe 48 39 ca 73 21 48 89 f7 0f 1f 80 00 00
> 00 00 48 89 d0 48 81 c2 00 00 20 00 48 0d e3 01 00 00 48 39 d1 <48> ab
> 77 e9 48 89 f7 49 81 c4 00 00 00 40 e8 e2 93 00 00 4c 89
> RIP [<ffffffff8101cd8b>] machine_kexec_prepare+0x16b/0x13e0
> RSP <ffff8801c95d1e88>
> CR2: ffff8800010a7000
> ---[ end trace 4eaa2a86a8e2da24 ]---
>
> ffff8800010a7000 should be OK, as crashkernel=64M@16M was passed to the
> kernel.
>

This is strange. As you said, ffff8800010a7000, should be a valid address
as you reserved memory from 16M.

I took above -mm and for me kernel loads fine. I reserved memory 64M@32M
as by default kernel is loading at address 16M.

How does your /proc/iomem look like in first kernel?

Thanks
Vivek

> It's here:
> static void init_level2_page(pmd_t *level2p, unsigned long addr)
> {
> unsigned long end_addr;
>
> addr &= PAGE_MASK;
> end_addr = addr + PUD_SIZE;
> while (addr < end_addr) {
> here -> set_pmd(level2p++, __pmd(addr | __PAGE_KERNEL_LARGE_EXEC));
> addr += PMD_SIZE;
> }
> }
>
> Corresponding -fverbose-asm with -g:
> .loc 1 65 0
> addq $2097152, %rdx #, addr
> .LVL31:
> .LBB416:
> .loc 5 77 0
> orq $483, %rax #, tmp140
> .LBE416:
> .loc 1 63 0
> cmpq %rdx, %rcx # addr, end_addr
> .LBB417:
> .loc 5 77 0
> stosq
> .LVL32:
> .LBE417:
> .loc 1 63 0
> ja .L26 #,
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.DeleteThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top
Jiri Slaby
External


Since: Nov 04, 2006
Posts: 645



PostPosted: Tue Nov 03, 2009 11:10 am    Post subject: Re: kdump fails to load and crashes [was: mmotm 2009-11-01-10-01 uploaded] [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On 11/03/2009 03:44 PM, Vivek Goyal wrote:
> On Tue, Nov 03, 2009 at 12:11:58AM +0100, Jiri Slaby wrote:
>> On 11/01/2009 07:07 PM, akpm.RemoveThis@linux-foundation.org wrote:
>>> The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to
>>
>> Hi, kdump loading crashes:
>> BUG: unable to handle kernel paging request at ffff8800010a7000
>> IP: [<ffffffff8101cd8b>] machine_kexec_prepare+0x16b/0x13e0
>> PGD 1806063 PUD 180a063 PMD 10001e1
....
>> ffff8800010a7000 should be OK, as crashkernel=64M@16M was passed to the
>> kernel.
>>
>
> This is strange. As you said, ffff8800010a7000, should be a valid address
> as you reserved memory from 16M.

Hmm, PMD has not RW bit set and we do store (see below).

> I took above -mm and for me kernel loads fine. I reserved memory 64M@32M
> as by default kernel is loading at address 16M.
>
> How does your /proc/iomem look like in first kernel?

I'm not any longer on that machine. init_pgtable() overwrites random
memory, so possibly even host's page tables, hence the oops above, I
suppose.

I'm currently chasing it down in the qemu virtual machine, since I
already got a garbage into my ~/.viminfo (some overwritten page got
flushed, I guess).

There /proc/iomem looks like:
00100000-12beffff : System RAM
01000000-04ffffff : Crash kernel
01000000-014680c2 : Kernel code
014680c3-016f39f7 : Kernel data
0175b000-017d97ab : Kernel bss

I'll keep you informed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.RemoveThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top
Vivek Goyal
External


Since: Mar 12, 2009
Posts: 46



PostPosted: Tue Nov 03, 2009 11:10 am    Post subject: Re: kdump fails to load and crashes [was: mmotm 2009-11-01-10-01 uploaded] [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Tue, Nov 03, 2009 at 04:14:25PM +0100, Jiri Slaby wrote:
> On 11/03/2009 03:44 PM, Vivek Goyal wrote:
> > On Tue, Nov 03, 2009 at 12:11:58AM +0100, Jiri Slaby wrote:
> >> On 11/01/2009 07:07 PM, akpm.DeleteThis@linux-foundation.org wrote:
> >>> The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to
> >>
> >> Hi, kdump loading crashes:
> >> BUG: unable to handle kernel paging request at ffff8800010a7000
> >> IP: [<ffffffff8101cd8b>] machine_kexec_prepare+0x16b/0x13e0
> >> PGD 1806063 PUD 180a063 PMD 10001e1
> ...
> >> ffff8800010a7000 should be OK, as crashkernel=64M@16M was passed to the
> >> kernel.
> >>
> >
> > This is strange. As you said, ffff8800010a7000, should be a valid address
> > as you reserved memory from 16M.
>
> Hmm, PMD has not RW bit set and we do store (see below).
>
> > I took above -mm and for me kernel loads fine. I reserved memory 64M@32M
> > as by default kernel is loading at address 16M.
> >
> > How does your /proc/iomem look like in first kernel?
>
> I'm not any longer on that machine. init_pgtable() overwrites random
> memory, so possibly even host's page tables, hence the oops above, I
> suppose.
>
> I'm currently chasing it down in the qemu virtual machine, since I
> already got a garbage into my ~/.viminfo (some overwritten page got
> flushed, I guess).
>
> There /proc/iomem looks like:
> 00100000-12beffff : System RAM
> 01000000-04ffffff : Crash kernel
> 01000000-014680c2 : Kernel code
> 014680c3-016f39f7 : Kernel data
> 0175b000-017d97ab : Kernel bss

Hmm.., this looks fishy. Reserved memory is starting at 16MB at the same
time first kernel is loaded at 16MB. So when we try to load a crash kernel
it can try to overwrite existing kernel.

In the past if crash kernel memory area used to overlap with kernel code,
data or bss, we would not reserve the memory for "Crash Kernel" and this
entry would not appear in /proc/iomem. Not sure what has changed.

Anyway, can you just try reserving memory at some other address, say
64M@32M and see if it works.

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


Since: Nov 04, 2006
Posts: 645



PostPosted: Tue Nov 03, 2009 11:10 am    Post subject: Re: kdump fails to load and crashes [was: mmotm 2009-11-01-10-01 uploaded] [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On 11/03/2009 04:24 PM, Vivek Goyal wrote:
>> There /proc/iomem looks like:
>> 00100000-12beffff : System RAM
>> 01000000-04ffffff : Crash kernel
>> 01000000-014680c2 : Kernel code
>> 014680c3-016f39f7 : Kernel data
>> 0175b000-017d97ab : Kernel bss
....
> Anyway, can you just try reserving memory at some other address, say
> 64M@32M and see if it works.

Yup, that's it of course. I missed it overlaps with current kernel. I
though they are areas for the crash kernels. Thanks for pointing out. So
the error is we reserve the space for kdump even we can't in fact?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo DeleteThis @vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top
Andrew Morton
External


Since: Feb 02, 2007
Posts: 2302



PostPosted: Wed Nov 04, 2009 1:10 am    Post subject: Re: vga_arb warning [was: mmotm 2009-11-01-10-01 uploaded] [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

Please cc me on mmotm bug reports!

On Sun, 01 Nov 2009 22:47:05 +0100 Jiri Slaby <jirislaby.DeleteThis@gmail.com> wrote:

> On 11/01/2009 07:07 PM, akpm.DeleteThis@linux-foundation.org wrote:
> > The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to
>
> Hi, I got the following warning while booting an image in qemu-kvm:
>
> WARNING: at fs/attr.c:158 notify_change+0x2da/0x310()
> Hardware name:
> Modules linked in:
> Pid: 1, comm: swapper Not tainted 2.6.32-rc5-mm1_64 #862
> Call Trace:
> [<ffffffff81038008>] warn_slowpath_common+0x78/0xb0
> [<ffffffff8103804f>] warn_slowpath_null+0xf/0x20
> [<ffffffff810d32ba>] notify_change+0x2da/0x310
> [<ffffffff810c5b88>] ? fsnotify_create+0x48/0x60
> [<ffffffff810c6d2b>] ? vfs_mknod+0xbb/0xe0
> [<ffffffff812487b6>] devtmpfs_create_node+0x1e6/0x270
> [<ffffffff811170d0>] ? sysfs_addrm_finish+0x20/0x280
> [<ffffffff811175d6>] ? __sysfs_add_one+0x26/0xf0
> [<ffffffff81117b6c>] ? sysfs_do_create_link+0xcc/0x160
> [<ffffffff81241cf0>] device_add+0x1e0/0x5b0
> [<ffffffff8124adb1>] ? pm_runtime_init+0xa1/0xb0
> [<ffffffff81248f05>] ? device_pm_init+0x65/0x70
> [<ffffffff812420d9>] device_register+0x19/0x20
> [<ffffffff81242290>] device_create_vargs+0xf0/0x120
> [<ffffffff812422ec>] device_create+0x2c/0x30
> [<ffffffff810c0516>] ? __register_chrdev+0x86/0xf0
> [<ffffffff81245599>] ? __class_create+0x69/0xa0
> [<ffffffff814326e9>] ? mutex_lock+0x19/0x50
> [<ffffffff811d4e23>] misc_register+0x93/0x170
> [<ffffffff818994a0>] ? vga_arb_device_init+0x0/0x77
> [<ffffffff818994b3>] vga_arb_device_init+0x13/0x77
> [<ffffffff818994a0>] ? vga_arb_device_init+0x0/0x77
> [<ffffffff810001e7>] do_one_initcall+0x37/0x190
> [<ffffffff8187d6ce>] kernel_init+0x172/0x1c8
> [<ffffffff81003c7a>] child_rip+0xa/0x20
> [<ffffffff8187d55c>] ? kernel_init+0x0/0x1c8
> [<ffffffff81003c70>] ? child_rip+0x0/0x20

There's a -mm-only debug patch:

http://userweb.kernel.org/~akpm/mmotm/broken-out/notify_change-callers...st-hold

--- a/fs/attr.c~notify_change-callers-must-hold-i_mutex
+++ a/fs/attr.c
@@ -155,6 +155,8 @@ int notify_change(struct dentry * dentry
return -EPERM;
}

+ WARN_ON_ONCE(!mutex_is_locked(&inode->i_mutex));
+
now = current_fs_time(inode->i_sb);

attr->ia_ctime = now;
_

I forget why it was added.


It looks like it's blaming the open-coded notify_change() call in
devtmpfs_create_node().

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


Since: May 14, 2006
Posts: 943



PostPosted: Thu Nov 05, 2009 3:10 pm    Post subject: Re: mmotm 2009-11-01-10-01 uploaded [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Sun, 1 Nov 2009, akpm DeleteThis @linux-foundation.org wrote:

> The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to
>
> http://userweb.kernel.org/~akpm/mmotm/
>
> and will soon be available at

Does "soon" mean within this century ?

> git://git.zen-sources.org/zen/mmotm.git

# git pull git://git.zen-sources.org/zen/mmotm.git master
git.zen-sources.org[0: 216.98.141.250]: errno=Connection timed out
git.zen-sources.org[0: 69.72.142.98]: errno=Connection refused
fatal: unable to connect a socket (Connection refused)

Thanks,

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


Since: Apr 21, 2007
Posts: 137



PostPosted: Fri Nov 06, 2009 7:10 am    Post subject: Re: mmotm 2009-11-01-10-01 uploaded [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Fri, Nov 6, 2009 at 12:43 AM, Thomas Gleixner <tglx.DeleteThis@linutronix.de> wrote:
> On Sun, 1 Nov 2009, akpm.DeleteThis@linux-foundation.org wrote:
>
>> The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to
>>
>>    http://userweb.kernel.org/~akpm/mmotm/
>>
>> and will soon be available at
>
> Does "soon" mean within this century ?
>
>>    git://git.zen-sources.org/zen/mmotm.git
>
> # git pull git://git.zen-sources.org/zen/mmotm.git master
> git.zen-sources.org[0: 216.98.141.250]: errno=Connection timed out
> git.zen-sources.org[0: 69.72.142.98]: errno=Connection refused
> fatal: unable to connect a socket (Connection refused)
>
I've seen that too, in fact I can't even reach the domain. I've pinged
the owner but not heard back yet.

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


Since: Nov 06, 2009
Posts: 1



PostPosted: Fri Nov 06, 2009 8:10 am    Post subject: Re: mmotm 2009-11-01-10-01 uploaded [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Fri, Nov 6, 2009 at 6:38 PM, Balbir Singh <balbir.TakeThisOut@linux.vnet.ibm.com> wrote:
> On Fri, Nov 6, 2009 at 12:43 AM, Thomas Gleixner <tglx.TakeThisOut@linutronix.de> wrote:
>> On Sun, 1 Nov 2009, akpm.TakeThisOut@linux-foundation.org wrote:
>>
>>> The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to
>>>
>>>    http://userweb.kernel.org/~akpm/mmotm/
>>>
>>> and will soon be available at
>>
>> Does "soon" mean within this century ?
>>
>>>    git://git.zen-sources.org/zen/mmotm.git
>>
>> # git pull git://git.zen-sources.org/zen/mmotm.git master
>> git.zen-sources.org[0: 216.98.141.250]: errno=Connection timed out
>> git.zen-sources.org[0: 69.72.142.98]: errno=Connection refused
>> fatal: unable to connect a socket (Connection refused)
>>
> I've seen that too, in fact I can't even reach the domain. I've pinged
> the owner but not heard back yet.


FTR, it moved to git://zen-kernel.org/kernel/mmotm.git and the
ownership has changed.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.TakeThisOut@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top
Randy Dunlap
External


Since: Jun 15, 2006
Posts: 897



PostPosted: Fri Nov 06, 2009 2:10 pm    Post subject: Re: mmotm 2009-11-01-10-01 uploaded [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Fri, 6 Nov 2009 19:39:30 +0700 Emmanuel Benisty wrote:

> On Fri, Nov 6, 2009 at 6:38 PM, Balbir Singh <balbir.DeleteThis@linux.vnet.ibm.com> wrote:
> > On Fri, Nov 6, 2009 at 12:43 AM, Thomas Gleixner <tglx.DeleteThis@linutronix.de> wrote:
> >> On Sun, 1 Nov 2009, akpm.DeleteThis@linux-foundation.org wrote:
> >>
> >>> The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to
> >>>
> >>>    http://userweb.kernel.org/~akpm/mmotm/
> >>>
> >>> and will soon be available at
> >>
> >> Does "soon" mean within this century ?
> >>
> >>>    git://git.zen-sources.org/zen/mmotm.git
> >>
> >> # git pull git://git.zen-sources.org/zen/mmotm.git master
> >> git.zen-sources.org[0: 216.98.141.250]: errno=Connection timed out
> >> git.zen-sources.org[0: 69.72.142.98]: errno=Connection refused
> >> fatal: unable to connect a socket (Connection refused)
> >>
> > I've seen that too, in fact I can't even reach the domain. I've pinged
> > the owner but not heard back yet.
>
>
> FTR, it moved to git://zen-kernel.org/kernel/mmotm.git and the
> ownership has changed.

Thanks. so that mmotm.git is now 5 weeks old.
http://git.zen-kernel.org/?p=kernel/mmotm.git;a=summary

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


Since: Nov 04, 2006
Posts: 645



PostPosted: Sun Nov 08, 2009 9:10 am    Post subject: Re: mmotm 2009-11-01-10-01 uploaded [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On 11/06/2009 07:48 PM, Randy Dunlap wrote:
> Thanks. so that mmotm.git is now 5 weeks old.
> http://git.zen-kernel.org/?p=kernel/mmotm.git;a=summary

How did you find out? Don't get wrong by the topmost commit and tag dates...

It definitely looks weird, but is the latest Smile:
6 weeks ago: 2009-11-01-10-01

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


Since: Jun 15, 2006
Posts: 897



PostPosted: Sun Nov 08, 2009 1:10 pm    Post subject: Re: mmotm 2009-11-01-10-01 uploaded [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

On Sun, 08 Nov 2009 14:46:10 +0100 Jiri Slaby wrote:

> On 11/06/2009 07:48 PM, Randy Dunlap wrote:
> > Thanks. so that mmotm.git is now 5 weeks old.
> > http://git.zen-kernel.org/?p=kernel/mmotm.git;a=summary
>
> How did you find out? Don't get wrong by the topmost commit and tag dates...
>
> It definitely looks weird, but is the latest Smile:
> 6 weeks ago: 2009-11-01-10-01

OK. yes, weird.

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


Since: Jan 15, 2009
Posts: 112



PostPosted: Thu Nov 12, 2009 4:10 am    Post subject: Re: mmotm 2009-11-01-10-01 uploaded [Login to view extended thread Info.]
Archived from groups: per prev. post (more info?)

> On Sun, 1 Nov 2009, akpm.DeleteThis@linux-foundation.org wrote:
>
> > The mm-of-the-moment snapshot 2009-11-01-10-01 has been uploaded to
> >
> > http://userweb.kernel.org/~akpm/mmotm/
> >
> > and will soon be available at
>
> Does "soon" mean within this century ?
>
> > git://git.zen-sources.org/zen/mmotm.git
>
> # git pull git://git.zen-sources.org/zen/mmotm.git master
> git.zen-sources.org[0: 216.98.141.250]: errno=Connection timed out
> git.zen-sources.org[0: 69.72.142.98]: errno=Connection refused
> fatal: unable to connect a socket (Connection refused)
>
> Thanks,

I asked the same question to mmotm git tree maintainer last month.
Currently mmotm git was gone by unhappy thing. and akpm stoped his recovery.
because akpm plan to get -mm into linux-next. He said please wait few weeks.

I guess akpm is pretty busy now. (guessing because recent mmotm commit mail
was not so active). then, I'd like to answer you instead. I hope this mail help you.

Thanks.



--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo.DeleteThis@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Back to top
Display posts from previous:   
Post new topic   General Reply to Topic (not reply to a specific post)    Forums Home -> Kernel All times are: Eastern Time (US & Canada) (change)
Page 1 of 1

 
You can post new topics in this forum
You can reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum