From: Florian Mickler <florian@mickler.org>
To: Dan Carpenter <error27@gmail.com>
Cc: Jeff Mahoney <jeffm@suse.com>,
Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
balbir@linux.vnet.ibm.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] taskstats: Use better ifdef for alignment
Date: Sun, 2 Jan 2011 13:17:47 +0100 [thread overview]
Message-ID: <20110102131747.3e79107a@schatten.dmk.lab> (raw)
In-Reply-To: <20110101165135.GJ1886@bicker>
On Sat, 1 Jan 2011 19:51:35 +0300
Dan Carpenter <error27@gmail.com> wrote:
> On Sat, Jan 01, 2011 at 05:19:46PM +0100, Florian Mickler wrote:
> > Is there already a patch available or integrated into iotop which
> > fixes this? I'd think that if the kernel could wait on fixed iotop's to
> > be distributed it would be easier to sell the breakage on bugzilla &
> > co...
> >
>
> The story is that 4be2c95d1f "taskstats: pad taskstats netlink response
> for aligment issues on ia64" broke iotop on 64 bit processors (32 bit
> was unaffected). This patch fixes it for x86-64 and powerpc-64.
>
> On the other 64 bit processors iotop works but instead you get a message
> in dmesg:
> kernel unaligned access to 0xe000023879dca9bc, ip=0xa000000100133d10
>
> So on those arches you were already getting posts to bugzilla etc. Now
> those people can upgrade the kernel and download iotop version 0.4.2 or
> higher.
>
> regards,
> dan carpenter
>
Ah ok. And probably bug #24272 is related to this. If I
understood it correctly 85893120 fixed some runtime warnings (or more
exactly the misaligning) and broke iotop in the process (on all of 64
bit).
4be2c95d1f undid that and enhanced the netlink messages on IA64
archs with a new type to fix the alignment and now it's changed to
align well on all archs that need alignment, leaving archs unbroken that
have efficient unaligned access (x86-64 and powerpc-64). Nice.
And to answer my original question, i just checked out (some?/the?)
iotop sources from git://repo.or.cz/iotop.git and found a fix[1] for the
issue with 85893120.
Is iotop parsing fixed to ignore the null-field in the meantime?
Thx,
Flo
[1]git://repo.or.cz/iotop.git:commit 08211d209ae8fc7e67ea3bebb09979ff61c70f97
Author: Guillaume Chazarain <guichaz@gmail.com>
Date: Sat Sep 4 13:57:43 2010 +0200
Instead of assuming the pid field is 4 bytes long, take its length from the header.
This is needed for http://lkml.org/lkml/2010/2/12/167
[PATCH] delayacct: align to 8 byte boundary on 64-bit systems
next prev parent reply other threads:[~2011-01-02 12:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 0:12 [PATCH] taskstats: Use better ifdef for alignment Jeff Mahoney
2010-12-30 0:14 ` Andrew Morton
2010-12-30 5:26 ` Jeff Mahoney
2010-12-30 5:32 ` Andrew Morton
2010-12-30 15:52 ` Jeff Mahoney
2011-01-01 16:19 ` Florian Mickler
2011-01-01 16:51 ` Dan Carpenter
2011-01-02 12:17 ` Florian Mickler [this message]
2011-01-08 22:42 ` Florian Mickler
2011-01-08 22:46 ` Jeff Mahoney
2010-12-31 0:23 ` David Miller
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=20110102131747.3e79107a@schatten.dmk.lab \
--to=florian@mickler.org \
--cc=akpm@linux-foundation.org \
--cc=balbir@linux.vnet.ibm.com \
--cc=davem@davemloft.net \
--cc=error27@gmail.com \
--cc=jeffm@suse.com \
--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