linux-ext4.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alex <alex.vizor@gmail.com>
To: tytso@mit.edu, adilger.kernel@dilger.ca, linux-ext4@vger.kernel.org
Subject: Re: WARNING: at fs/inode.c:884 unlock_new_inode+0x34/0x59()
Date: Sun, 27 Nov 2011 23:24:03 +0300	[thread overview]
Message-ID: <4ED29C63.8070601@gmail.com> (raw)
In-Reply-To: <4ED2994A.9080907@gmail.com>

BTW, after last resume from disk fs was corrupted but fsck managed to 
fix this error. So I think severity of this issue should be raised.

On 11/27/2011 11:10 PM, Alex wrote:
> Hi guys,
>
> I'm using linux kernel 3.2-rc3. Since bugzilla.kernel.org is in down 
> I'm writing this email. After resuming from s2disk I get following error:
> Nov 27 19:42:38 alex kernel: [ 3827.422675] ------------[ cut here 
> ]------------
> Nov 27 19:42:38 alex kernel: [ 3827.422683] WARNING: at fs/inode.c:884 
> unlock_new_inode+0x34/0x59()
> Nov 27 19:42:38 alex kernel: [ 3827.422686] Hardware name: 4170CTO
> Nov 27 19:42:38 alex kernel: [ 3827.422688] Modules linked in: vfat 
> fat usb_storage uas cpufreq_stats rfcomm lockd 8021q garp stp llc
>  fcoe libfcoe libfc scsi_transport_fc scsi_tgt bnep ip6t_REJECT 
> nf_conntrack_ipv6 nf_defrag_ipv6 ip6table_filter ip6_tables nf_conntr
> ack_ipv4 nf_defrag_ipv4 xt_state nf_conntrack hdaps(O) 
> snd_hda_codec_hdmi snd_hda_codec_conexant virtio_net kvm_intel kvm 
> snd_hda_int
> el snd_hda_codec btusb snd_hwdep snd_seq snd_seq_device snd_pcm 
> snd_timer arc4 iwlwifi mac80211 cfg80211 wmi e1000e uvcvideo videodev
>  media v4l2_compat_ioctl32 bluetooth uinput pcspkr joydev 
> thinkpad_acpi snd snd_page_alloc soundcore i2c_i801 iTCO_wdt 
> iTCO_vendor_su
> pport rfkill binfmt_misc microcode sunrpc tp_smapi(O) thinkpad_ec(O) 
> sdhci_pci sdhci mmc_core [last unloaded: scsi_wait_scan]
> Nov 27 19:42:38 alex kernel: [ 3827.422738] Pid: 968, comm: abrtd 
> Tainted: G        W  O 3.2.0-0.rc3.git0.1.fc16.x86_64 #1
> Nov 27 19:42:38 alex kernel: [ 3827.422740] Call Trace:
> Nov 27 19:42:38 alex kernel: [ 3827.422744]  [<ffffffff810589c2>] 
> warn_slowpath_common+0x83/0x9b
> Nov 27 19:42:38 alex kernel: [ 3827.422747]  [<ffffffff810589f4>] 
> warn_slowpath_null+0x1a/0x1c
> Nov 27 19:42:38 alex kernel: [ 3827.422750]  [<ffffffff8113de44>] 
> unlock_new_inode+0x34/0x59
> Nov 27 19:42:38 alex kernel: [ 3827.422754]  [<ffffffff8118b6b8>] 
> ext4_new_inode+0xbc6/0xc5b
> Nov 27 19:42:38 alex kernel: [ 3827.422758]  [<ffffffff81196ca1>] 
> ext4_symlink+0x14d/0x2f4
> Nov 27 19:42:38 alex kernel: [ 3827.422762]  [<ffffffff8113592b>] 
> vfs_symlink+0x54/0x74
> Nov 27 19:42:38 alex kernel: [ 3827.422766]  [<ffffffff811356a1>] ? 
> user_path_create+0x4d/0x57
> Nov 27 19:42:38 alex kernel: [ 3827.422769]  [<ffffffff811371b8>] 
> sys_symlinkat+0x6b/0xb2
> Nov 27 19:42:38 alex kernel: [ 3827.422773]  [<ffffffff81137215>] 
> sys_symlink+0x16/0x18
> Nov 27 19:42:38 alex kernel: [ 3827.422777]  [<ffffffff81526042>] 
> system_call_fastpath+0x16/0x1b
> Nov 27 19:42:38 alex kernel: [ 3827.422780] ---[ end trace 
> 9866b4286b488fd4 ]---
>
> Kernel config is attached. Please let me know if I can help you with 
> anything to fix this issue
>
> Best regards,
> Alex


       reply	other threads:[~2011-11-27 20:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <4ED2994A.9080907@gmail.com>
2011-11-27 20:24 ` Alex [this message]
2011-11-27 21:34   ` WARNING: at fs/inode.c:884 unlock_new_inode+0x34/0x59() Ted Ts'o
2011-11-28 12:38     ` Alexander Zhavnerchik
     [not found]     ` <4ED3CF24.2050702@gmail.com>
2011-11-28 18:28       ` Theodore Tso
2011-11-28 19:08         ` Alex
2011-12-01 22:33           ` Eric Sandeen
2011-12-05 20:54     ` Eric Sandeen
2011-12-05 21:07       ` Eric Sandeen

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=4ED29C63.8070601@gmail.com \
    --to=alex.vizor@gmail.com \
    --cc=adilger.kernel@dilger.ca \
    --cc=linux-ext4@vger.kernel.org \
    --cc=tytso@mit.edu \
    /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;
as well as URLs for NNTP newsgroup(s).