48423a0b5d
This function loads the BPF prog with prepared map into kernel and
attaches it into guest cgroup. It can be also used to replace existing
program in the cgroup if we need to resize BPF map to store more rules
for devices. The old program will be closed and removed from kernel.
There are two possible ways how to create BPF program:
- One way is to write simple C-like code which can by compiled into
BPF object file which can be loaded into kernel using elfutils.
- The second way is to define macros which look like assembler
instructions and can be used directly to create BPF program that
can be directly loaded into kernel.
Since the program is not too complex we can use the second option.
If there is no program, all devices are allowed, if there is some
program it is executed and based on the exit status the access is
denied for 0 and allowed for 1.
Our program will follow these rules:
- first it will try to look for the specific key using major and
minor to see if there is any rule for that specific device
- if there is no specific rule it will try to look for any rule that
matches only major of the device
- if there is no match with major it will try the same but with
minor of the device
- as the last attempt it will try to look for rule for all devices
and if there is no match it will return 0 to deny that access
Signed-off-by: Pavel Hrdina <phrdina@redhat.com>
Reviewed-by: Ján Tomko <jtomko@redhat.com>
|
||
|---|---|---|
| .. | ||
| af.mini.po | ||
| am.mini.po | ||
| anp.mini.po | ||
| ar.mini.po | ||
| as.mini.po | ||
| ast.mini.po | ||
| bal.mini.po | ||
| be.mini.po | ||
| bg.mini.po | ||
| bn_IN.mini.po | ||
| bn.mini.po | ||
| bo.mini.po | ||
| br.mini.po | ||
| brx.mini.po | ||
| bs.mini.po | ||
| ca.mini.po | ||
| cs.mini.po | ||
| cy.mini.po | ||
| da.mini.po | ||
| de_CH.mini.po | ||
| de.mini.po | ||
| el.mini.po | ||
| en_GB.mini.po | ||
| eo.mini.po | ||
| es.mini.po | ||
| et.mini.po | ||
| eu.mini.po | ||
| fa.mini.po | ||
| fi.mini.po | ||
| fil.mini.po | ||
| fr.mini.po | ||
| fur.mini.po | ||
| ga.mini.po | ||
| gl.mini.po | ||
| gu.mini.po | ||
| he.mini.po | ||
| hi.mini.po | ||
| hr.mini.po | ||
| hu.mini.po | ||
| ia.mini.po | ||
| id.mini.po | ||
| ilo.mini.po | ||
| is.mini.po | ||
| it.mini.po | ||
| ja.mini.po | ||
| ka.mini.po | ||
| kk.mini.po | ||
| km.mini.po | ||
| kn.mini.po | ||
| ko.mini.po | ||
| kw_GB.mini.po | ||
| kw.mini.po | ||
| kw@kkcor.mini.po | ||
| kw@uccor.mini.po | ||
| ky.mini.po | ||
| lt.mini.po | ||
| lv.mini.po | ||
| mai.mini.po | ||
| Makefile.am | ||
| mk.mini.po | ||
| ml.mini.po | ||
| mn.mini.po | ||
| mr.mini.po | ||
| ms.mini.po | ||
| my.mini.po | ||
| nb.mini.po | ||
| nds.mini.po | ||
| ne.mini.po | ||
| nl.mini.po | ||
| nn.mini.po | ||
| nso.mini.po | ||
| or.mini.po | ||
| pa.mini.po | ||
| pl.mini.po | ||
| POTFILES.in | ||
| pt_BR.mini.po | ||
| pt.mini.po | ||
| README.md | ||
| ro.mini.po | ||
| ru.mini.po | ||
| si.mini.po | ||
| sk.mini.po | ||
| sl.mini.po | ||
| sq.mini.po | ||
| sr.mini.po | ||
| sr@latin.mini.po | ||
| sv.mini.po | ||
| ta.mini.po | ||
| te.mini.po | ||
| tg.mini.po | ||
| th.mini.po | ||
| tr.mini.po | ||
| tw.mini.po | ||
| uk.mini.po | ||
| ur.mini.po | ||
| vi.mini.po | ||
| wba.mini.po | ||
| yo.mini.po | ||
| zanata.xml | ||
| zh_CN.mini.po | ||
| zh_HK.mini.po | ||
| zh_TW.mini.po | ||
| zu.mini.po | ||
Libvirt Message Translation
Libvirt translatable messages are maintained using the GNU Gettext tools and file formats, in combination with the Zanata web service.
python-zanata-client is required in order to use make to pull/push translations from/to Zanata server.
Source repository
The libvirt GIT repository does NOT store the master "libvirt.pot" file, nor does it store full "po" files for translations. The master "libvirt.pot" file can be generated at any time using
make libvirt.pot
The translations are kept in minimized files that are the same file format as normal po files but with all redundant information stripped and messages re-ordered. The key differences between the ".mini.po" files in GIT and the full ".po" files are
- msgids with no current translation are omitted
- msgids are sorted in alphabetical order not source file order
- msgids with a msgstr marked "fuzzy" are discarded
- source file locations are omitted
The full po files can be created at any time using
make update-po
This merges the "libvirt.pot" with the "$LANG.mini.po" for each language, to create the "$LANG.po" files. These are included in the release archives created by "make dist".
When a full po file is updated, changes can be propagated back into the minimized po files using
make update-mini-po
Note, however, that this is generally not something that should be run by developers normally, as it is triggered by 'make pull-po' when refreshing content from Zanata.
Zanata web service
The translation of libvirt messages has been outsourced to the Fedora translation team using the Zanata web service:
https://fedora.zanata.org/project/view/libvirt
As such, changes to translations will generally NOT be accepted as patches directly to libvirt GIT. Any changes made to "$LANG.mini.po" files in libvirt GIT will be overwritten and lost the next time content is imported from Zanata.
The master "libvirt.pot" file is periodically pushed to Zanata to provide the translation team with content changes, using
make push-pot
New translated text is then periodically pulled down from Zanata to update the minimized po files, using
make pull-po
Sometimes the translators make mistakes, most commonly with handling printf format specifiers. The "pull-po" command re-generates the .gmo files to try to identify such mistakes. If a mistake is made, the broken msgstr should be deleted in the local "$LANG.mini.po" file, and the Zanata web interface used to reject the translation so that the broken msgstr isn't pulled down next time.
After pulling down new content the diff should be examined to look for any obvious mistakes that are not caught automatically. There have been bugs in Zanata tools which caused messges to go missing, so pay particular attention to diffs showing deletions where the msgid still exists in libvirt.pot