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

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

Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later

Started byBen Hutchings <ben@decadent.org.uk>
First post2016-01-26 02:40 +0100
Last post2016-02-13 00:00 +0100
Articles 8 — 4 participants

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

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

Contents

  Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later Ben Hutchings <ben@decadent.org.uk> - 2016-01-26 02:40 +0100
    Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later Roger Shimizu <rogershimizu@gmail.com> - 2016-01-26 11:20 +0100
      Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later Ben Hutchings <ben@decadent.org.uk> - 2016-01-26 14:50 +0100
    Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later Zachary Loafman <zml@google.com> - 2016-01-26 16:40 +0100
      Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later Ben Hutchings <ben@decadent.org.uk> - 2016-01-26 19:00 +0100
        Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later Akihiro Suda <suda.kyoto@gmail.com> - 2016-01-27 08:50 +0100
        Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later Zachary Loafman <zml@google.com> - 2016-02-12 23:50 +0100
          Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later Ben Hutchings <ben@decadent.org.uk> - 2016-02-13 00:00 +0100

#52445 — Bug#812207: linux: AUFS can hang up; Please update to v20160111 or later

FromBen Hutchings <ben@decadent.org.uk>
Date2016-01-26 02:40 +0100
SubjectBug#812207: linux: AUFS can hang up; Please update to v20160111 or later
Message-ID<qV0LU-4dv-13@gated-at.bofh.it>

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

Control: tag -1 patch moreinfo

On Thu, 21 Jan 2016 15:08:17 +0000 Akihiro Suda <suda.kyoto@gmail.com> wrote:
> Source: linux-image-3.16.0-4

Please use 'reportbug kernel' to report any future kernel bugs, as that
will select the correct package name automatically.

> Version: 3.16.7-ckt20
> Severity: important
> 
> Dear Maintainer,
> 
> AUFS can hang up (more precisely, produces unkillable processes) with kernel 3.16.7-ckt20 due to commit 296291cdd1629c308114504b850dc343eabc278 appeared in ckt20.
> http://kernel.ubuntu.com/git/ubuntu/linux.git/tag/?h=linux-3.16.y&id=v3.16.7-ckt20
> http://kernel.ubuntu.com/git/ubuntu/linux.git/commit/?h=linux-3.16.y&id=475a23000dd8d2f264bab9d6eb71a2a6b9d4de72
> 
> Many docker users have been experiencing this issue: https://github.com/docker/docker/issues/18180
> 
> The issue has been fixed since AUFS v20160111: http://permalink.gmane.org/gmane.linux.file-systems.aufs.user/5345
> So I suggest updating AUFS to v20160111 or later.

We can't do that because it is no longer supported on Linux 3.x (and
not all the changes would be suitable for a stable update, anyway).

> Although I didn't test for 3.16.7, I think merging this commit is enough: https://github.com/sfjro/aufs4-linux/commit/f60d586b7b8cae42bacc603d192810db85278d3c

That and the previous commit appear to be sufficient, though they
needed some minor changes.  Please can you test whether the attached
patches work, following the procedure at
<https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official>.

Ben.

-- 
Ben Hutchings
Q.  Which is the greater problem in the world today, ignorance or apathy?
A.  I don't know and I couldn't care less.

[toc] | [next] | [standalone]

#52452

FromRoger Shimizu <rogershimizu@gmail.com>
Date2016-01-26 11:20 +0100
Message-ID<qV8T8-2E6-17@gated-at.bofh.it>
In reply to#52445
On Tue, Jan 26, 2016 at 10:36 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
> On Thu, 21 Jan 2016 15:08:17 +0000 Akihiro Suda <suda.kyoto@gmail.com> wrote:
>
> Please use 'reportbug kernel' to report any future kernel bugs, as that
> will select the correct package name automatically.

I didn't find this command to report bug in wiki [0][1], which is
better to add them.

[0]: https://wiki.debian.org/DebianKernel
[1]: https://wiki.debian.org/DebianKernelReportingBugs

-- 
Roger Shimizu, GMT +9 Tokyo
PGP/GPG: 17B3ACB1

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

#52456

FromBen Hutchings <ben@decadent.org.uk>
Date2016-01-26 14:50 +0100
Message-ID<qVcal-4P7-9@gated-at.bofh.it>
In reply to#52452

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

