From: Jon Mason <jdmason@kudzu.us>
To: Allen Hubbe <Allen.Hubbe@dell.com>
Cc: linux-ntb@googlegroups.com
Subject: Re: [PATCH] NTB: ntb_transport: fix debugfs_remove_recursive
Date: Tue, 10 Jan 2017 16:51:46 -0500 [thread overview]
Message-ID: <20170110215145.GC13381@kudzu.us> (raw)
In-Reply-To: <6f7341ada9073025b0172a2ab0decc084b4d2ef4.1482879327.git.Allen.Hubbe@dell.com>
On Tue, Dec 27, 2016 at 05:57:04PM -0500, Allen Hubbe wrote:
> The call to debugfs_remove_recursive(qp->debugfs_dir) of the sub-level
> directory must not be later than
> debugfs_remove_recursive(nt_debugfs_dir) of the top-level directory.
> Otherwise, the sub-level directory will not exist, and it would be
> invalid (panic) to attempt to remove it. This removes the top-level
> directory last, after sub-level directories have been cleaned up.
>
> Signed-off-by: Allen Hubbe <Allen.Hubbe@dell.com>
Applied to my ntb tree
Thanks,
Jon
> ---
> drivers/ntb/ntb_transport.c | 3 +--
> 1 file changed, 1 insertion(+), 2 deletions(-)
>
> diff --git a/drivers/ntb/ntb_transport.c b/drivers/ntb/ntb_transport.c
> index f81aa4b18d9f..0e18adb51e4e 100644
> --- a/drivers/ntb/ntb_transport.c
> +++ b/drivers/ntb/ntb_transport.c
> @@ -2273,9 +2273,8 @@ module_init(ntb_transport_init);
>
> static void __exit ntb_transport_exit(void)
> {
> - debugfs_remove_recursive(nt_debugfs_dir);
> -
> ntb_unregister_client(&ntb_transport_client);
> bus_unregister(&ntb_transport_bus);
> + debugfs_remove_recursive(nt_debugfs_dir);
> }
> module_exit(ntb_transport_exit);
> --
> 2.9.1
>
prev parent reply other threads:[~2017-01-10 21:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-27 22:57 [PATCH] NTB: ntb_transport: fix debugfs_remove_recursive Allen Hubbe
2017-01-10 21:51 ` Jon Mason [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=20170110215145.GC13381@kudzu.us \
--to=jdmason@kudzu.us \
--cc=Allen.Hubbe@dell.com \
--cc=linux-ntb@googlegroups.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