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

Message-ID: <20170609115905.GA11110@redhat.com>
Date:   Fri, 9 Jun 2017 07:59:05 -0400
From:   Mike Snitzer <snitzer@...hat.com>
To:     Damien Le Moal <damien.lemoal@....com>
Cc:     Stephen Rothwell <sfr@...b.auug.org.au>,
        Alasdair G Kergon <agk@...hat.com>,
        Linux-Next Mailing List <linux-next@...r.kernel.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: linux-next: build failure after merge of the device-mapper tree

On Fri, Jun 09 2017 at 12:28am -0400,
Damien Le Moal <damien.lemoal@....com> wrote:

> Stephen,
> 
> On 6/9/17 12:12, Stephen Rothwell wrote:
> > Hi all,
> > 
> > After merging the device-mapper tree, today's linux-next build (x86_64
> > allmodconfig) failed like this:
> > 
> > drivers/md/dm-zoned-target.c:947:2: error: unknown field 'suspend' specified in initializer
> >   .suspend  = dmz_suspend,
> >   ^
> > drivers/md/dm-zoned-target.c:947:14: error: initialization from incompatible pointer type [-Werror=incompatible-pointer-types]
> >   .suspend  = dmz_suspend,
> >               ^
> > 
> > Caused by commit
> > 
> >   02da2e15e81f ("dm zoned: drive-managed zoned block device target")
> > 
> > I have used the device-mapper tree from next-20170608 for today.
> 
> My apologies for that. My mistake.
> I just posted a patch to dm-devel to fix this.
> Everything should come in order after Mike's review.

I'm to blame for the above issue.  I've now fixed it up.