From: "John L. Males" <jlmales@gmail.com>
To: Dave Hansen <dave@linux.vnet.ibm.com>
Cc: linux-kernel@vger.kernel.org
Subject: Linux Kernel Commit 025cee7f8fef02af09b03c8e1cd9843cb32adf9b
Date: Thu, 28 Feb 2013 17:11:43 -0500 [thread overview]
Message-ID: <20130228171143.5c32726d.jlmales@gmail.com> (raw)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Dave,
With respect to Linux Kernel Commit
025cee7f8fef02af09b03c8e1cd9843cb32adf9b Change Log:
<http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.4.34>
comment "It has probably been the cause of a number of subtle
bugs over the years, although the conditions to excite them
would have been hard to trigger."
Would the Linux Kernel under "unique" Virtual Memory Subsystem
stress excite some of these "subtle bugs" in Linux Kernels
prior to this change set for Commit
025cee7f8fef02af09b03c8e1cd9843cb32adf9b? I am not asking for
you to identify the subtle bugs. It is obvious it would be
difficult to determine from reported and unreported cases such
bugs. Just your sense or first hand knowledge if a Linux Kernel
under "unique" stress including Virtual Memory Subsystem stress
would be a key element of?
I am one of those who seems to often cause system kernels of
any OS stress due to my very high power user use of Operating
Systems and hence why my question.
Regards,
John L. Males
Toronto, Ontario
Canada
28 February 2013 17:11
<mailto:jlmales@gmail.com>
==============================================================
2013-02-28 16:57:24.110757989-0500-EST
28 Feb 16:57:24 ntpdate[27847]: ntpdate 4.2.6p2@1.2194-o Sun
Oct 17 13:35:14 UTC 2010 (1)
28 Feb 16:58:59 ntpdate[27852]: step time server 132.246.11.228
offset -0.000138 sec
Linux 3.4.24-kernel.org-jlm-010-amd64 #1 SMP PREEMPT Sun Dec 23
10:06:41 EST 2012
Modified Debian GNU/Linux 6.0.3 (squeeze)
(Evaluating alternatives to Debian)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAlEv1h8ACgkQ+V/XUtB6aBDSzQCgiu+hskZzz2bMfLG5u+Ao9YzJ
hwIAn1IY5jnq0sJjIe0nxFnA+LKrGtAh
=1KDN
-----END PGP SIGNATURE-----
next reply other threads:[~2013-02-28 22:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-28 22:11 John L. Males [this message]
2013-02-28 22:18 ` Linux Kernel Commit 025cee7f8fef02af09b03c8e1cd9843cb32adf9b Dave Hansen
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=20130228171143.5c32726d.jlmales@gmail.com \
--to=jlmales@gmail.com \
--cc=dave@linux.vnet.ibm.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.