public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Matthew Bobrowski <mbobrowski@mbobrowski.org>
To: ltp@lists.linux.it
Subject: [LTP] [RFC 0/3] syscalls/fanotify03: add support and tests for new FAN_OPEN_EXEC_PERM flag
Date: Wed, 24 Oct 2018 14:26:56 +1100	[thread overview]
Message-ID: <cover.1540348505.git.mbobrowski@mbobrowski.org> (raw)

This patch series contains the modifications that I'm proposing in order        
to support the testing of the new permission flag FAN_OPEN_EXEC_PERM            
that is to be made available within fanotify.                                   
                                                                                 
The overall idea behind the changes are to allow more control over each         
individual test case based upon how it has been configured. At the same
time, it increases the overall test coverage by performing more operations
on file system objects that have been marked accordingly.
                                                                                
All modifications within this patch series are based on Amir's
'fanotify_sb' branch, which can be found below.                  
                                                                                 
https://github.com/amir73il/ltp/tree/fanotify_sb
                                                                                 
Please note, this is a RFC for testing functionality that is not yet
merged upstream.

---

Matthew Bobrowski (3):
  syscalls/fanotify03: defined additional tcase members to support more
    tcase control
  syscalls/fanotify03: included execve() to generate_events() to
    increase test coverage
  syscalls/fanotify03: add FAN_OPEN_EXEC_PERM tcase support

 testcases/kernel/syscalls/fanotify/.gitignore |   1 +
 testcases/kernel/syscalls/fanotify/fanotify.h |  14 ++
 .../kernel/syscalls/fanotify/fanotify03.c     | 194 ++++++++++++------
 .../kernel/syscalls/fanotify/fanotify_child.c |  14 ++
 4 files changed, 157 insertions(+), 66 deletions(-)
 create mode 100644 testcases/kernel/syscalls/fanotify/fanotify_child.c

-- 
2.17.2


-- 
Matthew Bobrowski <mbobrowski@mbobrowski.org>

             reply	other threads:[~2018-10-24  3:26 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-24  3:26 Matthew Bobrowski [this message]
2018-10-24  3:27 ` [LTP] [RFC 1/3] syscalls/fanotify03: defined additional tcase members to support more tcase control Matthew Bobrowski
2018-10-24  5:23   ` Amir Goldstein
2018-10-25  6:19     ` Matthew Bobrowski
2018-10-24  3:27 ` [LTP] [RFC 2/3] syscalls/fanotify03: included execve() to generate_events() to increase test coverage Matthew Bobrowski
2018-10-24  5:31   ` Amir Goldstein
2018-10-25  6:39     ` Matthew Bobrowski
2018-10-25  6:46       ` Amir Goldstein
2018-10-24  3:28 ` [LTP] [RFC 3/3] syscalls/fanotify03: add FAN_OPEN_EXEC_PERM tcase support Matthew Bobrowski
2018-10-24  5:56   ` Amir Goldstein
2018-10-25  6:39     ` Matthew Bobrowski

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=cover.1540348505.git.mbobrowski@mbobrowski.org \
    --to=mbobrowski@mbobrowski.org \
    --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