linux-kernel - linux-next: manual merge of the block tree with the v9fs tree

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [day] [month] [year] [list]

Message-Id: <20100428132413.28bc9ff2.sfr@canb.auug.org.au>
Date:	Wed, 28 Apr 2010 13:24:13 +1000
From:	Stephen Rothwell <sfr@...b.auug.org.au>
To:	Jens Axboe <jens.axboe@...cle.com>
Cc:	linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
	Sripathi Kodi <sripathik@...ibm.com>,
	Eric Van Hensbergen <ericvh@...il.com>
Subject: linux-next: manual merge of the block tree with the v9fs tree

Hi Jens,

Today's linux-next merge of the block tree got a conflict in
fs/9p/vfs_super.c between commit 0b2d973241f9bdbc8ed62caec42543e00ae6bd1e
("9p: VFS switches for 9p2000.L: VFS switches") from the v9fs tree and
commit 0ed07ddb56d1348e5ce33f3b8de20d730351983a ("9p: add bdi backing to
mount session") from the block tree.

Just context changes.  I fixed it up (see below) and can carry the
fix as necessary.
-- 
Cheers,
Stephen Rothwell                    sfr@...b.auug.org.au

diff --cc fs/9p/vfs_super.c
index 7c94cb0,806da5d..0000000
--- a/fs/9p/vfs_super.c
+++ b/fs/9p/vfs_super.c
@@@ -77,10 -76,8 +77,11 @@@ v9fs_fill_super(struct super_block *sb
  	sb->s_blocksize_bits = fls(v9ses->maxdata - 1);
  	sb->s_blocksize = 1 << sb->s_blocksize_bits;
  	sb->s_magic = V9FS_MAGIC;
 -	sb->s_op = &v9fs_super_ops;
 +	if (v9fs_proto_dotl(v9ses))
 +		sb->s_op = &v9fs_super_ops_dotl;
 +	else
 +		sb->s_op = &v9fs_super_ops;
+ 	sb->s_bdi = &v9ses->bdi;
  
  	sb->s_flags = flags | MS_ACTIVE | MS_SYNCHRONOUS | MS_DIRSYNC |
  	    MS_NOATIME;
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/