linux-audit.redhat.com archive mirror
 help / color / mirror / Atom feed
From: Martin Kletzander <mkletzan@redhat.com>
To: linux-audit@redhat.com
Subject: What fields should be used for reporting shared memory?
Date: Tue, 14 Mar 2017 12:42:27 +0100	[thread overview]
Message-ID: <20170314114227.GB6248@wheatley> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1091 bytes --]

Hi,

I am going through the fields in the dictionary and I can't find any
name to use for the following scenario.

We (libvirt) are running virtual machines and there's a thing nowadays,
that people like to use, called ivshmem (Inter-VM SHared MEMory).  From
host's point of view this is just a shared memory region accessed by
multiple VMs (and possibly to host as well).  The machine maps the
shared memory given a name (e.g. name "asdf" results in /dev/shm/asdf to
be mapped) *or* it can communicate with a server over UNIX socket and
that server handles interrupts and also tells the client which shared
memory region to map.  Talking about information we have; in server-less
setup it's the shared memory region that is shared, in the server
scenario it is the socket.  That's information we can output.

So my question is, when starting a domain or hot-(un)plugging, what
naming should we use for this kind of device and what are the things
that we should describe about it?  Basically, how would you like the
message to look?

Thanks in advance for any info.

Have a nice day,
Martin

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



             reply	other threads:[~2017-03-14 11:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-14 11:42 Martin Kletzander [this message]
2017-03-17  1:04 ` What fields should be used for reporting shared memory? Steve Grubb
2017-03-20 11:36   ` Martin Kletzander
2017-03-20 22:21     ` Steve Grubb
2017-05-10 12:37       ` Martin Kletzander

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=20170314114227.GB6248@wheatley \
    --to=mkletzan@redhat.com \
    --cc=linux-audit@redhat.com \
    /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;
as well as URLs for NNTP newsgroup(s).