All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: kbuild-all@lists.01.org
Subject: Re: [linux-stable-rc:linux-4.19.y 7762/7788] include/linux/spinlock.h:384:9: sparse: sparse: context imbalance in 'flush_end_io' - unexpected unlock
Date: Fri, 04 Oct 2019 10:03:09 +0200	[thread overview]
Message-ID: <20191004080309.GA27510@kroah.com> (raw)
In-Reply-To: <d9eb220f-517f-6f19-6423-7399153428c9@kernel.dk>

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

On Thu, Oct 03, 2019 at 08:33:38PM -0600, Jens Axboe wrote:
> On 10/3/19 8:20 PM, kbuild test robot wrote:
> > tree:   https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable-rc.git linux-4.19.y
> > head:   45830aebf3fc94937285ed325fdb97043f6b6108
> > commit: 9afbbbbab3cd79e3aa14edd4c6269e89eab79343 [7762/7788] block: fix null pointer dereference in blk_mq_rq_timed_out()
> > reproduce:
> >          # apt-get install sparse
> >          # sparse version: v0.6.1-rc1-7-g2b96cd8-dirty
> >          git checkout 9afbbbbab3cd79e3aa14edd4c6269e89eab79343
> >          make ARCH=x86_64 allmodconfig
> >          make C=1 CF='-fdiagnostic-prefix -D__CHECK_ENDIAN__'
> > 
> > If you fix the issue, kindly add following tag
> > Reported-by: kbuild test robot <lkp@intel.com>
> > 
> > 
> > sparse warnings: (new ones prefixed by >>)
> > 
> >>> include/linux/spinlock.h:384:9: sparse: sparse: context imbalance in 'flush_end_io' - unexpected unlock
> > 
> > vim +/flush_end_io +384 include/linux/spinlock.h
> > 
> > c2f21ce2e31286 Thomas Gleixner 2009-12-02  381
> > 3490565b633c70 Denys Vlasenko  2015-07-13  382  static __always_inline void spin_unlock_irqrestore(spinlock_t *lock, unsigned long flags)
> > c2f21ce2e31286 Thomas Gleixner 2009-12-02  383  {
> > c2f21ce2e31286 Thomas Gleixner 2009-12-02 @384  	raw_spin_unlock_irqrestore(&lock->rlock, flags);
> > c2f21ce2e31286 Thomas Gleixner 2009-12-02  385  }
> > c2f21ce2e31286 Thomas Gleixner 2009-12-02  386
> 
> This report looks bogus - both for mainline, and I checked that the 4.19
> backport is correct too.

Thanks for testing and verifying that this is sane.

greg k-h

       reply	other threads:[~2019-10-04  8:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d9eb220f-517f-6f19-6423-7399153428c9@kernel.dk>
2019-10-04  8:03 ` Greg Kroah-Hartman [this message]
2019-10-09  9:20 ` [linux-stable-rc:linux-4.19.y 7762/7788] include/linux/spinlock.h:384:9: sparse: sparse: context imbalance in 'flush_end_io' - unexpected unlock Rong Chen
2019-10-04  2:20 kbuild test robot

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20191004080309.GA27510@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=kbuild-all@lists.01.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.