From: Nathan Zimmer <nzimmer@sgi.com>
To: Holger Hans Peter Freyther <holger@freyther.de>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: /proc/timer_list and weird behavior with dropbear
Date: Fri, 19 Jul 2013 10:45:15 -0500 [thread overview]
Message-ID: <51E95F0B.6080703@sgi.com> (raw)
In-Reply-To: <20130719152800.GA20792@xiaoyu.lan>
On 07/19/2013 10:28 AM, Holger Hans Peter Freyther wrote:
> Dear Nathan,
>
> I am currently upgrading a kernel for a TI Davinci DM644x based design
> from Linux 3.2 to Linux 3.10.1. I have a funny re-producible issue that
> goes away by reverting b3956a896ea57f25cacd74708b8fab611543a81d.
>
> The dropbear sshd will open several files after accepting a connection to
> generate some entropy. The "/proc/timer_list" file is part of that[1].
> It will open that file and will try to read until the end of the file, but
> most of the time this end never comes. According to strace the read on the
> fd will always return 2048. I have attached the testcase I am using to
> re-produce the issue.
>
> Can this be re-produced by anyone else?
>
> holger
>
>
>
> [1] https://secure.ucc.asn.au/hg/dropbear/file/028fa77f952f/random.c#l204
>
I hadn't noticed anything.
Let me try your program and see what I may have missed.
next prev parent reply other threads:[~2013-07-19 15:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-19 15:28 Holger Hans Peter Freyther
2013-07-19 15:45 ` Nathan Zimmer [this message]
2013-07-19 17:03 ` Holger Hans Peter Freyther
2013-07-19 19:05 ` Nathan Zimmer
2013-07-19 20:33 ` Nathan Zimmer
2013-07-19 20:37 ` Nathan Zimmer
2013-07-20 5:43 ` Holger Hans Peter Freyther
2013-07-22 21:18 ` [PATCH] timer_list: Correct the show function for timer_list by using iter->now Nathan Zimmer
2013-07-23 7:18 ` Holger Hans Peter Freyther
2013-07-23 22:50 ` Nathan Zimmer
2013-07-24 14:31 ` [PATCH] timer_list: Correct the iterator for timer_list Nathan Zimmer
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=51E95F0B.6080703@sgi.com \
--to=nzimmer@sgi.com \
--cc=holger@freyther.de \
--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
Powered by JetHome