Re: [PATCH v2 09/11] docs: Fix some broken references
On Wed, 9 May 2018 10:18:52 -0300 Mauro Carvalho Chehab <mchehab+sams...@kernel.org> wrote: > As we move stuff around, some doc references are broken. Fix some of > them via this script: > ./scripts/documentation-file-ref-check --fix-rst > > Manually checked if the produced result is valid, removing a few > false-positives. The part of kprobes and trace_kprobe changes look good to me :) Acked-by: Masami Hiramatsu <mhira...@kernel.org> Thank you, > > Signed-off-by: Mauro Carvalho Chehab <mchehab+sams...@kernel.org> > --- > .../admin-guide/kernel-parameters.txt | 4 ++-- > .../bindings/input/rotary-encoder.txt | 2 +- > Documentation/driver-api/gpio/consumer.rst| 2 +- > Documentation/kprobes.txt | 4 ++-- > Documentation/trace/coresight.txt | 2 +- > Documentation/trace/events.rst| 2 +- > Documentation/trace/ftrace-uses.rst | 2 +- > Documentation/trace/histogram.txt | 2 +- > Documentation/trace/intel_th.rst | 2 +- > Documentation/trace/tracepoint-analysis.rst | 6 +++--- > Documentation/translations/ja_JP/howto.rst| 4 ++-- > .../translations/zh_CN/magic-number.txt | 4 ++-- > .../zh_CN/video4linux/omap3isp.txt| 4 ++-- > MAINTAINERS | 20 +-- > arch/Kconfig | 2 +- > arch/arm/include/asm/cacheflush.h | 2 +- > arch/arm64/include/asm/cacheflush.h | 2 +- > arch/microblaze/include/asm/cacheflush.h | 2 +- > arch/um/Kconfig.um| 2 +- > arch/unicore32/include/asm/cacheflush.h | 2 +- > arch/x86/entry/vsyscall/vsyscall_64.c | 2 +- > arch/xtensa/include/asm/cacheflush.h | 4 ++-- > block/Kconfig | 2 +- > certs/Kconfig | 2 +- > crypto/asymmetric_keys/asymmetric_type.c | 2 +- > crypto/asymmetric_keys/signature.c| 2 +- > drivers/char/Kconfig | 2 +- > drivers/clk/clk.c | 4 ++-- > drivers/clk/ingenic/cgu.h | 2 +- > drivers/gpu/vga/Kconfig | 2 +- > drivers/gpu/vga/vgaarb.c | 2 +- > drivers/input/joystick/Kconfig| 10 +- > drivers/input/joystick/iforce/Kconfig | 2 +- > drivers/input/joystick/walkera0701.c | 2 +- > drivers/input/misc/Kconfig| 4 ++-- > drivers/input/misc/rotary_encoder.c | 2 +- > drivers/input/mouse/Kconfig | 6 +++--- > drivers/input/mouse/alps.c| 2 +- > drivers/input/touchscreen/wm97xx-core.c | 2 +- > drivers/lightnvm/pblk-rb.c| 2 +- > drivers/md/bcache/Kconfig | 2 +- > drivers/md/bcache/btree.c | 2 +- > drivers/md/bcache/extents.c | 2 +- > drivers/media/dvb-core/dvb_ringbuffer.c | 2 +- > drivers/media/pci/meye/Kconfig| 2 +- > drivers/media/platform/pxa_camera.c | 4 ++-- > .../soc_camera/sh_mobile_ceu_camera.c | 2 +- > drivers/media/radio/Kconfig | 2 +- > drivers/media/radio/si470x/Kconfig| 2 +- > drivers/media/usb/dvb-usb-v2/lmedm04.c| 2 +- > drivers/media/usb/zr364xx/Kconfig | 2 +- > drivers/parport/Kconfig | 6 +++--- > drivers/staging/media/bcm2048/TODO| 2 +- > include/keys/asymmetric-subtype.h | 2 +- > include/keys/asymmetric-type.h| 2 +- > include/linux/assoc_array.h | 2 +- > include/linux/assoc_array_priv.h | 2 +- > include/linux/circ_buf.h | 2 +- > include/linux/ftrace.h| 2 +- > include/linux/rculist_nulls.h | 2 +- > include/uapi/linux/prctl.h| 2 +- > include/xen/interface/io/kbdif.h | 2 +- > kernel/cgroup/cpuset.c| 2 +- > kernel/trace/Kconfig | 16 +++ > lib/Kconfig | 2 +- > security/selinux/hooks.c | 2 +- > sound/core/Kconfig| 4 ++-- > sound/drivers/Kconfig | 4 ++-- > sound/pci/Kconfig | 10 +- > tools/include/uapi/linux/prctl.h | 2 +- > tools/lib/api/fs/fs.c | 2 +- > tools/memory-model/R
[lockdep] drm/i915: possible circular locking dependency in i915 driver init
On Mon, 15 Aug 2016 08:39:29 +0200
Daniel Vetter wrote:
> On Sun, Aug 14, 2016 at 11:01:35PM +0900, Masami Hiramatsu wrote:
> > Hello,
> >
> > I've found a suspicious circular locking dependency in i915 by lockdep.
> > It seems main driver initialization thread and sub fbdev configuration
> > thread take locks in different order implicitly. Please check it.
> >
> > The lockdep report is here.
>
> Should be fixed in 4.8-rc2, please confirm.
Thanks! I've confirmed this has fixed on 4.8-rc2.
Regards,
> -Daniel
>
> >
> > [4.254984] ==
> > [4.254984] [ INFO: possible circular locking dependency detected ]
> > [4.254985] 4.8.0-rc1+ #8 Not tainted
> > [4.254985] ---
> > [4.254986] kworker/u16:1/72 is trying to acquire lock:
> > [4.255001] (>mode_config.mutex){+.+.+.}, at: []
> > drm_modeset_lock_all+0x40/0x130 [drm]
> > [4.255001]
> >but task is already holding lock:
> > [4.255005] ((fb_notifier_list).rwsem){.+}, at:
> > [] __blocking_notifier_call_chain+0x35/0x70
> > [4.255005]
> >which lock already depends on the new lock.
> >
> > [4.255005]
> >the existing dependency chain (in reverse order) is:
> > [4.255006]
> >-> #1 ((fb_notifier_list).rwsem){.+}:
> > [4.255009][] lock_acquire+0x100/0x1f0
> > [4.255011][] down_write+0x49/0x80
> > [4.255013][]
> > blocking_notifier_chain_register+0x21/0xb0
> > [4.255015][] fb_register_client+0x18/0x20
> > [4.255016][]
> > backlight_device_register+0x12e/0x250
> > [4.255046][]
> > intel_backlight_device_register+0xa2/0x160 [i915]
> > [4.255070][]
> > intel_connector_register+0xe/0x10 [i915]
> > [4.255093][]
> > intel_dp_connector_register+0x1b/0x80 [i915]
> > [4.255102][] drm_connector_register+0x4a/0x80
> > [drm]
> > [4.255110][]
> > drm_modeset_register_all+0x1c6/0x260 [drm]
> > [4.255116][] drm_dev_register+0xc2/0xd0 [drm]
> > [4.255135][] i915_driver_load+0x771/0x1460
> > [i915]
> > [4.255153][] i915_pci_probe+0x4f/0x70 [i915]
> > [4.255155][] local_pci_probe+0x45/0xa0
> > [4.255157][] pci_device_probe+0xe1/0x130
> > [4.255159][] driver_probe_device+0x224/0x430
> > [4.255160][] __driver_attach+0xe3/0xf0
> > [4.255160][] bus_for_each_dev+0x66/0xa0
> > [4.255161][] driver_attach+0x1e/0x20
> > [4.255162][] bus_add_driver+0x200/0x270
> > [4.255164][] driver_register+0x60/0xe0
> > [4.255165][] __pci_register_driver+0x60/0x70
> > [4.255182][] i915_init+0x5b/0x62 [i915]
> > [4.255183][] do_one_initcall+0x3d/0x160
> > [4.255186][] do_init_module+0x5f/0x1f8
> > [4.255187][] load_module+0x246c/0x2bd0
> > [4.255188][] SYSC_finit_module+0xbc/0xf0
> > [4.255190][] SyS_finit_module+0xe/0x10
> > [4.255191][]
> > entry_SYSCALL_64_fastpath+0x23/0xc1
> > [4.255192]
> >-> #0 (>mode_config.mutex){+.+.+.}:
> > [4.255194][] __lock_acquire+0x125c/0x14b0
> > [4.255195][] lock_acquire+0x100/0x1f0
> > [4.255197][] mutex_lock_nested+0x69/0x3b0
> > [4.255206][] drm_modeset_lock_all+0x40/0x130
> > [drm]
> > [4.255212][]
> > drm_fb_helper_restore_fbdev_mode_unlocked+0x2b/0x80 [drm_kms_helper]
> > [4.255217][] drm_fb_helper_set_par+0x2d/0x50
> > [drm_kms_helper]
> > [4.255240][] intel_fbdev_set_par+0x1a/0x60
> > [i915]
> > [4.255242][] fbcon_init+0x57f/0x600
> > [4.255244][] visual_init+0xd6/0x130
> > [4.255245][] do_bind_con_driver+0x1c1/0x3a0
> > [4.255246][] do_take_over_console+0x116/0x180
> > [4.255247][] do_fbcon_takeover+0x57/0xb0
> > [4.255249][] fbcon_event_notify+0x658/0x750
> > [4.255250][] notifier_call_chain+0x4a/0x70
> > [4.255251][]
> > __blocking_notifier_call_chain+0x4d/0x70
> > [4.255253][]
> > blocking_notifier_call_chain+0x16/0x20
> > [4.255254][] fb_notifier_call_chain+0x1b/0x20
> > [4.
[lockdep] drm/i915: possible circular locking dependency in i915 driver init
not set I've hit this on my DELL XPS15 which has skylake CPU/GPU. Thanks, -- Masami Hiramatsu
