linux-kernel - Re: linux-next: build failure after merge of the staging 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>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <c43607d8-7dd5-030c-8036-208295c2aef0@huawei.com>
Date:   Mon, 30 Jul 2018 19:23:56 +0800
From:   Gao Xiang <gaoxiang25@...wei.com>
To:     David Howells <dhowells@...hat.com>
CC:     Stephen Rothwell <sfr@...b.auug.org.au>, Greg KH <greg@...ah.com>,
        Al Viro <viro@...IV.linux.org.uk>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Miao Xie <miaoxie@...wei.com>, Chao Yu <yuchao0@...wei.com>
Subject: Re: linux-next: build failure after merge of the staging tree



On 2018/7/30 19:18, David Howells wrote:
> Gao Xiang <gaoxiang25@...wei.com> wrote:
> 
>> struct erofs_mount_private priv = {
>> 	.dev_name = dev_name,
>> 	.options = data
>> };
>> return mount_bdev(fs_type, flags, dev_name, &priv, erofs_fill_super);
>>
>>
>> However, I have no idea if it is safe to do so in the future, so I also
>> change it into a more stardard way.
> 
> Hopefully, in the near future, you won't do it like this at all, but rather
> create an fs_context and then your filesystem would be able to munge that
> directly before calling mount_bdev().
> 

OK, got you. Look forword to the new fs_context feature and thanks for your help :)

Thanks,
Gao Xiang

> David
>