Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.kernel > #59339 > unrolled thread

Bug#880655: SMB mount/umount between 2 docker containers causes kernel Oops

Started byFabian Holler <fabian.holler@simplesurance.de>
First post2017-11-03 12:20 +0100
Last post2017-11-05 01:10 +0100
Articles 4 — 3 participants

Back to article view | Back to linux.debian.kernel


Contents

  Bug#880655: SMB mount/umount between 2 docker containers causes kernel Oops Fabian Holler <fabian.holler@simplesurance.de> - 2017-11-03 12:20 +0100
    Bug#880655: SMB mount/umount between 2 docker containers causes kernel Oops Ben Hutchings <ben@decadent.org.uk> - 2017-11-05 01:10 +0100
      Bug#880655: SMB mount/umount between 2 docker containers causes kernel Oops Fabian Holler <fabian.holler@simplesurance.de> - 2017-11-06 10:10 +0100
    Processed: Re: Bug#880655: SMB mount/umount between 2 docker  containers causes kernel Oops owner@bugs.debian.org (Debian Bug Tracking System) - 2017-11-05 01:10 +0100

#59339 — Bug#880655: SMB mount/umount between 2 docker containers causes kernel Oops

FromFabian Holler <fabian.holler@simplesurance.de>
Date2017-11-03 12:20 +0100
SubjectBug#880655: SMB mount/umount between 2 docker containers causes kernel Oops
Message-ID<uHIb0-3sf-3@gated-at.bofh.it>

[Multipart message — attachments visible in raw view] — view raw

Package: linux-image-4.9.0-4-amd64
Version: 4.9.51-1

Running Samba in one docker container and mounting/umounting a SMB share of it
in a second docker container causes a kernel Oops.
The machine did not crash with linux-image-4.9.0-4-amd64=4.9.51-1.

The bug can be reproduced by https://github.com/fho/docker-samba-loop.

I was also able to reproduce a kernel Oops with the docker-samba-loop scripts
in multiple Ubuntu kernels (incl. machine crashes).
The trace looks different on linux-image-4.9.0-4-amd64. It might be a
different issue.
Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 might be related,
it's about the "unregister_netdevice: waiting for lo to become free."
messages.

The kernel log is attached.

[toc] | [next] | [standalone]


#59350

FromBen Hutchings <ben@decadent.org.uk>
Date2017-11-05 01:10 +0100
Message-ID<uIgFI-6fj-19@gated-at.bofh.it>
In reply to#59339

[Multipart message — attachments visible in raw view] — view raw

Control: reassign -1 src:linux 4.9.51-1

On Fri, 2017-11-03 at 12:08 +0100, Fabian Holler wrote:
> Package: linux-image-4.9.0-4-amd64
> Version: 4.9.51-1
> 
> Running Samba in one docker container and mounting/umounting a SMB share of it
> in a second docker container causes a kernel Oops.
> The machine did not crash with linux-image-4.9.0-4-amd64=4.9.51-1.

That's the same version you're reporting as failing.  Which version is
working?

Ben.

> The bug can be reproduced by https://github.com/fho/docker-samba-loop.
> 
> I was also able to reproduce a kernel Oops with the docker-samba-loop scripts
> in multiple Ubuntu kernels (incl. machine crashes).
> The trace looks different on linux-image-4.9.0-4-amd64. It might be a
> different issue.
> Ubuntu bug report: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1729637
> https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1711407 might be related,
> it's about the "unregister_netdevice: waiting for lo to become free."
> messages.
> 
> The kernel log is attached.
-- 
Ben Hutchings
I'm not a reverse psychological virus.  Please don't copy me into your
sig.

[toc] | [prev] | [next] | [standalone]


#59360

FromFabian Holler <fabian.holler@simplesurance.de>
Date2017-11-06 10:10 +0100
Message-ID<uILzP-TG-1@gated-at.bofh.it>
In reply to#59350
On Sun, Nov 05, 2017 at 12:01:11AM +0000, Ben Hutchings wrote:
> Control: reassign -1 src:linux 4.9.51-1
> 
> On Fri, 2017-11-03 at 12:08 +0100, Fabian Holler wrote:
> > Package: linux-image-4.9.0-4-amd64
> > Version: 4.9.51-1
> > 
> > Running Samba in one docker container and mounting/umounting a SMB share of it
> > in a second docker container causes a kernel Oops.
> > The machine did not crash with linux-image-4.9.0-4-amd64=4.9.51-1.
> 
> That's the same version you're reporting as failing.  Which version is
> working?

Yes, the Oops happens with linux-image-4.9.0-4-amd64=4.9.51-1.
I meant the Oops happened with that kernel but after the Oops the machine
continued to run.

I tried it again again and the machine crashed on the 2. try.

[toc] | [prev] | [next] | [standalone]


#59351 — Processed: Re: Bug#880655: SMB mount/umount between 2 docker containers causes kernel Oops

Fromowner@bugs.debian.org (Debian Bug Tracking System)
Date2017-11-05 01:10 +0100
SubjectProcessed: Re: Bug#880655: SMB mount/umount between 2 docker containers causes kernel Oops
Message-ID<uIgFI-6fj-21@gated-at.bofh.it>
In reply to#59339
Processing control commands:

> reassign -1 src:linux 4.9.51-1
Bug #880655 [linux-image-4.9.0-4-amd64] SMB mount/umount between 2 docker containers causes kernel Oops
Bug reassigned from package 'linux-image-4.9.0-4-amd64' to 'src:linux'.
No longer marked as found in versions linux/4.9.51-1.
Ignoring request to alter fixed versions of bug #880655 to the same values previously set
Bug #880655 [src:linux] SMB mount/umount between 2 docker containers causes kernel Oops
Marked as found in versions linux/4.9.51-1.

-- 
880655: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=880655
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems

[toc] | [prev] | [standalone]


Back to top | Article view | linux.debian.kernel


csiph-web