linux-sh.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Matt Fleming <matt@console-pimps.org>
To: linux-sh@vger.kernel.org
Subject: Re: Unaligned kernel access for __udivsi3_i4i
Date: Sat, 20 Feb 2010 11:47:16 +0000	[thread overview]
Message-ID: <20100220114716.GB9774@console-pimps.org> (raw)
In-Reply-To: <5ec3d7931002191551g21c0cda9le17729529b1afd78@mail.gmail.com>

On Sat, Feb 20, 2010 at 01:24:38AM +0100, Drasko DRASKOVIC wrote:
> 
> Does that mean that we can do division by zero that goes completely
> unnoticed, unless we turn up the warnings (as kernel will fix these
> unalignments without even reporting it)?
> 

Unfortunately, yes.

> Doing: echo 1 > /proc/cpu/kernel_alignement, I saw that the kernel
> unaligned access was reported. Would that say that some module is
> trying division by zero, and not the application itself (because I did
> echo 1 > /proc/cpu/alignment at the same time, and it was not reported
> as User fault)? I am trying to isolate guilty party, so I would like
> to know if it comes from the user space or kernel module (or kernel
> itself).
> 

I would suspect that it is a kernel module that is doing the division by
zero in that case.

> Do you have some ah hoc ideas what would be best strategy to trace
> this call back?
> 

Perhaps insert a call to dump_stack() in inc_unaligned_kernel_access()?
That should give you some information about who called __udivsi3_i4i.


  parent reply	other threads:[~2010-02-20 11:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-19 23:51 Unaligned kernel access for __udivsi3_i4i Drasko DRASKOVIC
2010-02-20  0:08 ` Matt Fleming
2010-02-20  0:24 ` Drasko DRASKOVIC
2010-02-20 11:47 ` Matt Fleming [this message]
2010-02-20 12:17 ` Paul Mundt

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=20100220114716.GB9774@console-pimps.org \
    --to=matt@console-pimps.org \
    --cc=linux-sh@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;
as well as URLs for NNTP newsgroup(s).