could you try reproducing with the kernel in
http://people.canonical.com/~jj/linux+jj/
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
kernel BUG on snap d
Bug #1581990 looks to be the same kernel trace.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
kernel BUG on snap disconnect from within a snap
Status in
@jdstrand: but it is still not reliable, I tried the above steps in a
fresh VM without success (no crashes, no oops).
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
@jdstrand I was able to reproduce it today with the lines in
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/comments/22.
And Ondra hit the issue today as well.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to a
Annoying-- it happened to 3 people today but still no reliable
reproducer.
** Changed in: apparmor (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.lau
It seems like its not trivial to reproduce still, I tried:
# snap remove ubuntu-device-flash || true
# snap install --beta --devmode ubuntu-device-flash
# snap refresh --edge --devmode ubuntu-device-flash
which upgrades from r3->r5 (note that its the default profile anyway so it
shou
@Michael - can you attach the snap of the version you upgraded from as
well as to? I suspect the reproducer becomes:
$ sudo snap install --devmode /path/to/previous/udf
$ sudo snap install --devmode /path/to/updated/udf
Do we need to do something like this instead? (not sure what a fetch from the
** Changed in: apparmor (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
kernel BUG on snap disconnect from within
For me it happend today as well. It happend when I upgraded a devmode
snap to a new version of a devmode snap (ubuntu-device-flash in
particular). It also happend to ogra with the same snap (but a different
upgrade path). U-d-f is not using any plugs or slots, just the default
policy.
--
You rece
Unfortunately no, I mentioned earlier that I'm no longer able to
reproduce the problem but John said nothing went in that should have
fixed it. I'll leave it up to you guys if you'd like to invalidate it
or keep it open, but for me it is now unreproducible. :(
--
You received this bug notificati
Hi Paul - Any chance that you can help with the additional info
requested by John? Thanks!
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
kernel BUG on sna
Is the snap removed and then reinstalled?
Has this been triggered just by running the snap?
When was the kernel rebooted since the snap was installed? Since the snap was
removed?
...
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscrib
I have been unable to trigger this bug can you please provide more
information?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
kernel BUG on snap disconnec
I'll keep running to see if I can reproduce it again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
kernel BUG on snap disconnect from within a snap
Stat
No, which means its a race of some kind
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
kernel BUG on snap disconnect from within a snap
Status in apparmor
Strange, I rebuilt the snap today, built a new amd64 snappy image, and
ran through all the tests in kvm twice with no crash. Did something go
in that could have fixed it?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmo
Oh, I didn't give all the steps on recreating your snap and running the
tests (not sure how that happened). For posterity:
$ sudo apt-get install snapcraft
$ sudo unsquashfs /var/lib/snapd/snaps/snappy-tests_11.snap # unpack
$ sudo chown -R jamie:jamie ./squashfs-root
$ vi ./squashfs-root/comm
In my first attempt I didn't use --devmode.
However, I can't seem to make the snap work in a xenial amd64 VM.
I tried the original snap with:
$ sudo snap install --devmode ./snappy-tests_0.1_amd64.snap
$ snappy-tests -check.f homeInterfaceSuite
...
... Error reading config: open integration-tests
@Paul, I tried to test this in a snappy VM with:
$ snappy-tests -check.f homeInterfaceSuite
Bad system call
--
FAIL: :46: homeInterfaceSuite.SetUpSuite
/home/plars/work/snappy/snappy-tests/parts/snappy-tests/go/src/github.com/ubu
@Jamie: simply building that snap and installing it, and even
connecting/disconnecting the slots doesn't seem to reproduce the problem
easily. The easiest way I can come up with for reproducing it is to use the
snap that I'm using [attached]. To run into the problem I see, install this
snap, a
Linux localhost.localdomain 4.4.0-21-generic #37-Ubuntu SMP Mon Apr 18
18:33:37 UTC 2016 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/157913
What kernel (full version) did this occur on?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
kernel BUG on snap disconnect from within a snap
Status in ap
I'm told home-consumer is https://github.com/ubuntu-
core/snappy/blob/master/integration-tests/data/snaps/home-consumer/ so
reproducing with a snap would be to checkout that branch, run 'snapcraft
snap .' then installing the resulting snap (eg, 'sudo snap install
/path/to/snap' adding --devmode if
I cannot reproduce with the following:
$ mkdir /tmp/cache
$ tar -zxvf ./profiles.tgz
$ cd profiles
$ while /bin/true ; do sudo apparmor_parser --replace --write-cache -O
no-expr-simplify --cache-loc=/tmp/cache ./* ; done
The above apparmor_parser options are what snapd uses (see
interfaces/appar
It looks like you installed the snap with --devmode. Can you confirm?
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubuntu.
https://bugs.launchpad.net/bugs/1579135
Title:
kernel BUG on snap disconnect from wit
Tail end of syslog:
May 6 16:03:58 localhost kernel: [ 595.676922] audit: type=1400
audit(1462550638.144:10477): apparmor="ALLOWED" operation="recvmsg"
profile="snap.snappy-tests.snappy-tests//null-/usr/bin/sudo" pid=1908
comm="sudo" family="netlink" sock_type="raw" protocol=9
requested_mask=
** Attachment added: "/var/cache/apparmor"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+attachment/4657381/+files/var-cache-apparmor.tgz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ubunt
** Attachment added: "/var/lib/snapd/apparmor/profiles"
https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/1579135/+attachment/4657380/+files/profiles.tgz
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to apparmor in Ub
28 matches
Mail list logo
