On Wed, 6 Aug 2008, Stanislav Meduna wrote:
> So what should the applications calling openssl actually
> do if this happens? Now the ssh/apache/... simply exit,
> which is bad (it left me without an access to a remote
> box...).
Exiting is the best behaviour - continuing without a good source
of
> Tried many many times, even two running at the same time
> or poll timeout set to zero, not one instance of blocking
> even with
>od -x /dev/urandom
> and
>od -x /dev/random
> running simultaneously (the second one blocks, of course).
>
>
> H.. what the #$%# is happening here.. more
This is a note to let you know that we have just queued up the patch titled
Subject: uml: deal with host time going backwards
to the 2.6.25-stable tree. Its filename is
uml-deal-with-host-time-going-backwards.patch
A git repo of this tree can be found at
http://www.kernel.org/gi
This is a note to let you know that we have just queued up the patch titled
Subject: uml: fix bad NTP interaction with clock
to the 2.6.25-stable tree. Its filename is
uml-fix-bad-ntp-interaction-with-clock.patch
A git repo of this tree can be found at
http://www.kernel.org/git/
This is a note to let you know that we have just queued up the patch titled
Subject: uml: fix build when SLOB is enabled
to the 2.6.25-stable tree. Its filename is
uml-fix-build-when-slob-is-enabled.patch
A git repo of this tree can be found at
http://www.kernel.org/git/?p=linux
This is a note to let you know that we have just queued up the patch titled
Subject: uml: fix gcc ICEs and unresolved externs
to the 2.6.25-stable tree. Its filename is
uml-fix-gcc-ices-and-unresolved-externs.patch
A git repo of this tree can be found at
http://www.kernel.org/gi
This is a note to let you know that we have just queued up the patch titled
Subject: uml: memcpy export needs to follow host declaration
to the 2.6.25-stable tree. Its filename is
uml-memcpy-export-needs-to-follow-host-declaration.patch
A git repo of this tree can be found at
h
This is a note to let you know that we have just queued up the patch titled
Subject: uml: stub needs to tolerate SIGWINCH
to the 2.6.25-stable tree. Its filename is
uml-stub-needs-to-tolerate-sigwinch.patch
A git repo of this tree can be found at
http://www.kernel.org/git/?p=lin
This is a note to let you know that we have just queued up the patch titled
Subject: uml: physical memory shouldn't include initial stack
to the 2.6.25-stable tree. Its filename is
uml-physical-memory-shouldn-t-include-initial-stack.patch
A git repo of this tree can be found at
This is a note to let you know that we have just queued up the patch titled
Subject: uml: track and make up lost ticks
to the 2.6.25-stable tree. Its filename is
uml-track-and-make-up-lost-ticks.patch
A git repo of this tree can be found at
http://www.kernel.org/git/?p=linux/ker
On Sat, 16 Aug 2008 15:32:38 -0700
<[EMAIL PROTECTED]> wrote:
Hi Greg
while these notifications are very useful in general, I think you want
to exclude lkml as a destination to send them to.
--
If you want to reach me at my work email, use [EMAIL PROTECTED]
For development, discussion an
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Dike <[EMAIL PROTECTED]>
commit 43f5b3085fdd27c4edf535d938b2cb0ccead4f75 upstream
Reintroduce uml_kmalloc for the benefit of UML libc code. The
previous tactic of declaring __kmalloc so
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Dike <[EMAIL PROTECTED]>
commit cfd28f6695d0fc047478480791a21bdd4967f98e upstream
UML's supposed nanosecond clock interacts badly with NTP when NTP
decides that the clock has drifted ahe
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Dike <[EMAIL PROTECTED]>
commit 60a2988aea701a6424809a5432bf068667aac177 upstream
The top of physical memory should be below the initial process stack, not the
top of the address space,
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Dike <[EMAIL PROTECTED]>
commit fe2cc53ee013a4d4d0317d418e7019fe6533a5a8 upstream
Alarm delivery could be noticably late in the !CONFIG_NOHZ case because lost
ticks weren't being taken i
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Al Viro <[EMAIL PROTECTED]>
commit 296cd66f7f6e130fe08e6880ecb13c3fc615a8db upstream
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
Acked-by: Jeff Dike <[EMAIL PROTECTED]>
Signed-off-by: Linus To
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Dike <[EMAIL PROTECTED]>
commit 06e1e4ffbd1932e288839b3140cda6b8141eb684 upstream
Protection against the host's time going backwards (eg, ntp activity on
the host) by keeping track of th
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Tom Spink <[EMAIL PROTECTED]>
commit 40fb16a360d9c6459afee91dc793c1e3374feb94 upstream
This patch makes os_get_task_size locate the bottom of the address space,
as well as the top. This is f
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Al Viro <[EMAIL PROTECTED]>
commit 3e3b48e5198544dd90e27265a70c1a834139e025 upstream
Signed-off-by: Al Viro <[EMAIL PROTECTED]>
Cc: Jeff Dike <[EMAIL PROTECTED]>
Signed-off-by: Linus Torvalds
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Dike <[EMAIL PROTECTED]>
commit 8bfd04b974689f700bbd053ad6e66b0a95fb80c9 upstream
x86_64 defines either memcpy or __memcpy depending on the gcc version, and
it looks like UML needs to fo
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Dike <[EMAIL PROTECTED]>
commit 3d5ede6f776bdb1483bcd086f79c3bf41fed3865 upstream
We lost the marking of SIGWINCH as being OK to receive during stub
execution, causing a panic should tha
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Dike <[EMAIL PROTECTED]>
commit f1ef9167ca4494a8c6d71d0031c73e9c8841eadd upstream
Fedora broke PTRACE_SYSEMU again, and UML crashes as a result when it
doesn't need to. This patch makes
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Dike <[EMAIL PROTECTED]>
commit 4f81c5350b44bcc501ab6f8a089b16d064b4d2f6 upstream
There are various constraints on the use of unit-at-a-time:
- i386 uses no-unit-at-a-time for pre-4.0 (
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Jeff Dike <[EMAIL PROTECTED]>
commit 7c1fed03b9fa32d4323d5caa6a9c7dcdd7eba767 upstream
My copying of linux/init.h didn't go far enough. The definition of
__used singled out gcc minor version
2.6.25-stable review patch. If anyone has any objections, please let us know.
--
From: Ingo Molnar <[EMAIL PROTECTED]>
commit b6d8adf477439e7086224bc9674c6b6638780783 upstream.
Include limits.h to get a definition of PATH_MAX.
Signed-off-by: Ingo Molnar <[EMAIL PROTECTED]>
Sig
25 matches
Mail list logo
