All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: "Darrick J. Wong" <darrick.wong@oracle.com>
Cc: Brian Foster <bfoster@redhat.com>, linux-xfs@vger.kernel.org
Subject: Re: [PATCH v2] xfs: fix spurious spin_is_locked() assert failures on non-smp kernels
Date: Thu, 8 Jun 2017 08:43:11 -0700	[thread overview]
Message-ID: <20170608154311.GA6956@infradead.org> (raw)
In-Reply-To: <20170608152607.GH4530@birch.djwong.org>

On Thu, Jun 08, 2017 at 08:26:07AM -0700, Darrick J. Wong wrote:
> Hmm.... do you want me to put this into 4.12?  It's sort of a regression
> introduced in -rc4, but on the other hand this seems to have been broken
> for quite a while for SMP=n && XFS_DEBUG=y and nobody complained...

Please add it to 4.12.  It's harmless, and the thing that triggered it
only was merged in 4.12-rc.

      parent reply	other threads:[~2017-06-08 15:43 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-07 13:00 [PATCH v2] xfs: fix spurious spin_is_locked() assert failures on non-smp kernels Brian Foster
2017-06-08  7:54 ` Christoph Hellwig
2017-06-08 15:26 ` Darrick J. Wong
2017-06-08 15:38   ` Brian Foster
2017-06-08 15:43   ` Christoph Hellwig [this message]

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=20170608154311.GA6956@infradead.org \
    --to=hch@infradead.org \
    --cc=bfoster@redhat.com \
    --cc=darrick.wong@oracle.com \
    --cc=linux-xfs@vger.kernel.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.