On Tue, 2016-01-26 at 19:14 +0900, Roger Shimizu wrote:
> On Tue, Jan 26, 2016 at 10:36 AM, Ben Hutchings <ben@decadent.org.uk> wrote:
> > On Thu, 21 Jan 2016 15:08:17 +0000 Akihiro Suda  wrote:
> > 
> > Please use 'reportbug kernel' to report any future kernel bugs, as that
> > will select the correct package name automatically.
> 
> I didn't find this command to report bug in wiki [0][1], which is
> better to add them.
> 
> [0]: https://wiki.debian.org/DebianKernel
> [1]: https://wiki.debian.org/DebianKernelReportingBugs

Those pages are quite poorly maintained and contain a lot of redundant
information (some of which is better maintained in kernel-handbook).
I've made a few quick fixes but if you could give them a more thorough
review that would be very helpful.

Ben.

-- 
Ben Hutchings
Q.  Which is the greater problem in the world today, ignorance or apathy?
A.  I don't know and I couldn't care less.

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

#52458

FromZachary Loafman <zml@google.com>
Date2016-01-26 16:40 +0100
Message-ID<qVdSN-644-1@gated-at.bofh.it>
In reply to#52445

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

On Mon, Jan 25, 2016 at 5:36 PM, Ben Hutchings <ben@decadent.org.uk> wrote:

> > Although I didn't test for 3.16.7, I think merging this commit is
> enough:
> https://github.com/sfjro/aufs4-linux/commit/f60d586b7b8cae42bacc603d192810db85278d3c
>
> That and the previous commit appear to be sufficient, though they
> needed some minor changes.  Please can you test whether the attached
> patches work, following the procedure at
> <
> https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
> >.
>

I tested these patches on Jessie and they seem to work. Methodology: I spun
up an 3.16.7-ckt20-1+deb8u3 image in GCE, made sure
https://hub.docker.com/r/akihirosuda/test18180/ failed as expected. I built
a 3.16.7-ckt20-1+deb8u3 kernel with those patches quilted in and ran the
same image:

zml@jessie:~$ sudo docker run -it --rm akihirosuda/test18180
[INFO] Checking whether hitting docker#18180.
....................................................................................................
[INFO] OK. not hitting docker#18180.
[INFO] Checking whether sendfile(2) is killable.
[INFO] If the container hangs up here, you are still facing the bug
that linux@296291cd tried to fix.
/test.sh: line 22:  3308 Killed                  /sendfile-test
zml@jessie:~$

I think we're golden. (Container is not hung, both the original bug
and the new bug are fixed.)

...Zach

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

#52461

FromBen Hutchings <ben@decadent.org.uk>
Date2016-01-26 19:00 +0100
Message-ID<qVg4j-7AF-11@gated-at.bofh.it>
In reply to#52458

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

Control: tag -1 - moreinfo
Control: tag -1 pending

On Tue, 2016-01-26 at 07:37 -0800, Zachary Loafman wrote:
> On Mon, Jan 25, 2016 at 5:36 PM, Ben Hutchings <ben@decadent.org.uk> wrote:
> 
> > > Although I didn't test for 3.16.7, I think merging this commit is
> > enough:
> > https://github.com/sfjro/aufs4-linux/commit/f60d586b7b8cae42bacc603d192810db85278d3c
> > 
> > That and the previous commit appear to be sufficient, though they
> > needed some minor changes.  Please can you test whether the attached
> > patches work, following the procedure at
> > <
> > https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
> > > .
> > 
> 
> I tested these patches on Jessie and they seem to work. Methodology: I spun
> up an 3.16.7-ckt20-1+deb8u3 image in GCE, made sure
> https://hub.docker.com/r/akihirosuda/test18180/ failed as expected. I built
> a 3.16.7-ckt20-1+deb8u3 kernel with those patches quilted in and ran the
> same image:
> 
> zml@jessie:~$ sudo docker run -it --rm akihirosuda/test18180
> [INFO] Checking whether hitting docker#18180.
> ....................................................................................................
> [INFO] OK. not hitting docker#18180.
> [INFO] Checking whether sendfile(2) is killable.
> [INFO] If the container hangs up here, you are still facing the bug
> that linux@296291cd tried to fix.
> /test.sh: line 22:  3308 Killed                  /sendfile-test
> zml@jessie:~$
> 
> I think we're golden. (Container is not hung, both the original bug
> and the new bug are fixed.)

Thanks, I've queued these up for inclusion in the next security update.

Ben.

-- 
Ben Hutchings
Q.  Which is the greater problem in the world today, ignorance or apathy?
A.  I don't know and I couldn't care less.

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

#52466

FromAkihiro Suda <suda.kyoto@gmail.com>
Date2016-01-27 08:50 +0100
Message-ID<qVt1v-7Z-5@gated-at.bofh.it>
In reply to#52461
I also tested, and it works!

