From: Sergei Trofimovich <slyich@gmail.com>
To: linux-btrfs@vger.kernel.org
Subject: Re: autodegrag: WARNING: at fs/inode.c:1315 iput+0x20b/0x210()
Date: Sat, 27 Aug 2011 17:15:46 +0300 [thread overview]
Message-ID: <20110827171546.43929e96@sf.home> (raw)
In-Reply-To: <20110826231844.04016b8f@sf.home>
[-- Attachment #1: Type: text/plain, Size: 1947 bytes --]
On Fri, 26 Aug 2011 23:18:44 +0300
Sergei Trofimovich <slyich@gmail.com> wrote:
> I used 3.1.0-rc2+ kernel for some weeks before without any dmesg warnings.
> I've decided to enable autodegrag feature for my btrfs / today and got
> warning in $SUBJ.
>
> It's an:
> > static void iput_final(struct inode *inode)
> > ...
> > WARN_ON(inode->i_state & I_NEW);
>
If you prefer nontainted kernel report (without unrelated warnings):
[ 282.380849] ------------[ cut here ]------------
[ 282.380865] WARNING: at fs/inode.c:1315 iput+0x20b/0x210()
[ 282.380869] Hardware name: HP Compaq 2510p Notebook PC
[ 282.380873] Modules linked in: ext2 loop kvm_intel kvm fuse scsi_wait_scan usb_storage tun i915 drm_kms_helper drm yenta_socket sdhci_pci sdhci snd_hda_codec_analog iwl4965 mmc_core i2c_algo_bit pcmcia_core thermal container ac button fan battery e1000e iwl_legacy mac80211 snd_hda_intel cfg80211 snd_hda_codec pcmcia_rsrc processor rfkill snd_hwdep
[ 282.380932] Pid: 715, comm: btrfs-cleaner Not tainted 3.1.0-rc3-00203-gdbf2e46 #139
[ 282.380936] Call Trace:
[ 282.380947] [<ffffffff8103e7ba>] warn_slowpath_common+0x7a/0xb0
[ 282.380954] [<ffffffff8103e805>] warn_slowpath_null+0x15/0x20
[ 282.380960] [<ffffffff810eafbb>] iput+0x20b/0x210
[ 282.380967] [<ffffffff811b990b>] btrfs_iget+0x1eb/0x4a0
[ 282.380975] [<ffffffff811c3ce6>] btrfs_run_defrag_inodes+0x136/0x210
[ 282.380982] [<ffffffff811ad76f>] cleaner_kthread+0x17f/0x1a0
[ 282.380988] [<ffffffff81035b7d>] ? sub_preempt_count+0x9d/0xd0
[ 282.380994] [<ffffffff811ad5f0>] ? transaction_kthread+0x280/0x280
[ 282.381001] [<ffffffff8105b056>] kthread+0x96/0xa0
[ 282.381027] [<ffffffff81433914>] kernel_thread_helper+0x4/0x10
[ 282.381034] [<ffffffff8105afc0>] ? kthread_worker_fn+0x190/0x190
[ 282.381039] [<ffffffff81433910>] ? gs_change+0xb/0xb
[ 282.381044] ---[ end trace 40720e359a3c0fea ]---
--
Sergei
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-08-27 14:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-26 20:18 autodegrag: WARNING: at fs/inode.c:1315 iput+0x20b/0x210() Sergei Trofimovich
2011-08-27 14:15 ` Sergei Trofimovich [this message]
2011-08-28 8:49 ` Sergei Trofimovich
2011-08-29 19:19 ` Sergei Trofimovich
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=20110827171546.43929e96@sf.home \
--to=slyich@gmail.com \
--cc=linux-btrfs@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;
as well as URLs for NNTP newsgroup(s).