Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67;
Date:   Tue, 17 Jul 2018 14:58:29 +0200
From:   Christoph Hellwig <hch@lst.de>
To:     Laura Abbott <labbott@redhat.com>
Cc:     Christoph Hellwig <hch@lst.de>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        "Darrick J. Wong" <darrick.wong@oracle.com>,
        Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
        linux-aio@kvack.org
Subject: Re: compliation error with aio_abi.h
Message-ID: <20180717125829.GA12368@lst.de>
References: <05018ab0-37ce-37f3-e032-7daf0338a75d@redhat.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <05018ab0-37ce-37f3-e032-7daf0338a75d@redhat.com>
User-Agent: Mutt/1.5.17 (2007-11-01)
Sender: linux-kernel-owner@vger.kernel.org
Precedence: bulk

On Mon, Jul 16, 2018 at 09:40:19AM -0700, Laura Abbott wrote:
> This looks like the structure that was introduced with 7a074e96dee6
> ("aio: implement io_pgetevents") . is #include <linux/signal.h>
> the correct header? This breaks compilation of nginx
> https://bugzilla.redhat.com/show_bug.cgi?id=1597674

As far as the kernel is concerned it is the right header, but the
glibc side of signals is a mess.  I've thus submitted the fix below
to avoid exposing the signal bits at all:

https://marc.info/?l=linux-fsdevel&m=153131732618217&w=2