All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Hurley <peter@hurleysoftware.com>
To: sparclinux@vger.kernel.org
Subject: Re: RED state exception (trap type 0x64) on U5 reboot
Date: Wed, 20 Nov 2013 11:50:52 +0000	[thread overview]
Message-ID: <528CA21C.1020200@hurleysoftware.com> (raw)
In-Reply-To: <alpine.SOC.1.00.1310151347070.902@math.ut.ee>

On 11/17/2013 03:35 PM, Meelis Roos wrote:
> This patch seems to switch ldata with its read_buf and echo_buf from
> kmalloc/kfree to vmalloc/vfree (the bufs are now inlined in ldata, not
> separately allocated).
>
> More fields in ldata are now explicitly initialized to zero instead of
> kzalloc doing it before. However, I do not see the initialization of
> some of the fields - maybe they are done later in the code? I noticed
> process_char_map, raw, real_raw, icanon, read_buf, echo_buf that were
> zeroed before but I did not find explicit zeroing of them after the
> patch. However, just adding a memset to zero ldata after vmalloc does
> not change anything.

process_char_map, raw, real_raw & icanon are initialized in the
n_tty_set_termios() called from n_tty_open() where ldata is first allocated.

read_buf is the uninitialized buffer indexed by read_head, canon_head,
read_tail & line_start. echo_buf similarly is uninitialized and indexed by
echo_head, echo_tail & echo_commit.

Regards,
Peter Hurley

  parent reply	other threads:[~2013-11-20 11:50 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 11:51 RED state exception (trap type 0x64) on U5 reboot Meelis Roos
2013-10-21  8:58 ` Meelis Roos
2013-10-23 15:00 ` Peter Hurley
2013-10-24 11:48 ` Meelis Roos
2013-11-17 20:35 ` Meelis Roos
2013-11-17 20:52 ` Meelis Roos
2013-11-18  6:21 ` Meelis Roos
2013-11-18 12:41 ` Peter Hurley
2013-11-18 13:51 ` Peter Hurley
2013-11-18 15:46 ` Meelis Roos
2013-11-19 14:23 ` Peter Hurley
2013-11-20 11:50 ` Peter Hurley [this message]
2013-11-27 17:39 ` Meelis Roos
2013-11-28  1:38 ` Meelis Roos
2013-11-28 16:47 ` Meelis Roos
2013-11-29  7:31 ` Meelis Roos
2013-11-30 21:42 ` Meelis Roos
2013-11-30 23:04 ` Peter Hurley
2013-11-30 23:07 ` Peter Hurley
2013-12-01  1:18 ` Peter Hurley
2013-12-01  1:31 ` Meelis Roos
2013-12-01  1:32 ` Meelis Roos
2013-12-01  2:07 ` Peter Hurley
2013-12-01  2:40 ` Peter Hurley
2013-12-01  8:16 ` Meelis Roos
2013-12-01 14:39 ` Peter Hurley
2013-12-03 16:11 ` Meelis Roos
2013-12-03 16:47 ` Peter Hurley
2013-12-04 15:35 ` Meelis Roos
2013-12-06 15:54 ` Peter Hurley
2014-06-16  9:21 ` Meelis Roos
2014-06-16 14:37 ` Peter Hurley
2014-06-16 15:14 ` Christoph Lameter
2014-06-17 10:38 ` Meelis Roos
2014-06-17 14:14 ` Christoph Lameter
2014-06-17 15:50 ` Meelis Roos

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=528CA21C.1020200@hurleysoftware.com \
    --to=peter@hurleysoftware.com \
    --cc=sparclinux@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.