linux-kernel - RE: linux-next: build failure after merge of the block 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: <00b801d4250a$69e2a9f0$3da7fdd0$@opengridcomputing.com>
Date:   Thu, 26 Jul 2018 12:59:35 -0500
From:   "Steve Wise" <swise@...ngridcomputing.com>
To:     "'Christoph Hellwig'" <hch@....de>,
        "'Jens Axboe'" <axboe@...nel.dk>
Cc:     "'Stephen Rothwell'" <sfr@...b.auug.org.au>,
        "'Doug Ledford'" <dledford@...hat.com>,
        "'Jason Gunthorpe'" <jgg@...lanox.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 block tree



> -----Original Message-----
> From: Christoph Hellwig <hch@....de>
> Sent: Thursday, July 26, 2018 12:57 PM
> To: Jens Axboe <axboe@...nel.dk>
> Cc: Christoph Hellwig <hch@....de>; Stephen Rothwell
> <sfr@...b.auug.org.au>; Doug Ledford <dledford@...hat.com>; Jason
> Gunthorpe <jgg@...lanox.com>; Linux-Next Mailing List <linux-
> next@...r.kernel.org>; Linux Kernel Mailing List <linux-
> kernel@...r.kernel.org>; Steve Wise <swise@...ngridcomputing.com>
> Subject: Re: linux-next: build failure after merge of the block tree
> 
> On Thu, Jul 26, 2018 at 10:48:21AM -0700, Jens Axboe wrote:
> > >>  	inline_page_count = num_pages(port->inline_data_size);
> > >>  	inline_sge_count = max(cm_id->device->attrs.max_sge_rd,
> > >> -				cm_id->device->attrs.max_sge) - 1;
> > >> +				cm_id->device->attrs.max_send_sge) -
1;
> > >
> > > This should be max_recv_sge.
> >
> > Why do we even have this conflicts to begin with?
> 
> Because the nvme code added a new user of max_sges while the RDMA tree
> split it into two separate fields.  We discussed this a while ago when
> the issue came up.

See: https://www.spinics.net/lists/linux-rdma/msg66208.html 

Steve.