All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH 5/6] f2fs: set GFP_NOFS when moving inline dentries
Date: Tue, 10 Dec 2019 14:22:38 +0800	[thread overview]
Message-ID: <98bf2199-9555-f679-cfd0-385aa4374ac9@huawei.com> (raw)
In-Reply-To: <20191209222345.1078-5-jaegeuk@kernel.org>

On 2019/12/10 6:23, Jaegeuk Kim wrote:
> Otherwise, it can cause circular locking dependency reported by mm.
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,

WARNING: multiple messages have this Message-ID (diff)
From: Chao Yu <yuchao0@huawei.com>
To: Jaegeuk Kim <jaegeuk@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-f2fs-devel@lists.sourceforge.net>
Subject: Re: [f2fs-dev] [PATCH 5/6] f2fs: set GFP_NOFS when moving inline dentries
Date: Tue, 10 Dec 2019 14:22:38 +0800	[thread overview]
Message-ID: <98bf2199-9555-f679-cfd0-385aa4374ac9@huawei.com> (raw)
In-Reply-To: <20191209222345.1078-5-jaegeuk@kernel.org>

On 2019/12/10 6:23, Jaegeuk Kim wrote:
> Otherwise, it can cause circular locking dependency reported by mm.
> 
> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

Reviewed-by: Chao Yu <yuchao0@huawei.com>

Thanks,


_______________________________________________
Linux-f2fs-devel mailing list
Linux-f2fs-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-f2fs-devel

  reply	other threads:[~2019-12-10  6:22 UTC|newest]

Thread overview: 83+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-09 22:23 [PATCH 1/6] f2fs: call f2fs_balance_fs outside of locked page Jaegeuk Kim
2019-12-09 22:23 ` [f2fs-dev] " Jaegeuk Kim
2019-12-09 22:23 ` [PATCH 2/6] f2fs: declare nested quota_sem and remove unnecessary sems Jaegeuk Kim
2019-12-09 22:23   ` [f2fs-dev] " Jaegeuk Kim
2019-12-10  6:20   ` Chao Yu
2019-12-10  6:20     ` Chao Yu
2019-12-09 22:23 ` [PATCH 3/6] f2fs: keep quota data on write_begin failure Jaegeuk Kim
2019-12-09 22:23   ` [f2fs-dev] " Jaegeuk Kim
2019-12-10  6:22   ` Chao Yu
2019-12-10  6:22     ` Chao Yu
2019-12-09 22:23 ` [PATCH 4/6] f2fs: should avoid recursive filesystem ops Jaegeuk Kim
2019-12-09 22:23   ` [f2fs-dev] " Jaegeuk Kim
2019-12-10  6:22   ` Chao Yu
2019-12-10  6:22     ` Chao Yu
2019-12-09 22:23 ` [PATCH 5/6] f2fs: set GFP_NOFS when moving inline dentries Jaegeuk Kim
2019-12-09 22:23   ` [f2fs-dev] " Jaegeuk Kim
2019-12-10  6:22   ` Chao Yu [this message]
2019-12-10  6:22     ` Chao Yu
2019-12-09 22:23 ` [PATCH 6/6] f2fs: set I_LINKABLE early to avoid wrong access by vfs Jaegeuk Kim
2019-12-09 22:23   ` [f2fs-dev] " Jaegeuk Kim
2019-12-10  6:37   ` Chao Yu
2019-12-10  6:37     ` Chao Yu
2019-12-11  1:21     ` Jaegeuk Kim
2019-12-11  1:21       ` Jaegeuk Kim
2019-12-11  1:23       ` Chao Yu
2019-12-11  1:23         ` Chao Yu
2019-12-11  1:31         ` Jaegeuk Kim
2019-12-11  1:31           ` Jaegeuk Kim
2019-12-11  1:42           ` Chao Yu
2019-12-11  1:42             ` Chao Yu
2019-12-12 16:55             ` Jaegeuk Kim
2019-12-12 16:55               ` Jaegeuk Kim
2019-12-10  2:09 ` [f2fs-dev] [PATCH 1/6] f2fs: call f2fs_balance_fs outside of locked page Chao Yu
2019-12-10  2:09   ` Chao Yu
2020-02-22  4:46 ` Ondřej Jirman
2020-02-22  4:46   ` [f2fs-dev] " Ondřej Jirman
2020-02-22 18:17   ` Writes stoped working on f2fs after the compression support was added Ondřej Jirman
2020-02-22 18:17     ` [f2fs-dev] " Ondřej Jirman
2020-02-24 10:37     ` Chao Yu
2020-02-24 10:37       ` [f2fs-dev] " Chao Yu
2020-02-24 10:41       ` Chao Yu
2020-02-24 10:41         ` Chao Yu
2020-02-24 13:58         ` Ondřej Jirman
2020-02-24 13:58           ` Ondřej Jirman
2020-02-24 14:03           ` Ondřej Jirman
2020-02-24 14:03             ` Ondřej Jirman
2020-02-24 14:31             ` Ondřej Jirman
2020-02-24 14:31               ` Ondřej Jirman
2020-02-25 11:24               ` Chao Yu
2020-02-25 11:24                 ` Chao Yu
2020-02-25 11:32                 ` Chao Yu
2020-02-25 11:32                   ` Chao Yu
2020-02-25 12:08                 ` Ondřej Jirman
2020-02-25 12:08                   ` Ondřej Jirman
2020-02-25 12:27                   ` Ondřej Jirman
2020-02-25 12:27                     ` Ondřej Jirman
2020-02-26  1:58                     ` Chao Yu
2020-02-26  1:58                       ` Chao Yu
2020-02-26 12:11                       ` Ondřej Jirman
2020-02-26 12:11                         ` Ondřej Jirman
2020-02-26 18:05                         ` Ondřej Jirman
2020-02-26 18:05                           ` Ondřej Jirman
2020-02-27  2:01                           ` Chao Yu
2020-02-27  2:01                             ` Chao Yu
2020-03-06 12:02                             ` Ondřej Jirman
2020-03-06 12:02                               ` Ondřej Jirman
2020-03-06 12:43                               ` Ondřej Jirman
2020-03-06 12:43                                 ` Ondřej Jirman
2020-03-11  9:02                               ` Chao Yu
2020-03-11  9:02                                 ` Chao Yu
2020-03-11 10:33                                 ` Ondřej Jirman
2020-03-11 10:33                                   ` Ondřej Jirman
2020-03-11 10:51                                   ` Chao Yu
2020-03-11 10:51                                     ` Chao Yu
2020-03-11 11:01                                     ` Ondřej Jirman
2020-03-11 11:01                                       ` Ondřej Jirman
2020-03-11 12:13                                       ` Chao Yu
2020-03-11 17:01                               ` Jaegeuk Kim
2020-03-11 17:01                                 ` Jaegeuk Kim
2020-03-22 10:15                                 ` Chao Yu
2020-03-22 10:15                                   ` Chao Yu
2020-02-24 14:20         ` Ondřej Jirman
2020-02-24 14:20           ` Ondřej Jirman

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=98bf2199-9555-f679-cfd0-385aa4374ac9@huawei.com \
    --to=yuchao0@huawei.com \
    --cc=jaegeuk@kernel.org \
    --cc=linux-f2fs-devel@lists.sourceforge.net \
    --cc=linux-kernel@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.