utopic has seen the end of its life and is no longer receiving any
updates. Marking the utopic task for this ticket as "Won't Fix".
** Changed in: linux (Ubuntu Utopic)
Status: Confirmed => Won't Fix
--
You received this bug notification because you are a member of Kernel
Packages, which
This bug was fixed in the package linux - 4.3.0-1.10
---
linux (4.3.0-1.10) xenial; urgency=low
[ Andy Whitcroft ]
* [Config] make IBMVETH consistent on powerpc/ppc64el
- LP: #1521712
* [Config] follow ibmvscsi name change
- LP: #1521712
* [Config] move ibm disk and
This bug will be used for tracking the bad unix_addr_fs macro issue that
has already been commited.
The other part of the reported bug, deleted entry, denial for socket
being revalidated on shutdown will be tracked under bug 1446906.
--
You received this bug notification because you are a
So confirming that this bug is two separate issues
There is the committed fix for a bug around the bad unix_addr_fs macro
that was causing a failure. The remaining bug is around a socket that is
being shutdown and revalidated, it can manifest it self as a race so
there are cases where it appears
Ah those "upstream" kernels weren't pure... Just tested manually compiled
kernel master branch and tag 4.2, no issues. Copied over a packaged one:
problem reappears.
It's not a container problem though. Running this on a host has the same effect:
# aa-exec -p $pick_your_favorite_profile -- socat
We encountered the same problem and noticed it only happened on 64 bit
containers, while 32 bit containers seemed to work. We also tested
upstream kernels 4.1 and 4.2.3, same result.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux
smtp and qmgr suffer similar denials:
kernel: [33252.627322] audit: type=1400 audit(1434961302.532:240):
apparmor=DENIED operation=file_perm profile=lxc-container-default
name=private/trace pid=11752 comm=qmgr requested_mask=r
denied_mask=r fsuid=100104 ouid=0
kernel: [33252.626415] audit:
An again:
zoolook@venkman:~$ sudo lxc-attach -n dana
root@dana:~# mailq
postqueue: warning: close: Permission denied
root@dana:~# uname -a
Linux dana 3.19.0-21-generic #21-Ubuntu SMP Sun Jun 14 18:31:11 UTC 2015 x86_64
x86_64 x86_64 GNU/Linux
root@dana:~# dmesg | tail -n1
[ 3637.172284]
I waited two releases after the fix commited announce. Still not
fixed. Where's the fix? What version of what package?
This is current vivid.
zoolook@venkman:~$ sudo lxc-attach -n dana
root@dana:~# mailq
postqueue: warning: close: Permission denied
root@dana:~# uname -a
Linux dana
I'm seeing the same thing with postscreen on the current kernel:
audit: type=1400 audit(1433863724.358:39): apparmor=DENIED
operation=file_perm profile=lxc-container-default
name=private/dnsblog pid=21627 comm=postscreen requested_mask=r
denied_mask=r fsuid=100104 ouid=0
--
You received this
Hi,
Where is the Fix Committed, is there a package we could try or build ?
Regards,
Lee
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1390223
Title:
Apparmor related regression on
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1390223
Title:
Apparmor related regression on access to unix
** Changed in: linux (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1390223
Title:
Apparmor related regression on access to unix
This bug may have regressed again in the 3.19 kernel. Does this issue
go away if you boot into the 3.18.0-8.9 kernel?
** Changed in: linux (Ubuntu Vivid)
Status: Fix Released = Confirmed
--
You received this bug notification because you are a member of Kernel
Packages, which is
$ uname -a
Linux venkman 3.19.0-11-generic #11-Ubuntu SMP Tue Mar 31 22:17:56 UTC 2015
x86_64 x86_64 x86_64 GNU/Linux
Up-to-date Vivid.
Same problem.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
Just to add, getting this error in the dmesg:
[97661.056052] audit: type=1400 audit(1426952275.541:2120):
apparmor=DENIED operation=file_perm profile=lxc-container-default
name=public/showq pid=25035 comm=postqueue requested_mask=r
denied_mask=r fsuid=0 ouid=0
--
You received this bug
I have the same problem on 15.04 using Linux smtp01 3.19.0-9-generic.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1390223
Title:
Apparmor related regression on access to unix sockets
** CVE removed: http://www.cve.mitre.org/cgi-
bin/cvename.cgi?name=2014-8134
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1390223
Title:
Apparmor related regression on access to unix
I am have the same problem with puppet in a container on 14.04 using hwe kernel
version 3.16.0-31.
Package install for kernel is linux-image-generic-lts-utopic
Switch back to kernel 3.13.0-46 fixed the problem for me.
--
You received this bug notification because you are a member of Kernel
I went ahead and upgraded to vivid. My kerberos/ldap problems are solved
but I still get:
$ mailq
postqueue: warning: close: Permission denied
guest is trusty:
ii postfix 2.11.0-1ubuntu1
amd64High-performance mail transport agent
host is vivid:
ii lxc
I have some containers that authenticate thru kerberos/ldap and I
couldn't ssh in the containers while using utopic's kernels.
My fix was to temporaly go back to trusty's kernel.
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in
I have same problem on Trustu with Utopic kernel linux-generic-lts-
utopic 3.16.0.30.23 and nginx + uwsgi fastrouter socket. Sometimes
access denied and partial html file is send.
in /var/log/nginx/error.log
2015/02/11 08:39:27 [alert] 474#0: *148 readv() failed (13: Permission denied)
while
This bug was fixed in the package linux - 3.18.0-8.9
---
linux (3.18.0-8.9) vivid; urgency=low
[ Leann Ogasawara ]
* Release Tracking Bug
- LP: #1407692
* rebase to v3.18.1
* ubuntu: AUFS -- Resolve build failure union has no member named
'd_child'
[ Upstream
** Changed in: linux (Ubuntu Vivid)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1390223
Title:
Apparmor related regression on access to unix
** Also affects: linux (Ubuntu Vivid)
Importance: Medium
Assignee: John Johansen (jjohansen)
Status: Confirmed
** Also affects: linux (Ubuntu Utopic)
Importance: Undecided
Status: New
** Changed in: linux (Ubuntu Utopic)
Status: New = Confirmed
** Changed in:
I am seeing same kind of behaviour after upgrade to utopic, mailq fails
with permission denied.
The odd thing is it doesn't happen every time. Sometimes when running
mailq in a loop it might work occasionally. Sometimes not. Sometimes
it works for period of time just fine and then starts
** Changed in: linux (Ubuntu)
Importance: Undecided = Medium
** Changed in: linux (Ubuntu)
Status: Incomplete = Confirmed
** Tags added: kernel-da-key
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
** Changed in: linux (Ubuntu)
Assignee: (unassigned) = John Johansen (jjohansen)
--
You received this bug notification because you are a member of Kernel
Packages, which is subscribed to linux in Ubuntu.
https://bugs.launchpad.net/bugs/1390223
Title:
Apparmor related regression on access
28 matches
Mail list logo
