All of lore.kernel.org
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-xfs@vger.kernel.org
Subject: [Bug 206807] [xfstests generic/053]: WARNING: possible circular locking between fs_reclaim_acquire.part and xfs_ilock_attr_map_shared
Date: Tue, 10 Mar 2020 22:25:01 +0000	[thread overview]
Message-ID: <bug-206807-201763-jKOByzlC5Z@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-206807-201763@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=206807

--- Comment #1 from Dave Chinner (david@fromorbit.com) ---
On Tue, Mar 10, 2020 at 09:26:11AM +0000, bugzilla-daemon@bugzilla.kernel.org
wrote:
> https://bugzilla.kernel.org/show_bug.cgi?id=206807
> 
>             Bug ID: 206807
>            Summary: [xfstests generic/053]: WARNING: possible circular
>                     locking between fs_reclaim_acquire.part and
>                     xfs_ilock_attr_map_shared
>            Product: File System
>            Version: 2.5
>     Kernel Version: xfs-5.7-merge-1
>           Hardware: All
>                 OS: Linux
>               Tree: Mainline
>             Status: NEW
>           Severity: normal
>           Priority: P1
>          Component: XFS
>           Assignee: filesystem_xfs@kernel-bugs.kernel.org
>           Reporter: zlang@redhat.com
>         Regression: No
> 
> xfstests generic/053 always hit below warning. I'm not sure if it's a real
> issue, just due to it can be reproduced easily. So report this bug to get
> more
> xfs developer review.

False positive. Please close.

-Dave.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-03-10 22:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-03-10  9:26 [Bug 206807] New: [xfstests generic/053]: WARNING: possible circular locking between fs_reclaim_acquire.part and xfs_ilock_attr_map_shared bugzilla-daemon
2020-03-10 22:24 ` Dave Chinner
2020-03-10 22:25 ` bugzilla-daemon [this message]
2020-03-11  4:15 ` [Bug 206807] " bugzilla-daemon

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=bug-206807-201763-jKOByzlC5Z@https.bugzilla.kernel.org/ \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --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.