Thank you for patches Ben, thank you for testing Zachary, and thank
you for pointing out Roger san!

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

#52826

FromZachary Loafman <zml@google.com>
Date2016-02-12 23:50 +0100
Message-ID<r1uHf-4N4-9@gated-at.bofh.it>
In reply to#52461

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

Ben -

Thanks for queueing these. I've been trying to figure out the process from
this point forward, though, and wondering if you can help educate me.
Looking at
http://metadata.ftp-master.debian.org/changelogs/main/l/linux/?C=M;O=A, it
looks like there has been at least (4.3.5-1) unstable and (4.4.1-1~exp1)
experimental builds since the patches were queued, but I don't think I saw
the aufs patches in those changelogs. I also haven't yet seen any builds
beyond those, and those are both lower urgency, it looks like.

If these were queued for a security update, is there a deadline timer
before they go out for jessie-security and wheezy-backports, or does it
just mean they're on a security train that goes out with the next CVE?

Thanks.

...Zach

On Tue, Jan 26, 2016 at 9:53 AM, Ben Hutchings <ben@decadent.org.uk> wrote:

> Control: tag -1 - moreinfo
> Control: tag -1 pending
>
> On Tue, 2016-01-26 at 07:37 -0800, Zachary Loafman wrote:
> > On Mon, Jan 25, 2016 at 5:36 PM, Ben Hutchings <ben@decadent.org.uk>
> wrote:
> >
> > > > Although I didn't test for 3.16.7, I think merging this commit is
> > > enough:
> > >
> https://github.com/sfjro/aufs4-linux/commit/f60d586b7b8cae42bacc603d192810db85278d3c
> > >
> > > That and the previous commit appear to be sufficient, though they
> > > needed some minor changes.  Please can you test whether the attached
> > > patches work, following the procedure at
> > > <
> > >
> https://kernel-handbook.alioth.debian.org/ch-common-tasks.html#s-common-official
> > > > .
> > >
> >
> > I tested these patches on Jessie and they seem to work. Methodology: I
> spun
> > up an 3.16.7-ckt20-1+deb8u3 image in GCE, made sure
> > https://hub.docker.com/r/akihirosuda/test18180/ failed as expected. I
> built
> > a 3.16.7-ckt20-1+deb8u3 kernel with those patches quilted in and ran the
> > same image:
> >
> > zml@jessie:~$ sudo docker run -it --rm akihirosuda/test18180
> > [INFO] Checking whether hitting docker#18180.
> >
> ....................................................................................................
> > [INFO] OK. not hitting docker#18180.
> > [INFO] Checking whether sendfile(2) is killable.
> > [INFO] If the container hangs up here, you are still facing the bug
> > that linux@296291cd tried to fix.
> > /test.sh: line 22:  3308 Killed                  /sendfile-test
> > zml@jessie:~$
> >
> > I think we're golden. (Container is not hung, both the original bug
> > and the new bug are fixed.)
>
> Thanks, I've queued these up for inclusion in the next security update.
>
> Ben.
>
> --
> Ben Hutchings
> Q.  Which is the greater problem in the world today, ignorance or apathy?
> A.  I don't know and I couldn't care less.
>

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

#52827

FromBen Hutchings <ben@decadent.org.uk>
Date2016-02-13 00:00 +0100
Message-ID<r1uQW-4Rz-1@gated-at.bofh.it>
In reply to#52826

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

On Fri, 2016-02-12 at 14:41 -0800, Zachary Loafman wrote:
> Ben -
> 
> Thanks for queueing these. I've been trying to figure out the process from
> this point forward, though, and wondering if you can help educate me.
> Looking at
> http://metadata.ftp-master.debian.org/changelogs/main/l/linux/?C=M;O=A, it
> looks like there has been at least (4.3.5-1) unstable and (4.4.1-1~exp1)
> experimental builds since the patches were queued, but I don't think I saw
> the aufs patches in those changelogs. I also haven't yet seen any builds
> beyond those, and those are both lower urgency, it looks like.

Those versions of the kernel package do not include aufs at all.  (They
do have a few supporting changes that allow aufs to be built separately
as a module.)

> If these were queued for a security update, is there a deadline timer
> before they go out for jessie-security and wheezy-backports, or does it
> just mean they're on a security train that goes out with the next CVE?

The latter.

Ben.

-- 
Ben Hutchings
I say we take off; nuke the site from orbit.  It's the only way to be sure.

[toc] | [prev] | [standalone]

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

csiph-web