mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Eric Paris <eparis@redhat.com>
To: Tvrtko Ursulin <tvrtko.ursulin@sophos.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>,
	Andreas Gruenbacher <agruen@suse.de>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: struct fanotify_event_metadata
Date: Thu, 19 Aug 2010 13:53:46 -0400	[thread overview]
Message-ID: <1282240426.21419.1716.camel@acb20005.ipt.aol.com> (raw)
In-Reply-To: <201008191644.29299.tvrtko.ursulin@sophos.com>

On Thu, 2010-08-19 at 16:44 +0100, Tvrtko Ursulin wrote:
> On Saturday 14 Aug 2010 18:44:38 Andreas Schwab wrote:
> > The pid field of struct fanotify_event_metadata has 64 bits which looks
> > excessive.  Wouldn't it make sense to make it 32 bits and swap it with
> > the mask field?  That would avoid the unaligned mask field, and remove
> > the need for the packed attribute.

Wish this thought came up 2 weeks ago  :)  It's going to stay __packed__
no matter what, even if the alignment works out nicely and it doesn't do
anything.

I'm certainly willing to shrink the pid and switch some locations if
noone objects but it will definitely break userspace, in that it is
going to require a recompile of anyone's userspace listener (the
interface was only intended to grow, not get switched around) but it has
only been in there about a week so I'm not seeing a huge harm.

I would not be happy to see the mask shrink, we might not be there yet,
we might not ever get there, but it was part of the future proofing of
the interface.

Would anyone like to send a patch? Tvrtko?

-Eric


  parent reply	other threads:[~2010-08-19 17:54 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-08-14 17:44 Andreas Schwab
2010-08-19 15:44 ` Tvrtko Ursulin
2010-08-19 16:07   ` Andreas Gruenbacher
2010-08-19 16:35     ` Tvrtko Ursulin
2010-08-19 17:53   ` Eric Paris [this message]
2010-08-20  9:02     ` Tvrtko Ursulin
2010-08-20  9:16       ` Andreas Schwab
2010-08-20  9:23         ` Tvrtko Ursulin
2010-08-20 13:13         ` Eric Paris
2010-08-20 13:27           ` Andreas Schwab
2010-08-20 15:19             ` Eric Paris
2010-08-20 17:47               ` Eric Paris

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=1282240426.21419.1716.camel@acb20005.ipt.aol.com \
    --to=eparis@redhat.com \
    --cc=agruen@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=schwab@linux-m68k.org \
    --cc=tvrtko.ursulin@sophos.com \
    /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