From: Sasha Levin <sasha.levin@oracle.com>
To: Hugh Dickins <hughd@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Dave Jones <davej@redhat.com>
Subject: mm: shmem: WARNING: CPU: 1 PID: 8994 at mm/shmem.c:594 shmem_evict_inode+0x123/0x150()
Date: Tue, 08 Jul 2014 09:18:33 -0400 [thread overview]
Message-ID: <53BBEFA9.9020608@oracle.com> (raw)
Hi Hugh,
This is the first time I saw the warning at mm/shmem.c:594 getting hit. Your comments on
that warning is that you saw it getting hit yourself (and changed it from a BUG_ON to WARN),
but it's still useful to know about it.
So this is my FYI report about that warning still being triggered :)
[ 297.375500] WARNING: CPU: 1 PID: 8994 at mm/shmem.c:594 shmem_evict_inode+0x123/0x150()
[ 297.380368] Modules linked in:
[ 297.381370] CPU: 1 PID: 8994 Comm: trinity-c84 Not tainted 3.16.0-rc4-next-20140708-sasha-00022-g94c7290-dirty #770
[ 297.384668] 0000000000000009 ffff880248403ae8 ffffffff8d495ea4 0000000000000000
[ 297.387501] 0000000000000000 ffff880248403b28 ffffffff8a16ad4c ffff880248403b28
[ 297.389813] ffff88006d8340d0 ffff88006d8340d0 ffff88006d8340d0 ffff88006d834128
[ 297.393372] Call Trace:
[ 297.394791] dump_stack (lib/dump_stack.c:52)
[ 297.397459] warn_slowpath_common (kernel/panic.c:431)
[ 297.400225] warn_slowpath_null (kernel/panic.c:466)
[ 297.402078] shmem_evict_inode (mm/shmem.c:594 (discriminator 1))
[ 297.404050] evict (fs/inode.c:550)
[ 297.405639] iput (fs/inode.c:1438)
[ 297.407289] __dentry_kill (fs/dcache.c:292 fs/dcache.c:477)
[ 297.408206] ? dput (fs/dcache.c:509 fs/dcache.c:617)
[ 297.408971] dput (fs/dcache.c:521 fs/dcache.c:617)
[ 297.409731] __fput (fs/file_table.c:235)
[ 297.410692] ____fput (fs/file_table.c:253)
[ 297.411442] task_work_run (kernel/task_work.c:125 (discriminator 1))
[ 297.412242] do_exit (kernel/exit.c:756)
[ 297.412997] ? put_lock_stats.isra.12 (./arch/x86/include/asm/preempt.h:98 kernel/locking/lockdep.c:254)
[ 297.413933] ? _raw_spin_unlock_irq (./arch/x86/include/asm/paravirt.h:819 include/linux/spinlock_api_smp.h:168 kernel/locking/spinlock.c:199)
[ 297.414878] do_group_exit (kernel/exit.c:884)
[ 297.415674] get_signal_to_deliver (kernel/signal.c:2351)
[ 297.416626] ? vtime_account_user (kernel/sched/cputime.c:687)
[ 297.417558] do_signal (arch/x86/kernel/signal.c:698)
[ 297.418372] ? vtime_account_user (kernel/sched/cputime.c:687)
[ 297.419305] ? kmemleak_no_scan (mm/kmemleak.c:1102)
[ 297.420258] ? is_prefetch.isra.11 (arch/x86/mm/fault.c:158)
[ 297.421144] ? context_tracking_user_exit (./arch/x86/include/asm/paravirt.h:809 (discriminator 2) kernel/context_tracking.c:184 (discriminator 2))
[ 297.422120] ? __this_cpu_preempt_check (lib/smp_processor_id.c:63)
[ 297.423137] ? trace_hardirqs_on_caller (kernel/locking/lockdep.c:2557 kernel/locking/lockdep.c:2599)
[ 297.424139] do_notify_resume (arch/x86/kernel/signal.c:751)
[ 297.424974] retint_signal (arch/x86/kernel/entry_64.S:921)
Thanks,
Sasha
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
reply other threads:[~2014-07-08 13:27 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=53BBEFA9.9020608@oracle.com \
--to=sasha.levin@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=davej@redhat.com \
--cc=hughd@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).