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
Date: Tue, 17 Jul 2018 14:58:29 +0200 [thread overview]
Message-ID: <20180717125829.GA12368@lst.de> (raw)
In-Reply-To: <05018ab0-37ce-37f3-e032-7daf0338a75d@redhat.com>
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
prev parent reply other threads:[~2018-07-17 12:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 16:40 compliation error with aio_abi.h Laura Abbott
2018-07-17 12:58 ` Christoph Hellwig [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20180717125829.GA12368@lst.de \
--to=hch@lst.de \
--cc=darrick.wong@oracle.com \
--cc=gregkh@linuxfoundation.org \
--cc=labbott@redhat.com \
--cc=linux-aio@kvack.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.