linux-kernel - Re: struct fanotify_event

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <1282240426.21419.1716.camel@acb20005.ipt.aol.com>
Date:	Thu, 19 Aug 2010 13:53:46 -0400
From:	Eric Paris <eparis@...hat.com>
To:	Tvrtko Ursulin <tvrtko.ursulin@...hos.com>
Cc:	Andreas Schwab <schwab@...ux-m68k.org>,
	Andreas Gruenbacher <agruen@...e.de>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: struct fanotify_event_metadata

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

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/