From: liubo <liubo254@huawei.com>
To: <akpm@linux-foundation.org>, <linux-mm@kvack.org>,
<linux-kernel@vger.kernel.org>
Cc: <ying.huang@intel.com>, <willy@infradead.org>, <vbabka@suse.cz>,
<surenb@google.com>, <peterx@redhat.com>, <neilb@suse.de>,
<naoya.horiguchi@nec.com>, <minchan@kernel.org>,
<linmiaohe@huawei.com>, <louhongxiang@huawei.com>,
<linfeilong@huawei.com>, <liubo254@huawei.com>
Subject: [PATCH v2 0/2] mm/swapfile: release swap info when swap device is unpluged
Date: Wed, 15 Jun 2022 15:02:26 +0800 [thread overview]
Message-ID: <20220615070228.2858170-1-liubo254@huawei.com> (raw)
This series patch try to fix the problem that the resources
corresponding to swap are not effectively released when
the swap partition disk is hot-pluged.
1/2: Extract operations of resource release in the swapoff process.
2/2: release swap info when swap device is unpluged
This is a second version, which addressed some comments:
1. turn first patch into a two patch series. The first does the
code movement with no functional changes and the second does
the actual fix.
---
For v1, see: https://lore.kernel.org/linux-mm/20220528084941.28391-1-liubo254@huawei.com/
---
liubo (2):
mm/swapfile: Extract operations of resource release in the swapoff
process
mm/swapfile: release swap info when swap device is unpluged
mm/swapfile.c | 261 +++++++++++++++++++++++++++++++++++---------------
1 file changed, 183 insertions(+), 78 deletions(-)
--
2.27.0
next reply other threads:[~2022-06-15 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 7:02 liubo [this message]
2022-06-15 7:02 ` [PATCH v2 1/2] mm/swapfile: Extract operations of resource release in the swapoff process liubo
2022-06-15 7:02 ` [PATCH v2 2/2] mm/swapfile: release swap info when swap device is unpluged liubo
2022-06-15 11:22 ` Christoph Hellwig
2022-06-16 7:00 ` Miaohe Lin
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=20220615070228.2858170-1-liubo254@huawei.com \
--to=liubo254@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linfeilong@huawei.com \
--cc=linmiaohe@huawei.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=louhongxiang@huawei.com \
--cc=minchan@kernel.org \
--cc=naoya.horiguchi@nec.com \
--cc=neilb@suse.de \
--cc=peterx@redhat.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=willy@infradead.org \
--cc=ying.huang@intel.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