From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [PATCH 1/5] syscalls/fanotify03: defined additional tcase members for added control
Date: Thu, 21 Feb 2019 17:42:35 +0100 [thread overview]
Message-ID: <20190221164234.GD17813@rei.lan> (raw)
In-Reply-To: <20190122223526.GA32694@lithium.mbobrowski.org>
Hi!
I've finally started to look into this patchset (sorry for the long delay), the
changes to fanotify03 looks good to me and I wanted to push them, but I'm
getting rejects:
Checking patch testcases/kernel/syscalls/fanotify/fanotify03.c...
error: while searching for:
static pid_t child_pid;
static unsigned long long event_set[EVENT_MAX];
static unsigned int event_resp[EVENT_MAX];
static char event_buf[EVENT_BUF_LEN];
static int support_perm_events;
static struct tcase {
const char *tname;
struct fanotify_mark_type mark;
} tcases[] = {
{
"inode mark permission events",
INIT_FANOTIFY_MARK_TYPE(INODE),
},
{
"mount mark permission events",
INIT_FANOTIFY_MARK_TYPE(MOUNT),
},
{
"filesystem mark permission events",
INIT_FANOTIFY_MARK_TYPE(FILESYSTEM),
},
};
static void generate_events(void)
error: patch failed: testcases/kernel/syscalls/fanotify/fanotify03.c:42
Hunk #3 succeeded at 147 (offset -21 lines).
error: while searching for:
}
} else {
/*
* To distigouish between perm event not supported and
* filesystem mark not supported.
*/
support_perm_events = 1;
Is this based on some yet to be merged patchset?
--
Cyril Hrubis
chrubis@suse.cz
next prev parent reply other threads:[~2019-02-21 16:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-22 22:35 [LTP] [PATCH 1/5] syscalls/fanotify03: defined additional tcase members for added control Matthew Bobrowski
2019-02-21 16:42 ` Cyril Hrubis [this message]
2019-02-22 7:22 ` Amir Goldstein
2019-02-26 13:31 ` Cyril Hrubis
2019-02-26 13:45 ` Amir Goldstein
2019-02-26 15:16 ` Cyril Hrubis
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=20190221164234.GD17813@rei.lan \
--to=chrubis@suse.cz \
--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