From: Randy Dunlap <rdunlap@xenotime.net>
To: Alessandro Suardi <alessandro.suardi@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: warn_slowpath_common WARNING on boot since 3.0.0-git7
Date: Sat, 30 Jul 2011 19:18:55 -0700 [thread overview]
Message-ID: <20110730191855.eaec670f.rdunlap@xenotime.net> (raw)
In-Reply-To: <CAKWSe6B3hWt4ANpgoS4dRUZPju0Abey9y3DORVFqGYgMeF=gQA@mail.gmail.com>
On Sat, 30 Jul 2011 17:31:51 +0200 Alessandro Suardi wrote:
> F15 x86_64, still present in 3.0.0-git11; didn't report it earlier as I
> thought it'd be squashed sooner... probably it's not as common
> as I thought it'd be:
>
> Jul 27 18:46:18 duff kernel: WARNING: at fs/proc/base.c:1123
> oom_adjust_write+0x185/0x23c()
> Jul 27 18:46:18 duff kernel: Hardware name: Latitude E6400
> Jul 27 18:46:18 duff kernel: sshd (3245): /proc/3245/oom_adj is
> deprecated, please use /proc/3245/oom_score_adj instead.
Looks like sshd is using a deprecated /proc interface.
fs/proc/base.c:1118 says:
* Warn that /proc/pid/oom_adj is deprecated, see
* Documentation/feature-removal-schedule.txt.
What else needs to be done here?
> Jul 27 18:46:18 duff kernel: Modules linked in: sunrpc rfcomm bnep
> ip6t_REJECT nf_conntrack_ipv6 ipt_REJECT nf_defrag_ipv6
> nf_conntrack_ipv4 ip6table_filter nf_defrag_ipv4 ip6_tables xt_state
> nf_conntrack iptable_filter ip_tables snd_hda_codec_hdmi
> snd_hda_codec_idt snd_hda_intel snd_hda_codec aes_x86_64 aes_generic
> ecb snd_hwdep btusb snd_seq snd_seq_device bluetooth snd_pcm
> dell_laptop snd_timer snd i2c_i801 rfkill microcode pcspkr joydev
> soundcore snd_page_alloc dcdbas ipv6 autofs4 ext4 jbd2 crc16 sdhci_pci
> firewire_ohci sdhci firewire_core crc_itu_t mmc_core i915
> drm_kms_helper drm i2c_algo_bit i2c_core video [last unloaded:
> scsi_wait_scan]
> Jul 27 18:46:18 duff kernel: Pid: 3245, comm: sshd Not tainted 3.0.0-git7 #6
> Jul 27 18:46:18 duff kernel: Call Trace:
> Jul 27 18:46:18 duff kernel: [<ffffffff8103774c>] warn_slowpath_common+0x7e/0x96
> Jul 27 18:46:18 duff kernel: [<ffffffff810377f8>] warn_slowpath_fmt+0x41/0x43
> Jul 27 18:46:18 duff kernel: [<ffffffff810408f4>] ? ns_capable+0x35/0x4a
> Jul 27 18:46:18 duff kernel: [<ffffffff81129fb8>] oom_adjust_write+0x185/0x23c
> Jul 27 18:46:18 duff kernel: [<ffffffff810e0736>] vfs_write+0xa3/0xca
> Jul 27 18:46:18 duff kernel: [<ffffffff8109176f>] ?
> trace_hardirqs_on_caller+0xe/0x22
> Jul 27 18:46:18 duff kernel: [<ffffffff810e08d2>] sys_write+0x45/0x69
> Jul 27 18:46:18 duff kernel: [<ffffffff813752fb>] system_call_fastpath+0x16/0x1b
---
~Randy
*** Remember to use Documentation/SubmitChecklist when testing your code ***
next prev parent reply other threads:[~2011-07-31 2:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 15:31 Alessandro Suardi
2011-07-31 2:18 ` Randy Dunlap [this message]
2011-07-31 16:20 ` Alessandro Suardi
2011-08-01 20:38 ` Alessandro Suardi
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=20110730191855.eaec670f.rdunlap@xenotime.net \
--to=rdunlap@xenotime.net \
--cc=alessandro.suardi@gmail.com \
--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
all inboxes | Powered by JetHome®