From: Mihai Moldovan <ionic@ionic.de>
To: Dan Carpenter <error27@gmail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: openssh-server: sshd (<pid>): /proc/<pid>/oom_adj is deprecated, please use /proc/<pid>/oom_score_adj instead.
Date: Wed, 03 Aug 2011 01:14:43 +0200 [thread overview]
Message-ID: <4E3884E3.1090709@ionic.de> (raw)
In-Reply-To: <20110802225825.GE3839@shale.localdomain>
[-- Attachment #1: Type: text/plain, Size: 947 bytes --]
Hi Dan,
* On 03.08.2011 12:58 AM, Dan Carpenter wrote:
> Debian testing and Fedora 14 (and 15) are still using an old version
> of sshd so in 3.1, I get a popup in gnome that a "kernel crash has
> been detected."
> [...]
> There was a warning there for a year, and the distributions have one
> more year to upgrade to the newer software, so it's valid to apply
> pressure now.
>
> Could we do it in a way that made it more clear that the problem was
> an old version of openssh-server and not the kernel? The information
> is there, but it's overwhelmed in stack trace spam. Also the kernel
> is tainted now because of sshd. Maybe the message could include a
> link to a wiki page that told people which version off sshd uses the
> new proc file.
Please read and add your thoughts to this thread:
https://lkml.org/lkml/2011/8/1/433
(Actually you just created a duplicate discussion. ;))
Best regards,
Mihai
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4369 bytes --]
next prev parent reply other threads:[~2011-08-02 23:14 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20110514102014.12739.91576.reportbug@eiffel4.mcfm>
[not found] ` <20110801122537.GA9469@mwanda>
[not found] ` <alpine.DEB.2.00.1108011206130.28986@chino.kir.corp.google.com>
2011-08-02 22:58 ` openssh-server: sshd (<pid>): /proc/<pid>/oom_adj is deprecated, please use /proc/<pid>/oom_score_adj instead Dan Carpenter
2011-08-02 23:14 ` Mihai Moldovan [this message]
2011-08-03 4:53 ` David Rientjes
2011-08-03 12:21 ` 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=4E3884E3.1090709@ionic.de \
--to=ionic@ionic.de \
--cc=error27@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