From: Nicolas Iooss <nicolas.iooss@m4x.org>
To: Vit Mojzis <vmojzis@redhat.com>
Cc: SElinux list <selinux@vger.kernel.org>
Subject: Re: [PATCH] python/semaange: fix moduleRecords.customized()
Date: Sat, 28 Sep 2019 12:10:36 +0200 [thread overview]
Message-ID: <CAJfZ7=nBDUZYO95PN4p5FaXh_KAa3SeHu6yq4CteFGgyPkjEUw@mail.gmail.com> (raw)
In-Reply-To: <20190927144243.3479-1-vmojzis@redhat.com>
On Fri, Sep 27, 2019 at 4:42 PM Vit Mojzis <vmojzis@redhat.com> wrote:
>
> Return value of "customized" has to be iterable.
>
> Fixes:
> "semanage export" with no modules in the system (eg. monolithic policy)
> crashes:
>
> Traceback (most recent call last):
> File "/usr/sbin/semanage", line 970, in <module>
> do_parser()
> File "/usr/sbin/semanage", line 949, in do_parser
> args.func(args)
> File "/usr/sbin/semanage", line 771, in handleExport
> for c in OBJECT.customized():
> TypeError: 'NoneType' object is not iterable
>
> Signed-off-by: Vit Mojzis <vmojzis@redhat.com>
This looks good to me, but there is a misspelling in the subject of
the patch: semaange -> semanage.
Acked-by: Nicolas Iooss <nicolas.iooss@m4x.org>
Thanks!
Nicolas
> ---
> python/semanage/seobject.py | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/python/semanage/seobject.py b/python/semanage/seobject.py
> index 5e9e3eb5..f4c29854 100644
> --- a/python/semanage/seobject.py
> +++ b/python/semanage/seobject.py
> @@ -380,7 +380,7 @@ class moduleRecords(semanageRecords):
> def customized(self):
> all = self.get_all()
> if len(all) == 0:
> - return
> + return []
> return ["-d %s" % x[0] for x in [t for t in all if t[1] == 0]]
>
> def list(self, heading=1, locallist=0):
> --
> 2.21.0
>
next prev parent reply other threads:[~2019-09-28 10:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-27 14:42 [PATCH] python/semaange: fix moduleRecords.customized() Vit Mojzis
2019-09-28 10:10 ` Nicolas Iooss [this message]
2019-09-30 7:49 ` [PATCH] python/semanage: " Vit Mojzis
2019-10-01 18:28 ` Stephen Smalley
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='CAJfZ7=nBDUZYO95PN4p5FaXh_KAa3SeHu6yq4CteFGgyPkjEUw@mail.gmail.com' \
--to=nicolas.iooss@m4x.org \
--cc=selinux@vger.kernel.org \
--cc=vmojzis@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).