linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
* linux-next: manual merge of the vfs tree with the ubifs tree
@ 2019-07-09  1:38 Stephen Rothwell
  0 siblings, 0 replies; 4+ messages in thread
From: Stephen Rothwell @ 2019-07-09  1:38 UTC (permalink / raw)
  To: Al Viro, Artem Bityutskiy
  Cc: Linux Next Mailing List, Linux Kernel Mailing List,
	David Howells, Michele Dionisio, Richard Weinberger

[-- Attachment #1: Type: text/plain, Size: 3736 bytes --]

Hi all,

Today's linux-next merge of the vfs tree got a conflict in:

  fs/ubifs/super.c

between commit:

  eeabb9866e4c ("ubifs: Add support for zstd compression.")

from the ubifs tree and commit:

  334d581528b9 ("vfs: Convert ubifs to use the new mount API")

from the vfs 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/ubifs/super.c
index 5c472cca3876,62f339d901c1..000000000000
--- a/fs/ubifs/super.c
+++ b/fs/ubifs/super.c
@@@ -939,49 -937,42 +939,43 @@@ enum 
  	Opt_auth_key,
  	Opt_auth_hash_name,
  	Opt_ignore,
- 	Opt_err,
  };
  
- static const match_table_t tokens = {
- 	{Opt_fast_unmount, "fast_unmount"},
- 	{Opt_norm_unmount, "norm_unmount"},
- 	{Opt_bulk_read, "bulk_read"},
- 	{Opt_no_bulk_read, "no_bulk_read"},
- 	{Opt_chk_data_crc, "chk_data_crc"},
- 	{Opt_no_chk_data_crc, "no_chk_data_crc"},
- 	{Opt_override_compr, "compr=%s"},
- 	{Opt_auth_key, "auth_key=%s"},
- 	{Opt_auth_hash_name, "auth_hash_name=%s"},
- 	{Opt_ignore, "ubi=%s"},
- 	{Opt_ignore, "vol=%s"},
- 	{Opt_assert, "assert=%s"},
- 	{Opt_err, NULL},
+ static const struct fs_parameter_spec ubifs_param_specs[] = {
+ 	fsparam_flag	("fast_unmount",		Opt_fast_unmount),
+ 	fsparam_flag	("norm_unmount",		Opt_norm_unmount),
+ 	fsparam_flag	("bulk_read",			Opt_bulk_read),
+ 	fsparam_flag	("no_bulk_read",		Opt_no_bulk_read),
+ 	fsparam_flag	("chk_data_crc",		Opt_chk_data_crc),
+ 	fsparam_flag	("no_chk_data_crc",		Opt_no_chk_data_crc),
+ 	fsparam_enum	("compr",			Opt_compr),
+ 	fsparam_enum	("assert",			Opt_assert),
+ 	fsparam_string	("auth_key",			Opt_auth_key),
+ 	fsparam_string	("auth_hash_name",		Opt_auth_hash_name),
+ 	fsparam_string	("ubi",				Opt_ignore),
+ 	fsparam_string	("vol",				Opt_ignore),
+ 	{}
  };
  
- /**
-  * parse_standard_option - parse a standard mount option.
-  * @option: the option to parse
-  *
-  * Normally, standard mount options like "sync" are passed to file-systems as
-  * flags. However, when a "rootflags=" kernel boot parameter is used, they may
-  * be present in the options string. This function tries to deal with this
-  * situation and parse standard options. Returns 0 if the option was not
-  * recognized, and the corresponding integer flag if it was.
-  *
-  * UBIFS is only interested in the "sync" option, so do not check for anything
-  * else.
-  */
- static int parse_standard_option(const char *option)
- {
+ static const struct fs_parameter_enum ubifs_param_enums[] = {
+ 	{ Opt_compr,	"none",		UBIFS_COMPR_NONE },
+ 	{ Opt_compr,	"lzo",		UBIFS_COMPR_LZO },
+ 	{ Opt_compr,	"zlib",		UBIFS_COMPR_ZLIB },
++	{ Opt_compr,	"zstd",		UBIFS_COMPR_ZSTD },
+ 	{ Opt_assert,	"report",	ASSACT_REPORT },
+ 	{ Opt_assert,	"read-only",	ASSACT_RO },
+ 	{ Opt_assert,	"panic",	ASSACT_PANIC },
+ 	{}
+ };
  
- 	pr_notice("UBIFS: parse %s\n", option);
- 	if (!strcmp(option, "sync"))
- 		return SB_SYNCHRONOUS;
- 	return 0;
- }
+ static const struct fs_parameter_description ubifs_fs_parameters = {
+ 	.name		= "ubifs",
+ 	.specs		= ubifs_param_specs,
+ 	.enums		= ubifs_param_enums,
+ };
  
  /**
-  * ubifs_parse_options - parse mount parameters.
+  * ubifs_parse_param - parse a parameter.
   * @c: UBIFS file-system description object
   * @options: parameters to parse
   * @is_remount: non-zero if this is FS re-mount

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: linux-next: manual merge of the vfs tree with the ubifs tree
  2019-09-16 13:40 Mark Brown
@ 2019-09-16 16:37 ` Richard Weinberger
  0 siblings, 0 replies; 4+ messages in thread
From: Richard Weinberger @ 2019-09-16 16:37 UTC (permalink / raw)
  To: Mark Brown
  Cc: David Howells, Richard Weinberger, Artem Bityutskiy,
	Adrian Hunter, Al Viro, Wenwen Wang, Linux Next Mailing List,
	linux-mtd, Linux Kernel Mailing List

On Mon, Sep 16, 2019 at 3:40 PM Mark Brown <broonie@kernel.org> wrote:
>
> Hi all,
>
> Today's linux-next merge of the vfs tree got a conflict in:
>
>   fs/ubifs/super.c
>
> between commit:
>
>   9163e0184bd7d5f ("ubifs: Fix memory leak bug in alloc_ubifs_info() error path")
>
> from the ubifs tree and commit:
>
>   50d7aad57710e2b ("vfs: Convert ubifs to use the new mount API")
>
> from the vfs tree.
>
> I fixed it up dropping the ubifs change 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.

Thanks a lot for letting me know!

-- 
Thanks,
//richard

^ permalink raw reply	[flat|nested] 4+ messages in thread

* linux-next: manual merge of the vfs tree with the ubifs tree
@ 2019-09-16 13:40 Mark Brown
  2019-09-16 16:37 ` Richard Weinberger
  0 siblings, 1 reply; 4+ messages in thread
From: Mark Brown @ 2019-09-16 13:40 UTC (permalink / raw)
  To: David Howells, Richard Weinberger, Artem Bityutskiy,
	Adrian Hunter, Al Viro, Wenwen Wang
  Cc: linux-mtd, Linux Next Mailing List, Linux Kernel Mailing List

[-- Attachment #1: Type: text/plain, Size: 843 bytes --]

Hi all,

Today's linux-next merge of the vfs tree got a conflict in:

  fs/ubifs/super.c

between commit:

  9163e0184bd7d5f ("ubifs: Fix memory leak bug in alloc_ubifs_info() error path")

from the ubifs tree and commit:

  50d7aad57710e2b ("vfs: Convert ubifs to use the new mount API")

from the vfs tree.

I fixed it up dropping the ubifs change 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.

diff --cc fs/ubifs/super.c
index 7d4547e5202de,a5fa725e7cf16..0000000000000
--- a/fs/ubifs/super.c
+++ b/fs/ubifs/super.c

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

^ permalink raw reply	[flat|nested] 4+ messages in thread

* linux-next: manual merge of the vfs tree with the ubifs tree
@ 2016-10-10  0:20 Stephen Rothwell
  0 siblings, 0 replies; 4+ messages in thread
From: Stephen Rothwell @ 2016-10-10  0:20 UTC (permalink / raw)
  To: Al Viro, Artem Bityutskiy
  Cc: linux-next, linux-kernel, Richard Weinberger, Miklos Szeredi

Hi Al,

Today's linux-next merge of the vfs tree got a conflict in:

  fs/ubifs/dir.c

between commits:

  9e0a1fff8db5 ("ubifs: Implement RENAME_WHITEOUT")
  9ec64962afb1 ("ubifs: Implement RENAME_EXCHANGE")

from the ubifs tree and commit:

  f03b8ad8d386 ("fs: support RENAME_NOREPLACE for local filesystems")
  2773bf00aeb9 ("fs: rename "rename2" i_op to "rename"")

from the vfs tree.

I fixed it up (I think - 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/ubifs/dir.c
index ccd9128f8faf,64902702b17d..000000000000
--- a/fs/ubifs/dir.c
+++ b/fs/ubifs/dir.c
@@@ -1384,13 -1183,10 +1387,10 @@@ const struct inode_operations ubifs_dir
  	.mkdir       = ubifs_mkdir,
  	.rmdir       = ubifs_rmdir,
  	.mknod       = ubifs_mknod,
- 	.rename2     = ubifs_rename2,
 -	.rename     = ubifs_rename,
++	.rename     = ubifs_rename2,
  	.setattr     = ubifs_setattr,
  	.getattr     = ubifs_getattr,
- 	.setxattr    = generic_setxattr,
- 	.getxattr    = generic_getxattr,
  	.listxattr   = ubifs_listxattr,
- 	.removexattr = generic_removexattr,
  #ifdef CONFIG_UBIFS_ATIME_SUPPORT
  	.update_time = ubifs_update_time,
  #endif

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2019-09-16 16:37 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-07-09  1:38 linux-next: manual merge of the vfs tree with the ubifs tree Stephen Rothwell
  -- strict thread matches above, loose matches on Subject: below --
2019-09-16 13:40 Mark Brown
2019-09-16 16:37 ` Richard Weinberger
2016-10-10  0:20 Stephen Rothwell

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).