From: Oleg Nesterov <oleg@redhat.com>
To: Dave Chinner <david@fromorbit.com>
Cc: jack@suse.cz, xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] xfs: kill lockdep false positives from readdir
Date: Wed, 12 Aug 2015 13:42:25 +0200 [thread overview]
Message-ID: <20150812114225.GA3712@redhat.com> (raw)
In-Reply-To: <1439330648-1057-1-git-send-email-david@fromorbit.com>
On 08/12, Dave Chinner wrote:
>
> Oleg and Jan, this patchset should fix the lockdep issues that have
> been seen with the freeze rework. Oleg, can you you try it with your
> current patchset and testing and let me know if there are any issues
> that you see?
Tested-by: Oleg Nesterov <oleg@redhat.com>
To clarify, I tested these patches with
[PATCH v2 0/8] change sb_writers to use percpu_rw_semaphore
I sent yesterday first. Then I applied the additional patch (attached
below) which just restores the lockdep improvements from v1, everything
looks fine:
Ran: generic/068 generic/085 generic/280 generic/311 xfs/011 xfs/119 xfs/297
Passed all 7 tests
nothing interesting in dmesg.
Thanks Dave!
Oleg.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-08-12 11:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-11 22:04 [PATCH 0/2] xfs: kill lockdep false positives from readdir Dave Chinner
2015-08-11 22:04 ` [PATCH 1/2] xfs: clean up inode lockdep annotations Dave Chinner
2015-08-14 19:41 ` Brian Foster
2015-08-11 22:04 ` [PATCH 2/2] xfs: stop holding ILOCK over filldir callbacks Dave Chinner
2015-08-14 19:41 ` Brian Foster
2015-08-14 22:39 ` Dave Chinner
2015-08-15 13:01 ` Brian Foster
2015-08-15 22:56 ` Dave Chinner
2015-08-12 11:42 ` Oleg Nesterov [this message]
2015-08-12 11:43 ` [PATCH 0/2] xfs: kill lockdep false positives from readdir Oleg Nesterov
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=20150812114225.GA3712@redhat.com \
--to=oleg@redhat.com \
--cc=david@fromorbit.com \
--cc=jack@suse.cz \
--cc=xfs@oss.sgi.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox