<mokomull>
I can't get any symbols out of that stack trace.
esmiurium has joined #sandstorm
<dwrensha>
mokomull: what code are you running under spk dev?
<dwrensha>
like, are you able to run a simple "hello world" without hitting the EIO?
<mokomull>
I've got a Rust binary that answers HTTP requests by just dumping the headers in the response - was hoping to poke around at the platform a little bit.
<mokomull>
This is my hello-world equivalent, so no :)
<dwrensha>
:/
<dwrensha>
does `sudo modprobe fuse` do anything for you?
<mokomull>
exits cleanly. Like I said, $ grep -i FUSE /boot/config-$(uname -r)
<mokomull>
I believe so. After that, had to do nothing (except fix the argv[0] for the program) to get it to work as expected.
<dwrensha>
will Xenial's default kernel eventually get updated?
<digitalcircuit>
dwrensha: Xenial will probably follow the same policy as past releases, e.g. https://wiki.ubuntu.com/Kernel/LTSEnablementStack As to the default in the near future, or the 4.4 series, I don't know.
<mokomull>
hm, I didn't try anything out of xenial-proposed. Lemme install the 4.4.0-32 from there and see what happens.
<mokomull>
My wild-ass-guess is that the breakage is a Canonical patch on top of mainline, and if so, it'll get carried to future releases anyway :)
<mokomull>
Same error on -32, so I'm probably going to bisect the Canonical patches when I get back.
<dwrensha>
it'd be awesome if we could pinpoint the problem
xet7__ has joined #sandstorm
xet7 has quit [Read error: Connection reset by peer]
<mokomull>
If that commit is it, then you're probably already getting gibberish for pids over FUSE, but I'll wager nothing's actually conditional on pids.
digitalcircuit has joined #sandstorm
<asheesh>
What does "pids over FUSE" mean?
<asheesh>
Does FUSE have a way to talk about PIDs? Honest question; I'm more of a n00b than dwrensha at this stuff.
<mokomull>
asheesh: looking at the diff, the pid is in the fuse_req struct, and had previously been shoved in there untranslated.
<asheesh>
Ah hah, I see that now, thanks!
<mokomull>
As for the actual consequences of that - I've got no idea.
<asheesh>
Yeah; it's fascinating but probably not that important for us. The "return -EIO;" is more troublesome.
<asheesh>
I guess I should email them.
<asheesh>
Or at least write this up in a Sandstorm bug first.
<asheesh>
Or you can, if you prefer to get credit for it! Also feel free to keep bisecting, but this does look thoroughly relevant.
<asheesh>
I wonder if you can test with this one patch reverted, even.
<asheesh>
Are you doing kernel builds as part of your bisect?
<mokomull>
I will try that after the last step. I kicked off a 'make' before I read through the logs for fs/fuse.
<mokomull>
Yeah, and I'm being lazy and building all the modules that Ubuntu ships with, so it's not exactly what we call "fast". But at least I have a lot of CPU in this box.
<mokomull>
asheesh: more than fake /proc - fakes /sys/fs/cgroup too, IIRC, since cgroup namespaces are new (and require unified hierarchy). I've pointed zarvox at lxcfs before :)
<mokomull>
And this kernel testing exploded XFS on my test VM. I think that's a sign I should stop for the day.
sydney_untangle has quit [Ping timeout: 240 seconds]
Isla_de_Muerte is now known as NwS
mnutt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
<dwrensha>
mokomull: when you said "specialsauce", I didn't realize that Ubuntu's modifications to the kernel are actually labeled "SAUCE" :)
jemc has joined #sandstorm
jemc has quit [Ping timeout: 265 seconds]
jemc has joined #sandstorm
mnutt has joined #sandstorm
jemc has quit [Quit: WeeChat 1.4]
jemc has joined #sandstorm
mnutt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
mnutt has joined #sandstorm
mnutt has quit [Quit: My Mac has gone to sleep. ZZZzzz…]
bony has quit [Ping timeout: 240 seconds]
bony has joined #sandstorm
isd has joined #sandstorm
jemc has quit [Ping timeout: 250 seconds]
dwrensha has quit [Quit: ChatZilla 0.9.92 [Firefox 47.0/20160604131506]]
frigginglorious has joined #sandstorm
<mokomull>
asheesh: reverting that patch [and fixing merge conflicts to keep the user-namespaces support they also added] seems to have done the trick.
frigginglorious has quit [Quit: frigginglorious]
<asheesh>
And I guess what if you remove just one or two of the "return -EIO"?
<asheesh>
I guess presumably we know the answer. I guess I'm wondering exactly what to do now! Let me think about it more in a little bit.
frigginglorious has joined #sandstorm
bony has quit [Ping timeout: 240 seconds]
dwrensha has joined #sandstorm
<kentonv>
hmm, so who should tell Canonical that they broke Sandstorm development?