From: Stephen Rothwell <sfr@canb.auug.org.au>
To: Jaegeuk Kim <jaegeuk@kernel.org>, Theodore Ts'o <tytso@mit.edu>
Cc: linux-next@vger.kernel.org, linux-kernel@vger.kernel.org,
Eric Biggers <ebiggers@google.com>, Chao Yu <yuchao0@huawei.com>
Subject: linux-next: manual merge of the f2fs tree with the ext4 tree
Date: Mon, 19 Sep 2016 11:26:37 +1000 [thread overview]
Message-ID: <20160919112637.31d5eadd@canb.auug.org.au> (raw)
Hi Jaegeuk,
Today's linux-next merge of the f2fs tree got a conflict in:
fs/f2fs/dir.c
between commit:
59aa5a3aeead ("fscrypto: make filename crypto functions return 0 on success")
from the ext4 tree and commit:
e06f86e61d7a ("f2fs crypto: avoid unneeded memory allocation in ->readdir")
from the f2fs tree.
I fixed it up (see below) and can carry the fix as necessary. This
is now fixed as far as linux-next is concerned, but any non trivial
conflicts should be mentioned to your upstream maintainer when your tree
is submitted for merging. You may also want to consider cooperating
with the maintainer of the conflicting tree to minimise any particularly
complex conflicts.
--
Cheers,
Stephen Rothwell
diff --cc fs/f2fs/dir.c
index 8716943335b1,2fb20fc58346..000000000000
--- a/fs/f2fs/dir.c
+++ b/fs/f2fs/dir.c
@@@ -786,19 -813,12 +813,10 @@@ bool f2fs_fill_dentries(struct dir_cont
if (f2fs_encrypted_inode(d->inode)) {
int save_len = fstr->len;
- int err;
- int ret;
- de_name.name = f2fs_kmalloc(de_name.len, GFP_NOFS);
- if (!de_name.name)
- return false;
-
- memcpy(de_name.name, d->filename[bit_pos], de_name.len);
-
- err = fscrypt_fname_disk_to_usr(d->inode,
- ret = fscrypt_fname_disk_to_usr(d->inode,
++ if (fscrypt_fname_disk_to_usr(d->inode,
(u32)de->hash_code, 0,
-- &de_name, fstr);
- kfree(de_name.name);
- if (err)
- if (ret < 0)
++ &de_name, fstr))
return true;
de_name = *fstr;
next reply other threads:[~2016-09-19 1:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-19 1:26 Stephen Rothwell [this message]
-- strict thread matches above, loose matches on Subject: below --
2016-05-08 23:36 linux-next: manual merge of the f2fs tree with the ext4 tree Stephen Rothwell
2016-05-09 17:15 ` Jaegeuk Kim
2016-05-16 21:30 ` Theodore Ts'o
2016-05-16 22:22 ` Jaegeuk Kim
2016-05-16 23:55 ` Theodore Ts'o
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=20160919112637.31d5eadd@canb.auug.org.au \
--to=sfr@canb.auug.org.au \
--cc=ebiggers@google.com \
--cc=jaegeuk@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=tytso@mit.edu \
--cc=yuchao0@huawei.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