linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: tixy@linaro.org (Jon Medhurst (Tixy))
To: linux-arm-kernel@lists.infradead.org
Subject: .align may cause data to be interpreted as instructions
Date: Wed, 16 Oct 2013 18:03:45 +0100	[thread overview]
Message-ID: <1381943025.3419.59.camel@linaro1.home> (raw)
In-Reply-To: <1381939571.3419.44.camel@linaro1.home>

On Wed, 2013-10-16 at 17:06 +0100, Jon Medhurst (Tixy) wrote:
> On Wed, 2013-10-16 at 12:13 +0100, Ben Dooks wrote:
> > On 15/10/13 23:38, Taras Kondratiuk wrote:
> > > Hi
> > >
> > > I was debugging kprobes-test for BE8 and noticed that some data fields
> > > are stored in LE instead of BE. It happens because these data fields
> > > get interpreted as instructions.
> > >
> > > Is it a known issue?
> > 
> > I reported the crashes to Tixy along with a different
> > method of sovling the problem (changed to using pointers to
> > the strings) a while ago.
> 
> I found that fix in the list archives:
> http://lists.infradead.org/pipermail/linux-arm-kernel/2013-July/186528.html
> 
> >  However it seems that nothing has
> > happened to fix this.
> >
> > Since kprobes seems to work with the fixed tests I forgot
> > to follow up and prod Jon about looking into this problem.
> 
> Sorry, I sorta forgot/ignored the issue, strange compiler problem with a
> vague explanation on a big-endian kernel (who uses that ;-)
> 
> > Jon, if you are not interested in fixing this, then please
> > let me know and we can get a patch sorted to fix it.
> 
> Looking at your old patch again, it looks good to me. 

Actually it's broken for thumb, the pointer to the title needs storing
at a 4 byte alignment, which presumably will make the problem we're
trying to workaround re-occur. I'll try and find some time to take a
look for a different way of doing things...

-- 
Tixy

  reply	other threads:[~2013-10-16 17:03 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-15 22:38 .align may cause data to be interpreted as instructions Taras Kondratiuk
2013-10-16 11:13 ` Ben Dooks
2013-10-16 16:06   ` Jon Medhurst (Tixy)
2013-10-16 17:03     ` Jon Medhurst (Tixy) [this message]
2013-10-16 21:16       ` Taras Kondratiuk
2013-10-16 15:28 ` Jon Medhurst (Tixy)
2013-10-17 12:17 ` Jon Medhurst (Tixy)
2013-10-17 18:09   ` Taras Kondratiuk
     [not found] <20131016192512.GB21726@localhost.localdomain>
2013-10-16 20:47 ` Taras Kondratiuk
2013-10-16 21:17   ` Måns Rullgård
     [not found] <20131017125533.GD2442@localhost.localdomain>
2013-10-18 11:03 ` Jon Medhurst (Tixy)
2013-10-18 12:36   ` Taras Kondratiuk

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=1381943025.3419.59.camel@linaro1.home \
    --to=tixy@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.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).