1. 20 9月, 2018 5 次提交
  2. 08 9月, 2018 16 次提交
  3. 07 9月, 2018 14 次提交
  4. 06 9月, 2018 5 次提交
    • S
      printk/tracing: Do not trace printk_nmi_enter() · d1c392c9
      Steven Rostedt (VMware) 提交于
      I hit the following splat in my tests:
      
      ------------[ cut here ]------------
      IRQs not enabled as expected
      WARNING: CPU: 3 PID: 0 at kernel/time/tick-sched.c:982 tick_nohz_idle_enter+0x44/0x8c
      Modules linked in: ip6t_REJECT nf_reject_ipv6 ip6table_filter ip6_tables ipv6
      CPU: 3 PID: 0 Comm: swapper/3 Not tainted 4.19.0-rc2-test+ #2
      Hardware name: MSI MS-7823/CSM-H87M-G43 (MS-7823), BIOS V1.6 02/22/2014
      EIP: tick_nohz_idle_enter+0x44/0x8c
      Code: ec 05 00 00 00 75 26 83 b8 c0 05 00 00 00 75 1d 80 3d d0 36 3e c1 00
      75 14 68 94 63 12 c1 c6 05 d0 36 3e c1 01 e8 04 ee f8 ff <0f> 0b 58 fa bb a0
      e5 66 c1 e8 25 0f 04 00 64 03 1d 28 31 52 c1 8b
      EAX: 0000001c EBX: f26e7f8c ECX: 00000006 EDX: 00000007
      ESI: f26dd1c0 EDI: 00000000 EBP: f26e7f40 ESP: f26e7f38
      DS: 007b ES: 007b FS: 00d8 GS: 00e0 SS: 0068 EFLAGS: 00010296
      CR0: 80050033 CR2: 0813c6b0 CR3: 2f342000 CR4: 001406f0
      Call Trace:
       do_idle+0x33/0x202
       cpu_startup_entry+0x61/0x63
       start_secondary+0x18e/0x1ed
       startup_32_smp+0x164/0x168
      irq event stamp: 18773830
      hardirqs last  enabled at (18773829): [<c040150c>] trace_hardirqs_on_thunk+0xc/0x10
      hardirqs last disabled at (18773830): [<c040151c>] trace_hardirqs_off_thunk+0xc/0x10
      softirqs last  enabled at (18773824): [<c0ddaa6f>] __do_softirq+0x25f/0x2bf
      softirqs last disabled at (18773767): [<c0416bbe>] call_on_stack+0x45/0x4b
      ---[ end trace b7c64aa79e17954a ]---
      
      After a bit of debugging, I found what was happening. This would trigger
      when performing "perf" with a high NMI interrupt rate, while enabling and
      disabling function tracer. Ftrace uses breakpoints to convert the nops at
      the start of functions to calls to the function trampolines. The breakpoint
      traps disable interrupts and this makes calls into lockdep via the
      trace_hardirqs_off_thunk in the entry.S code. What happens is the following:
      
        do_idle {
      
          [interrupts enabled]
      
          <interrupt> [interrupts disabled]
      	TRACE_IRQS_OFF [lockdep says irqs off]
      	[...]
      	TRACE_IRQS_IRET
      	    test if pt_regs say return to interrupts enabled [yes]
      	    TRACE_IRQS_ON [lockdep says irqs are on]
      
      	    <nmi>
      		nmi_enter() {
      		    printk_nmi_enter() [traced by ftrace]
      		    [ hit ftrace breakpoint ]
      		    <breakpoint exception>
      			TRACE_IRQS_OFF [lockdep says irqs off]
      			[...]
      			TRACE_IRQS_IRET [return from breakpoint]
      			   test if pt_regs say interrupts enabled [no]
      			   [iret back to interrupt]
      	   [iret back to code]
      
          tick_nohz_idle_enter() {
      
      	lockdep_assert_irqs_enabled() [lockdep say no!]
      
      Although interrupts are indeed enabled, lockdep thinks it is not, and since
      we now do asserts via lockdep, it gives a false warning. The issue here is
      that printk_nmi_enter() is called before lockdep_off(), which disables
      lockdep (for this reason) in NMIs. By simply not allowing ftrace to see
      printk_nmi_enter() (via notrace annotation) we keep lockdep from getting
      confused.
      
      Cc: stable@vger.kernel.org
      Fixes: 42a0bb3f ("printk/nmi: generic solution for safe printk in NMI")
      Acked-by: NSergey Senozhatsky <sergey.senozhatsky@gmail.com>
      Acked-by: NPetr Mladek <pmladek@suse.com>
      Signed-off-by: NSteven Rostedt (VMware) <rostedt@goodmis.org>
      d1c392c9
    • I
      rbd: support cloning across namespaces · e92c0eaf
      Ilya Dryomov 提交于
      If parent_get class method is not supported by the OSDs, fall back to
      the legacy class method and assume that the parent is in the default
      (i.e. "") namespace.  The "use the child's image namespace" workaround
      is no longer needed because creating images within namespaces will
      require parent_get aware OSDs.
      Signed-off-by: NIlya Dryomov <idryomov@gmail.com>
      Reviewed-by: NJason Dillaman <dillaman@redhat.com>
      e92c0eaf
    • I
      rbd: factor out get_parent_info() · eb3b2d6b
      Ilya Dryomov 提交于
      In preparation for the new parent_get and parent_overlap_get class
      methods, factor out the fetching and decoding of parent data.
      
      As a side effect, we now decode all four fields in the "no parent"
      case.
      Signed-off-by: NIlya Dryomov <idryomov@gmail.com>
      Reviewed-by: NJason Dillaman <dillaman@redhat.com>
      eb3b2d6b
    • I
      ceph: avoid a use-after-free in ceph_destroy_options() · 8aaff151
      Ilya Dryomov 提交于
      syzbot reported a use-after-free in ceph_destroy_options(), called from
      ceph_mount().  The problem was that create_fs_client() consumed the opt
      pointer on some errors, but not on all of them.  Make sure it always
      consumes both libceph and ceph options.
      
      Reported-by: syzbot+8ab6f1042021b4eed062@syzkaller.appspotmail.com
      Signed-off-by: NIlya Dryomov <idryomov@gmail.com>
      Reviewed-by: N"Yan, Zheng" <zyan@redhat.com>
      8aaff151
    • Z
      ACPI / LPSS: Force LPSS quirks on boot · f11fc4bc
      Zhang Rui 提交于
      Commit 12864ff8 (ACPI / LPSS: Avoid PM quirks on suspend and resume
      from hibernation) bypasses lpss quirks for S3 and S4, by setting a flag
      for S3/S4 in acpi_lpss_suspend(), and check that flag in
      acpi_lpss_resume().
      
      But this overlooks the boot case where acpi_lpss_resume() may get called
      without a corresponding acpi_lpss_suspend() having been called.
      
      Thus force setting the flag during boot.
      
      Fixes: 12864ff8 (ACPI / LPSS: Avoid PM quirks on suspend and resume from hibernation)
      Link: https://bugzilla.kernel.org/show_bug.cgi?id=200989Reported-and-tested-by: NWilliam Lieurance <william.lieurance@namikoda.com>
      Signed-off-by: NZhang Rui <rui.zhang@intel.com>
      Cc: 4.15+ <stable@vger.kernel.org> # 4.15+: 12864ff8 (ACPI / LPSS: Avoid ...)
      Signed-off-by: NRafael J. Wysocki <rafael.j.wysocki@intel.com>
      f11fc4bc