WARNING: at /build/buildd/linux-2.6.35/ubuntu/aufs/plink.c:332 au_plink_append+0x1f1/0x2e0 [aufs]()
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| | linux (Ubuntu) |
Low
|
Andy Whitcroft | ||
| | Maverick |
Low
|
Unassigned | ||
| | Natty |
Low
|
Andy Whitcroft | ||
Bug Description
This happens when using aufs schroots.
ProblemType: KernelOops
DistroRelease: Ubuntu 10.10
Package: linux-image-
Regression: Yes
ProcVersionSign
Uname: Linux 2.6.35-16-generic x86_64
Annotation: Your system might become unstable now and might need to be restarted.
Architecture: amd64
Date: Fri Aug 20 10:51:21 2010
Failure: oops
SourcePackage: linux
Title: WARNING: at /build/
| Marc Deslauriers (mdeslaur) wrote : | #1 |
| Jamie Strandboge (jdstrand) wrote : | #2 |
| tags: | added: kj-triage |
| Jamie Strandboge (jdstrand) wrote : | #3 |
Marking Confirmed since the security team sees this regularly. Setting to 'High' as we need to reboot after performing a build otherwise there are stability issues. I see this on virtually every build these days.
| Changed in linux (Ubuntu): | |
| importance: | Undecided → High |
| status: | New → Confirmed |
| Marc Deslauriers (mdeslaur) wrote : | #4 |
I hit this every couple of days while building stuff with sbuild.
| Kees Cook (kees) wrote : | #5 |
I hit this too; seems easy to trigger with mk-sbuild's schroots.
| Jamie Strandboge (jdstrand) wrote : | #6 |
I should mention that I started seeing this in Maverick, and continue to see it in up to date Natty.
| Jamie Strandboge (jdstrand) wrote : | #7 |
Actually, in natty the Oops is in the attached.
| Jamie Strandboge (jdstrand) wrote : | #8 |
| Changed in linux (Ubuntu Natty): | |
| assignee: | nobody → Canonical Kernel Team (canonical-kernel-team) |
| Changed in linux (Ubuntu Maverick): | |
| status: | New → Confirmed |
| Brian Murray (brian-murray) wrote : | #9 |
These bug reports might be related to this one:
621763-
623489-
623546-
627861-
629749-
630515-
630629-
630952-
631628-
631855-
632511-
632761-
633307-
633539-
634534-
641389-
646291-
654071-
654307-
656703-
657458-
685740-
| Tim Gardner (timg-tpi) wrote : | #10 |
Jamie - the next time it happens on Natty, please attach the whole dmesg so that we get the exact kernel version, etc.
| Changed in linux (Ubuntu Natty): | |
| assignee: | Canonical Kernel Team (canonical-kernel-team) → Andy Whitcroft (apw) |
| Jamie Strandboge (jdstrand) wrote : | #11 |
Tim, after a reboot and a single attempt at a build, here is your dmesg.
| Andy Whitcroft (apw) wrote : | #12 |
Looking at the errors in comment #11 from Natty, we see the following:
[ 134.061517] WARNING: at .../ubuntu/
[ 134.061519] Hardware name: 5129CTO
[ 134.061520] pseudo-link is not flushed
[...]
[ 134.061641] [<ffffffff81182
This is being triggered out of an unmount of the union mount. Looking at the
code this seems to be a benign warning, note how the code goes on to flush out the links and clean up:
void au_plink_put(struct super_block *sb, int verbose)
[...]
[...]
I would not expect this to trigger any instability. I think this warning likely should be squashed in general on the unmount path.
Looking at the Maverick errors as originally reported we see the following:
WARNING: at .../ubuntu/
Hardware name: 6459CTO
unexpectedly many pseudo links, 101
[...]
[<
This is a completly different error. However this also does not appear to be anything other than a diagnostic. It implies we have a large number of pseudo links, but processing goes on as normal:
void au_plink_
{
[...]
if (!found) {
[...]
As this list is maintained via RCU it is possible for this list to grow quite large under high load. This also looks like a candidate for removal as a benign message.
@All -- can you confirm that there are stability issues on Maverick associated with aufs use here? If so what are the symptoms. Just seeing these messages are not in of themselves indications of anything other than use of aufs itself.
@Jamie -- could you confirm whether you are seeing any bad effects with the Natty kernel in the face of the error there. I believe that is a different and very likely benign message.
| Jamie Strandboge (jdstrand) wrote : | #13 |
@Andy -- Thank you so much for looking at this. I can't say for sure I have seen instability on natty as a result of this bug, because unity and the kernel have been rather cantankerous with me during the natty cycle. Up until yesterday, I thought that this bug might be aggravating my (extremely annoying) linux/qemu-kvm bug #694029, but I don't believe that to be the case anymore. I'm all for squashing the warning if it is indeed benign, cause as is clear from this bug, it can be confusing. :)
| Changed in linux (Ubuntu Natty): | |
| importance: | High → Low |
| Changed in linux (Ubuntu Natty): | |
| status: | Confirmed → Fix Committed |
| Launchpad Janitor (janitor) wrote : | #14 |
This bug was fixed in the package linux - 2.6.38-1.27
---------------
linux (2.6.38-1.27) natty; urgency=low
[ Andy Whitcroft ]
* ubuntu: AUFS -- update aufs-update to track new locations of headers
* ubuntu: AUFS -- update to c5021514085a5d9
* SAUCE: ensure root is ready before running usermodehelpers in it
* correct the Vcs linkage to point to natty
* rebase to linux tip e78bf5e6cbe837d
* [Config] update configs following rebase
e78bf5e6cbe
* SAUCE: Yama: follow changes to generic_permission
* ubuntu: compcache -- follow changes to bd_claim/bd_release
* ubuntu: iscsitarget -- follow changes to open_bdev_exclusive
* ubuntu: ndiswrapper -- fix interaction between __packed and packed
* ubuntu: AUFS -- update to 806051bcbeec277
* update package version to match payload version
* rebase to e6f597a1425b5af
* rebase to v2.6.38-rc1
* [Config] updateconfigs following rebase to v2.6.38-rc1
* SAUCE: x86 fix up jiffies/jiffies_64 handling
* rebase to linus tip 2b1caf6ed7b888c
* [Config] updateconfigs following rebase to
2b1caf6ed7b
* [Config] disable CONFIG_
* ubuntu: AUFS -- suppress benign plink warning messages
- LP: #621195
* [Config] CONFIG_NR_CPUS=256 for amd64 -server flavour
* rebase to v2.6.38-rc2
* rebase to mainline d315777b32a4696
* rebase to c723fdab8aa728d
* [Config] update configs following rebase to
c723fdab8aa
* [Config] disable CONFIG_AD7152 to fix FTBS on armel versatile
* [Config] disable CONFIG_AD7150 to fix FTBS on armel versatile
* [Config] disable CONFIG_RTL8192CE to fix FTBS on armel omap
* [Config] disable CONFIG_MANTIS_CORE to fix FTBS on armel versatile
[ Kees Cook ]
* SAUCE: kernel: make /proc/kallsyms mode 400 to reduce ease of attacking
[ Stefan Bader ]
* Temporarily disable RODATA for virtual i386
- LP: #699828
[ Tim Gardner ]
* [Config] CONFIG_
- LP: #683690
* [Config] CONFIG_
* update bnx2 firmware files in d-i/firmware/
[ Upstream Kernel Changes ]
* Revert "drm/radeon/bo: add some fallback placements for VRAM only
objects."
* packaging: make System.map mode 0600
* thinkpad_acpi: Always report scancodes for hotkeys
- LP: #702407
* sched: tg->se->load should be initialised to tg->shares
* Input: sysrq -- ensure sysrq_enabled and __sysrq_enabled are consistent
* brcm80211: include linux/slab.h for kfree
* pch_dma: add include/slab.h for kfree
* i2c-eg20t: include linux/slab.h for kfree
* gpio/ml_ioh_gpio: include linux/slab.h for kfree
* tty: include linux/slab.h for kfree
* winbond: include linux/delay.h for mdelay et al
[ Upstream Kernel Changes ]
* mark the start of v2.6.38 versioning
* rebase v2.6.37 to v2.6.38-rc2 + c723fdab8aa728d
- LP: #689886
- LP: #702125
- LP: #608775
- LP: #215802
...
| Changed in linux (Ubuntu Natty): | |
| status: | Fix Committed → Fix Released |
| Changed in linux (Ubuntu Maverick): | |
| importance: | Undecided → Low |
| Adam Conrad (adconrad) wrote : Update Released | #15 |
The verification of this Stable Release Update has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regresssions.
| Julian Wiedmann (jwiedmann) wrote : | #16 |
This release has reached end-of-life [0].
| Changed in linux (Ubuntu Maverick): | |
| status: | Confirmed → Invalid |
I've seen this occasionally as well.