On a third machine:
...
  Updating   : selinux-policy-devel-3.13.1-105.9.fc21.noarch                                                                                                                      5/64 
/usr/share/selinux/devel/include/system/sysnetwork.if: Syntax error on line 98928 ' [type=SQUOTE]
  Updating   : selinux-policy-targeted-3.13.1-105.9.fc21.noarch                                                                                                                   6/64
...

*** Bug 1207944 has been marked as a duplicate of this bug. ***

Interestingly enough I see the same on a machine with selinux-policy-devel-3.13.1-105.9.fc21 installed but the line in question is consistently 261773.

It is enough to run '/usr/bin/sepolgen-ifgen' to generate this message.

The line number always varies for me [1].

More cases:

4th machine: /usr/share/selinux/devel/include/system/sysnetwork.if: Syntax error on line 83859 ' [type=SQUOTE]

5th machine: /usr/share/selinux/devel/include/system/sysnetwork.if: Syntax error on line 8440 ' [type=SQUOTE]

6th machine:
/usr/share/selinux/devel/include/system/sysnetwork.if: Syntax error on line 83206 ' [type=SQUOTE]

My wild guess would be a leak/overflow somewhere in SELinux.


[1] Seems to me as if I pasted an identical block twice in my initial report, instead of pasting 2 different ones. 
The numbers were different in all cases!

On a clean and up-to-date F21 host, the yum update gives:
. . .
  Upgrading   : selinux-policy-devel-3.13.1-105.9.fc21.noarch             27/78 
/usr/share/selinux/devel/include/system/sysnetwork.if: Syntax error on line 8946 ' [type=SQUOTE]
. . .

This is the last unquote in the file.  Searching backwards for malformed rules, the sysnet_filetrans_named_content rule at line 1070 (actual fault at line 1091) looks an awful lot like the real problem with mismatched quoting in the new ruleset.

(In reply to John Mellor from comment #6)
> This is the last unquote in the file.  Searching backwards for malformed
> rules, the sysnet_filetrans_named_content rule at line 1070 (actual fault at
> line 1091) looks an awful lot like the real problem with mismatched quoting
> in the new ruleset.

* I am inclined to agree. Seems to me as if the section at line 1087-1090 is bogus/broken (This section originates from policy-f21-base.patch).

Simply removing line 1090 (AFAIU, a stray ")") at least silences the error, but I don't fully understand what I am doing, here :)

* After having removed line "1090" 2 more presumable bugs face up:
# sepolgen-ifgen -d -v
...
Missing interface definition for files_write_all_pid_sockets
Found circular interface class
...

* Also, AFAIS, the "random line numbers" seem to be a defect inside of the parser, which apparently doesn't handle line-numbers correctly.

You are right, this was due to syntax error. My bad, sorry.

I'm going to make new build ASAP.


commit 53ec367ed646bfc9c2bcb5f2952621a81cc49c9f
Author: Lukas Vrabec <lvrabec>
Date:   Thu Apr 2 11:02:35 2015 +0200

    Fix sysnet_filetrans_named_content interface. BZ(1207942)

selinux-policy-3.13.1-105.11.fc21 has been submitted as an update for Fedora 21.
https://admin.fedoraproject.org/updates/selinux-policy-3.13.1-105.11.fc21

Package selinux-policy-3.13.1-105.11.fc21:
* should fix your issue,
* was pushed to the Fedora 21 testing repository,
* should be available at your local mirror within two days.
Update it with:
# su -c 'yum update --enablerepo=updates-testing selinux-policy-3.13.1-105.11.fc21'
as soon as you are able to.
Please go to the following url:
https://admin.fedoraproject.org/updates/FEDORA-2015-5478/selinux-policy-3.13.1-105.11.fc21
then log in and leave karma (feedback).

Installing : selinux-policy-devel-3.13.1-105.9.fc21.noarch                                                                                                 10/16 
/usr/share/selinux/devel/include/system/sysnetwork.if: Syntax error on line 2360 ' [type=SQUOTE]

Looks like there is one more.

Since this error and the new related one are stopping selinux from operating correctly, I would think that the priority and severity should both be bumped up to urgent.  This is a severe security issue.

Hi Sudhir, 
Could you please try it with new version package?

Hello Lukas,

No problems with selinux-policy-devel-3.13.1-105.11.fc21.

Thanks,
-Sudhir.

Perfect, 
Thank you!

This message is a reminder that Fedora 21 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 21. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '21'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 21 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Fedora 21 changed to end-of-life (EOL) status on 2015-12-01. Fedora 21 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.