From: Jan Stancek <jstancek@redhat.com>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/1] fanotify: Fix for musl
Date: Sat, 16 Nov 2019 12:22:57 -0500 (EST) [thread overview]
Message-ID: <977310824.12699736.1573924977430.JavaMail.zimbra@redhat.com> (raw)
In-Reply-To: <20191116002003.13013-1-petr.vorel@gmail.com>
----- Original Message -----
> FSID_VAL_MEMBER() wrapper was meant to be only for struct
> fanotify_event_info_fid, it was used also for struct event_t
> (which has also __kernel_fsid_t fsid, but shouldn't be redefined).
>
> This caused error on recent musl v1.1.23 (with f67b3c17),
> which has struct fanotify_event_info_fid.
>
> Fixes: 0498fc0a8 ("fanotify: Detect val vs. __val
> fanotify_event_info_fid.fsid member")
>
> Signed-off-by: Petr Vorel <petr.vorel@gmail.com>
If it's needed for __kernel_fsid_t we'll need to come up with better names.
This basically reverts part of previous patch, which looks ok to me.
Acked-by: Jan Stancek <jstancek@redhat.com>
next prev parent reply other threads:[~2019-11-16 17:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 0:20 [LTP] [PATCH 1/1] fanotify: Fix for musl Petr Vorel
2019-11-16 17:22 ` Jan Stancek [this message]
2019-11-17 10:04 ` Petr Vorel
2019-11-18 20:33 ` Petr Vorel
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=977310824.12699736.1573924977430.JavaMail.zimbra@redhat.com \
--to=jstancek@redhat.com \
--cc=ltp@lists.linux.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox