Received: by 10.223.176.5 with SMTP id f5csp1967914wra; Wed, 31 Jan 2018 14:26:43 -0800 (PST) X-Google-Smtp-Source: AH8x224f8g0LB3MsGdohnbsijPsrExs8PvC57QubWhJmo+otnqmj+B9jQ+Okyy8VR4ucfidFDjF9 X-Received: by 2002:a17:902:694a:: with SMTP id k10-v6mr28537251plt.301.1517437603377; Wed, 31 Jan 2018 14:26:43 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1517437603; cv=none; d=google.com; s=arc-20160816; b=AWQmbEp844WHqktqLSSbsMximKgmriiVDs2/kRvpLcVnVmSK1pBnkArIMjXdr4GNP2 AfJsbk522Jc59/u5DqguFBcDczBq1YkGzI7iu0/ZKuEBic/WqhefKsKbNvfrytFqQ51T c4F16DYwzWqGaOqQTRCY6aS2EWiRFK3HTGdr9DrnxwEVKLwUQF+C5a95v5/xcOXO3hix t3c/YImp3/K9jblAo5z1GK/6YL/iWb8SzN6rTDgKUTpLxNF/iGA1ndVc1LzkDDm94ie3 oGWql3Q0wBnEjlm6iVUYgOMV07n+PAMkEpTm8BwVXVpEdIxKxueqmOdT6vXm/5p1Ta2W 676Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding:mime-version :references:in-reply-to:message-id:subject:cc:to:from:date :dkim-signature:arc-authentication-results; bh=LCo0XchQfDACZinDlZE7wudAUWQMGQxy8v2hhev3T4Q=; b=f/6K6l/B32GYYeFMQ4TwRCjjgE+jrF/DjsYqh+2AjWMf3TLyeC9+W8na7v9Zsj6YcP eQrGddoKO96GnrNrSV+2cA4MNzdtq3sE5MjWWrUJigPnYscqhAiETUT0e0LdVqb5pE0n OZFL76e+gY8aSkgowKSUKMymPGNcl28gxztAeKk0eey7SEMtDEF9KTmR7Wr+tc46ZtQr BToLL+uRdhdq7fnziWrY7PO3Koyx4/NBwkbmufdDJATzWz7nFgYIyJ3ijlZhqkudv+Qn 7VAQKxwaMS58g+hqqvOSB6mfFQk7dtSi5RvX8x057BxGwbJ/i+VfdkFbmPKAF6rfQ4zZ RgDw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@canb.auug.org.au header.s=201702 header.b=PcQLaw+7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id q184si4231577pga.242.2018.01.31.14.26.28; Wed, 31 Jan 2018 14:26:43 -0800 (PST) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; dkim=pass header.i=@canb.auug.org.au header.s=201702 header.b=PcQLaw+7; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751801AbeAaWZz (ORCPT + 99 others); Wed, 31 Jan 2018 17:25:55 -0500 Received: from ozlabs.org ([103.22.144.67]:60405 "EHLO ozlabs.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751643AbeAaWZy (ORCPT ); Wed, 31 Jan 2018 17:25:54 -0500 Received: from authenticated.ozlabs.org (localhost [127.0.0.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ozlabs.org (Postfix) with ESMTPSA id 3zWyWM74w7z9ryr; Thu, 1 Feb 2018 09:25:51 +1100 (AEDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=canb.auug.org.au; s=201702; t=1517437552; bh=cwCqzZSPmD5cJfjTg+43Kv71KUS0AxoHoaMF6WRG//o=; h=Date:From:To:Cc:Subject:In-Reply-To:References:From; b=PcQLaw+7vGOSh+roczRT8ZkQ/SYMpBvGORYuc5iL8oiSMBggDFmU3UehshL7aYD+D pHMRWNOXkwxF8C5hEHoGUck4M2oLhMe90ofwd4Rb8+tBegKT5E1/5iJP0E2ni9dCQR ywQHE/ztt9o/I0a4iaqiN/VwDAS73km7Sla8dEcvMXa0/CskSdqBi+YwmUzrI5GrID GCP9+J39fKIUApmjP3xyXYkATL2QMQEGs7UiNtEM5LvZNpZL6bpi7MtTPViVjOQMYm B2G0gxLqHTCDId5kHvpBkbMCDV6W40g//nO5qm2uqAQg6yd8uRS2jXesyfctSWQ6g3 iaxCznLP+K3Hg== Date: Thu, 1 Feb 2018 09:25:51 +1100 From: Stephen Rothwell To: Jaegeuk Kim Cc: Linus Torvalds , Linux F2FS Dev Mailing List , Linux Kernel Mailing List , Chris Mason , Josef Bacik , Yufen Yu , Tejun Heo Subject: Re: [GIT PULL] f2fs update for 4.16-rc1 Message-ID: <20180201092551.759f32be@canb.auug.org.au> In-Reply-To: <20180131002535.GD65489@jaegeuk-macbookpro.roam.corp.google.com> References: <20180130223220.GB65489@jaegeuk-macbookpro.roam.corp.google.com> <20180131095446.443670dc@canb.auug.org.au> <20180131002535.GD65489@jaegeuk-macbookpro.roam.corp.google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Jaegeuk, On Tue, 30 Jan 2018 16:25:35 -0800 Jaegeuk Kim wrote: > > On 01/31, Stephen Rothwell wrote: > > > > On Tue, 30 Jan 2018 14:32:20 -0800 Jaegeuk Kim wrote: > > > > > > Could you please consider the below pull request? > > > > > > Thanks, > > > > > > The following changes since commit ace52288edf0cb5e7a52b681f057f86224c49c27: > > > > > > Merge tag 'for-linus-20171218' of git://git.infradead.org/linux-mtd (2017-12-18 16:18:01 -0800) > > > > > > are available in the Git repository at: > > > > > > git://git.kernel.org/pub/scm/linux/kernel/git/jaegeuk/f2fs.git tags/f2fs-for-4.16-rc1 > > > > > > for you to fetch changes up to 1c1d35df71104c76a4a2e25862926f22c334c9d6: > > > > > > f2fs: support inode creation time (2018-01-25 14:10:39 -0800) > > > > This has an interesting conflict with the btrfs tree: > > > > ----------------------------------------------------------------------- > > After merging the f2fs tree, today's linux-next build (x86_64 > > allmodconfig) failed like this: > > > > /home/sfr/next/next/fs/f2fs/super.c: In function 'f2fs_fill_super': > > /home/sfr/next/next/fs/f2fs/super.c:2563:18: error: 'SB_I_CGROUPWB' undeclared (first use in this function); did you mean 'S_CGROUPWB'? > > sb->s_iflags |= SB_I_CGROUPWB; > > ^~~~~~~~~~~~~ > > S_CGROUPWB > > > > Caused by commit > > > > 578c647879f7 ("f2fs: implement cgroup writeback support") > > > > interacting with commit > > > > 34934189a3dd ("cgroup, writeback: replace SB_I_CGROUPWB with per-inode S_CGROUPWB" > > > > from the btrfs tree. > > > > I have reverted the f2fs tree commit for today, but a better resolution > > would be appreciated. > > ----------------------------------------------------------------------- > > > > I have seen no response to the above email and have been reverting that > > commit since Jan 18. > > I think this can be addressed by: > > diff --git a/fs/f2fs/inode.c b/fs/f2fs/inode.c > index 89c838bfb067..c743b73976d0 100644 > --- a/fs/f2fs/inode.c > +++ b/fs/f2fs/inode.c > @@ -48,9 +48,10 @@ void f2fs_set_inode_flags(struct inode *inode) > new_fl |= S_DIRSYNC; > if (f2fs_encrypted_inode(inode)) > new_fl |= S_ENCRYPTED; > + new_fl |= S_CGROUPWB; > inode_set_flags(inode, new_fl, > S_SYNC|S_APPEND|S_IMMUTABLE|S_NOATIME|S_DIRSYNC| > - S_ENCRYPTED); > + S_ENCRYPTED|S_CGROUPWB); > } > > static void __get_inode_rdev(struct inode *inode, struct f2fs_inode *ri) > diff --git a/fs/f2fs/super.c b/fs/f2fs/super.c > index 8173ae688814..ebcd58476fc7 100644 > --- a/fs/f2fs/super.c > +++ b/fs/f2fs/super.c > @@ -2560,7 +2560,6 @@ static int f2fs_fill_super(struct super_block *sb, void *data, int silent) > sb->s_flags = (sb->s_flags & ~SB_POSIXACL) | > (test_opt(sbi, POSIX_ACL) ? SB_POSIXACL : 0); > memcpy(&sb->s_uuid, raw_super->uuid, sizeof(raw_super->uuid)); > - sb->s_iflags |= SB_I_CGROUPWB; > > /* init f2fs-specific super block info */ > sbi->valid_super_block = valid_super_block; > I have applied that (by hand) as a merge fix patch for the merge of teh btrfs tree for today. Thanks for the resolution. -- Cheers, Stephen Rothwell