From: William Roberts <WRoberts@tresys.com>
To: William Roberts <bill.c.roberts@gmail.com>,
"linux-audit@redhat.com" <linux-audit@redhat.com>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"rgb@redhat.com" <rgb@redhat.com>,
"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>
Cc: "sds@tycho.nsa.gov" <sds@tycho.nsa.gov>
Subject: RE: [PATCH] - auditing cmdline
Date: Fri, 6 Dec 2013 15:34:32 +0000 [thread overview]
Message-ID: <A8856C6323EFE0459533E910625AB930347FDF@Exchange10.columbia.tresys.com> (raw)
In-Reply-To: <1386018639-18916-1-git-send-email-wroberts@tresys.com>
I sent out 3 patches on 12/2/2013. I didn't get any response. I thought I added the right people based on get_maintainers script.
Can anyone comment on these or point me in the right direction?
RGB, Can you at least ACK the audit subsystem patch " audit: Audit proc cmdline value"?
Thank you,
Bill
-----Original Message-----
From: owner-linux-mm@kvack.org [mailto:owner-linux-mm@kvack.org] On Behalf Of William Roberts
Sent: Monday, December 02, 2013 1:11 PM
To: linux-audit@redhat.com; linux-mm@kvack.org; linux-kernel@vger.kernel.org; rgb@redhat.com; viro@zeniv.linux.org.uk
Cc: sds@tycho.nsa.gov
Subject: [PATCH] - auditing cmdline
This patch series relates to work started on the audit mailing list.
It eventually involved touching other modules, so I am trying to pull in those owners as well. In a nutshell I add new utility functions for accessing a processes cmdline value as displayed in proc/<self>/cmdline, and then refactor procfs to use the utility functions, and then add the ability to the audit subsystem to record this value.
Thanks for any feedback and help.
[PATCH 1/3] mm: Create utility functions for accessing a tasks
[PATCH 2/3] proc: Update get proc_pid_cmdline() to use mm.h helpers
[PATCH 3/3] audit: Audit proc cmdline value
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2013-12-06 15:35 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-02 21:10 William Roberts
2013-12-02 21:10 ` [PATCH 1/3] mm: Create utility functions for accessing a tasks commandline value William Roberts
2013-12-13 14:12 ` Stephen Smalley
2013-12-13 14:51 ` William Roberts
2013-12-13 15:04 ` Stephen Smalley
2013-12-13 15:26 ` William Roberts
2013-12-13 15:27 ` William Roberts
2013-12-02 21:10 ` [PATCH 2/3] proc: Update get proc_pid_cmdline() to use mm.h helpers William Roberts
2013-12-13 14:23 ` Stephen Smalley
2013-12-13 14:57 ` William Roberts
2013-12-02 21:10 ` [PATCH 3/3] audit: Audit proc cmdline value William Roberts
2013-12-09 15:33 ` Richard Guy Briggs
2013-12-06 15:34 ` William Roberts [this message]
2013-12-06 15:39 ` [PATCH] - auditing cmdline William Roberts
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=A8856C6323EFE0459533E910625AB930347FDF@Exchange10.columbia.tresys.com \
--to=wroberts@tresys.com \
--cc=bill.c.roberts@gmail.com \
--cc=linux-audit@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=rgb@redhat.com \
--cc=sds@tycho.nsa.gov \
--cc=viro@zeniv.linux.org.uk \
/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