From: Philippe De Muyter <phdm@macqel.be>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: linux-m68k@lists.linux-m68k.org, Greg Ungerer <gerg@uclinux.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] m68k: Use generic strncpy_from_user(), strlen_user(), and strnlen_user()
Date: Wed, 6 Jun 2012 17:20:30 +0200 [thread overview]
Message-ID: <20120606152030.GA9809@frolo.macqel> (raw)
In-Reply-To: <CAMuHMdW0XqO9iOiuOXrRao_A41L-0iZXXyZugCmiizG=7-VkHg@mail.gmail.com>
Hi Geert,
On Wed, Jun 06, 2012 at 03:44:03PM +0200, Geert Uytterhoeven wrote:
> On Wed, May 30, 2012 at 4:04 PM, Philippe De Muyter <phdm@macqel.be> wrote:
> >> > Sorry, I did not follow what happened to unaligned accesses, but
> >> > CPU32 family (at least 68340) crashes on unaligned accesses.
> >>
> >> We don't seem to have CONFIG_M68340 in arch/m68k/Kconfig.cpu?
> >
> > I have a local port here (but based on an ancient linux kernel, 2.6.2 IIRC)
>
> Just to be sure: basically include/asm-m68knommu/unaligned.h has always
> been wrong (also in 2.6.2), so you had to fix this locally?
I have just verified, and you are right :
include/asm-m68knommu/unaligned.h was wrong in 2.6.2
But I did not have to fix it locally.
I remember the ppp driver kernel doing by error unaligned accesses
(of course without using unaligned macros) and crashing my kernel.
I fixed the error in the ppp driver and the fix went into the
mainline kernel.
I am not aware that unaligned macros were used in the parts of the
kernel I used on this board. Just to be sure I made a quick list :
$ find -name \*.o | sed -e 's/\.o$/.c/' | xargs grep t_unaligned 2> /dev/null
./fs/partitions/msdos.c:#define SYS_IND(p) (get_unaligned(&p->sys_ind))
./fs/partitions/msdos.c: get_unaligned(&p->nr_sects); \
./fs/partitions/msdos.c: get_unaligned(&p->start_sect); \
./drivers/net/slhc.c: put_unaligned(ip_fast_csum(icp, ip->ihl),
I am 100% sure I did not use msdos partitions on that board. I don't
know why msdos.c was compiled in. For the slhc case, I surmise that it
was not used because its usage depends on some option we did not use.
Best regards
Philippe
--
Philippe De Muyter +32 2 6101532 Macq SA rue de l'Aeronef 2 B-1140 Bruxelles
next prev parent reply other threads:[~2012-06-06 15:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-29 21:33 [PATCH] m68k: Use generic strncpy_from_user(), strlen_user(), and strnlen_user() Geert Uytterhoeven
2012-05-30 3:07 ` Greg Ungerer
2012-05-30 10:22 ` Philippe De Muyter
2012-05-30 11:20 ` Geert Uytterhoeven
[not found] ` <CAMuHMdV5GVZR1BvGD3EncDFfPt=Bt9ndkKE8Mp7euE9KoSaGNQ@mail.gmail.com>
2012-05-30 14:04 ` Philippe De Muyter
2012-06-05 20:57 ` Geert Uytterhoeven
[not found] ` <CAMuHMdW29QYN6XpBb9F3GGoJ-9frrD-00Wx=FchT9ALqW1LcPg@mail.gmail.com>
2012-06-06 6:31 ` Greg Ungerer
2012-06-06 17:46 ` Geert Uytterhoeven
[not found] ` <CAMuHMdWg6W4uOm3N-etXJud5Lw-vBkstQ2h7HK=6i+sCLgeksQ@mail.gmail.com>
2012-06-07 11:10 ` Greg Ungerer
2012-06-07 13:14 ` Andreas Schwab
[not found] ` <m2bokvw9f1.fsf@igel.home>
2012-06-08 4:14 ` Greg Ungerer
2012-06-06 13:44 ` Geert Uytterhoeven
2012-06-06 15:20 ` Philippe De Muyter [this message]
2012-05-30 14:42 ` Andreas Schwab
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=20120606152030.GA9809@frolo.macqel \
--to=phdm@macqel.be \
--cc=geert@linux-m68k.org \
--cc=gerg@uclinux.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-m68k@lists.linux-m68k.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