public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Richard Zidlicky <rz@linux-m68k.org>
To: linux-kernel@vger.kernel.org
Subject: ext3 mkdir mutex bug?
Date: Tue, 16 Jun 2009 14:28:31 +0200	[thread overview]
Message-ID: <20090616122831.GA6423@linux-m68k.org> (raw)

[-- Attachment #1: Type: text/plain, Size: 2730 bytes --]

Hi,

is this a known problem?

Regards
Richard

Jun 16 09:01:06 richard kernel: [   85.231233] ------------[ cut here ]------------
Jun 16 09:01:06 richard kernel: [   85.231258] WARNING: at /home/rz/rpmbuild/kernels/linux-2.6.30/kernel/mutex-debug.c:105 mutex_destroy+0x35/0x3f()
Jun 16 09:01:06 richard kernel: [   85.231272] Hardware name: NB81005
Jun 16 09:01:06 richard kernel: [   85.231280] Modules linked in: i915 i2c_algo_bit rfcomm l2cap bluetooth ppdev parport_pc lp parport autofs4 acpi_cpufreq cpufreq_userspace cpufreq_conservative cpufreq_powersave cpufreq_stats pci_slot sbs sbshc container drm i2c_core ipv6 snd_hda_codec_realtek arc4 ecb snd_hda_intel snd_hda_codec snd_hwdep snd_pcm_oss snd_mixer_oss snd_pcm uvcvideo videodev v4l1_compat video output rtc_cmos snd_seq_dummy ath5k serio_raw mac80211 led_class cfg80211 r8169 mii battery ac snd_seq_oss snd_seq_midi button processor snd_rawmidi snd_seq_midi_event snd_seq snd_timer pcspkr pata_acpi snd_seq_device iTCO_wdt iTCO_vendor_support intel_agp snd agpgart shpchp soundcore snd_page_alloc xt_multiport nf_conntrack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack xt_tcpudp ipt_LOG xt_limit iptable_filter ip_tables x_tables thermal fan fuse loop nls_iso8859_1 vfat fat squashfs ata_generic ehci_hcd isofs
Jun 16 09:01:06 richard kernel: [   85.231685] Pid: 4246, comm: pulseaudio Not tainted 2.6.30v1 #1
Jun 16 09:01:06 richard kernel: [   85.231696] Call Trace:
Jun 16 09:01:06 richard kernel: [   85.231719]  [<c042d5cc>] warn_slowpath_common+0x60/0x90
Jun 16 09:01:06 richard kernel: [   85.231737]  [<c042d609>] warn_slowpath_null+0xd/0x10
Jun 16 09:01:06 richard kernel: [   85.231754]  [<c0449bfa>] mutex_destroy+0x35/0x3f
Jun 16 09:01:06 richard kernel: [   85.231774]  [<c04b7a70>] unlock_new_inode+0x24/0x93
Jun 16 09:01:06 richard kernel: [   85.231792]  [<c04f4611>] ext3_mkdir+0x23c/0x270
Jun 16 09:01:07 richard kernel: [   85.231809]  [<c04af2b5>] vfs_mkdir+0xc1/0x12e
Jun 16 09:01:07 richard kernel: [   85.231825]  [<c04b1578>] sys_mkdirat+0x8c/0xc7
Jun 16 09:01:07 richard kernel: [   85.231843]  [<c0493581>] ? remove_vma+0x55/0x5b
Jun 16 09:01:07 richard kernel: [   85.231860]  [<c04941c9>] ? do_munmap+0x21c/0x237
Jun 16 09:01:07 richard kernel: [   85.231878]  [<c04030ff>] ? sysenter_do_call+0x2d/0x38
Jun 16 09:01:07 richard kernel: [   85.231898]  [<c0578754>] ? trace_hardirqs_on_thunk+0xc/0x10
Jun 16 09:01:07 richard kernel: [   85.231915]  [<c0403119>] ? sysenter_exit+0xf/0x1a
Jun 16 09:01:07 richard kernel: [   85.231932]  [<c04b15c3>] sys_mkdir+0x10/0x12
Jun 16 09:01:07 richard kernel: [   85.231949]  [<c04030e4>] sysenter_do_call+0x12/0x38
Jun 16 09:01:07 richard kernel: [   85.231962] ---[ end trace fcd76b47795c1c4a ]---

[-- Attachment #2: config.bz2 --]
[-- Type: application/x-bzip2, Size: 24362 bytes --]

                 reply	other threads:[~2009-06-16 12:30 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20090616122831.GA6423@linux-m68k.org \
    --to=rz@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox