From: Florian Mickler <florian@mickler.org>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"David S. Miller" <davem@davemloft.net>,
Dan Carpenter <error27@gmail.com>,
balbir@linux.vnet.ibm.com,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] taskstats: Use better ifdef for alignment
Date: Sat, 1 Jan 2011 17:19:46 +0100 [thread overview]
Message-ID: <20110101171946.6179c3b6@schatten.dmk.lab> (raw)
In-Reply-To: <4D1CAAA1.8030106@suse.com>
On Thu, 30 Dec 2010 10:52:01 -0500
Jeff Mahoney <jeffm@suse.com> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 12/30/2010 12:32 AM, Andrew Morton wrote:
> > On Thu, 30 Dec 2010 00:26:34 -0500 Jeff Mahoney <jeffm@suse.com> wrote:
> >
> >> On 12/29/2010 07:14 PM, Andrew Morton wrote:
> >>> On Wed, 29 Dec 2010 19:12:08 -0500 Jeff Mahoney <jeffm@suse.com> wrote:
> >>>
> >>>> Commit 4be2c95d added a null field to align the taskstats structure but
> >>>> the discussion centered around ia64. The issue exists on other platforms
> >>>> with inefficient unaligned access and adding them piecemeal would be
> >>>> an unmaintainable mess.
> >>>>
> >>>> This patch uses Dave Miller's suggestion of using a combination of
> >>>> CONFIG_64BIT && !CONFIG_HAVE_EFFICIENT_UNALIGNED_ACCESS to determine
> >>>> whether alignment is needed.
> >>>>
> >>>> Note that this will cause breakage on those platforms with applications
> >>>> like iotop which had hard-coded offsets into the packet to access the
> >>>> taskstats structure.
> >>>
> >>> That seems a very good reason to not apply the patch.
> >>>
> >>> Tell us more, please...
> >>
> >> I don't want to rehash the same discussion
> >
> > Please do so. That discussion went on for a long time over many emails
> > and multiple iterations of the patch. I personally have forgotten the
> > reasoning and if I could remember it, I wouldn't remember which version
> > of the patch it applied to.
> >
> > Applying a patch which is *known* to break *known* userspace
> > applications is a quite extraordinary thing to do. We owe it to people
> > to fully explain the reasoning.
>
> Ok, so the gist is that iotop makes what I'd call unreasonable
> assumptions about the contents of a netlink genetlink packet containing
> generic attributes.
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...
Just my 2 cents, but I don't know enough to weigh the different aspects
of this... iotop shurely is not a showstopper if the upsides of this
patch are big enough?
Regards,
Flo
next prev parent reply other threads:[~2011-01-01 16:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-30 0:12 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 [this message]
2011-01-01 16:51 ` Dan Carpenter
2011-01-02 12:17 ` Florian Mickler
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=20110101171946.6179c3b6@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
Powered by JetHome