From: "Américo Wang" <xiyou.wangcong@gmail.com>
To: linux-kernel@vger.kernel.org
Cc: William Irwin <wli@holomorphy.com>,
James Morris <jmorris@namei.org>, Mel Gorman <mel@csn.ul.ie>,
Andrew Morton <akpm@linux-foundation.org>,
Serge Hallyn <serue@us.ibm.com>,
David Howells <dhowells@redhat.com>
Subject: hugetlbfs warning in mmtom
Date: Fri, 18 Sep 2009 11:26:56 +0800 [thread overview]
Message-ID: <2375c9f90909172026o6095f0adx46df2bb05c46ff89@mail.gmail.com> (raw)
It seems that this one is not reported yet.
Please feel free to ask more info from me if you need.
Here it is:
Sep 17 16:07:24 dhcp-66-70-5 kernel: ------------[ cut here ]------------
Sep 17 16:07:24 dhcp-66-70-5 kernel: WARNING: at
fs/hugetlbfs/inode.c:957 hugetlb_file_setup+0x136/0x398()
Sep 17 16:07:24 dhcp-66-70-5 kernel: Hardware name: PowerEdge T105
Sep 17 16:07:24 dhcp-66-70-5 kernel: Using mlock ulimits for
SHM_HUGETLB deprecated
Sep 17 16:07:24 dhcp-66-70-5 kernel: Modules linked in: ib_iser
rdma_cm ib_cm iw_cm ib_sa ib_mad ib_core ib_addr ipv6 iscsi_tcp
libiscsi_tcp libiscsi scsi_transport_iscsi cpufreq_ondemand
powernow_k8 freq_table dm_multipath scsi_dh video output sbs sbshc
battery acpi_memhotplug ac parport_pc lp parport sg dcdbas sr_mod
cdrom serio_raw tg3 libphy button rtc_cmos rtc_core rtc_lib
i2c_nforce2 i2c_core shpchp pcspkr dm_snapshot dm_zero dm_mirror
dm_region_hash dm_log dm_mod sata_nv libata sd_mod scsi_mod ext3 jbd
uhci_hcd ohci_hcd ehci_hcd
Sep 17 16:07:24 dhcp-66-70-5 kernel: Pid: 3240, comm: auditd Tainted:
G W 2.6.31-mm1 #1
Sep 17 16:07:24 dhcp-66-70-5 kernel: Call Trace:
Sep 17 16:07:24 dhcp-66-70-5 kernel: [<ffffffff811d8414>] ?
hugetlb_file_setup+0x136/0x398
Sep 17 16:07:24 dhcp-66-70-5 kernel: [<ffffffff8106352a>] ?
warn_slowpath_common+0xb8/0xe5
Sep 17 16:07:24 dhcp-66-70-5 kernel: [<ffffffff810635e5>] ?
warn_slowpath_fmt+0x66/0x7c
Sep 17 16:07:24 dhcp-66-70-5 kernel: [<ffffffff811f92f4>] ?
security_capable+0x4b/0x54
Sep 17 16:07:24 dhcp-66-70-5 kernel: [<ffffffff81070d26>] ? capable+0x3e/0x79
Sep 17 16:07:24 dhcp-66-70-5 kernel: [<ffffffff8111aeb9>] ?
user_shm_lock+0x9b/0xf1
Sep 17 16:07:24 dhcp-66-70-5 kernel: [<ffffffff811d8414>] ?
hugetlb_file_setup+0x136/0x398
Sep 17 16:07:24 dhcp-66-70-5 kernel: [<ffffffff8111e75a>] ?
do_mmap_pgoff+0x28c/0x608
Sep 17 16:07:24 dhcp-66-70-5 kernel: [<ffffffff8108d896>] ? up_read+0x10/0x19
Sep 17 16:07:24 dhcp-66-70-5 kernel: [<ffffffff8101246d>] ? sys_mmap+0xcb/0x124
Sep 17 16:07:24 dhcp-66-70-5 kernel: [<ffffffff8100c7ab>] ?
system_call_fastpath+0x16/0x1b
Sep 17 16:07:24 dhcp-66-70-5 kernel: ---[ end trace d386d7615cf4b03d ]---
next reply other threads:[~2009-09-18 3:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-18 3:26 Américo Wang [this message]
2009-09-18 7:45 ` Mel Gorman
2009-09-18 8:38 ` Andrew Morton
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=2375c9f90909172026o6095f0adx46df2bb05c46ff89@mail.gmail.com \
--to=xiyou.wangcong@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=jmorris@namei.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mel@csn.ul.ie \
--cc=serue@us.ibm.com \
--cc=wli@holomorphy.com \
/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
all inboxes | Powered by JetHome®