mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: David Laight <David.Laight@ACULAB.COM>
To: 'Mark Rutland' <mark.rutland@arm.com>
Cc: 'Szabolcs Nagy' <szabolcs.nagy@arm.com>,
	Theodore Ts'o <tytso@mit.edu>,
	"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-arm-kernel@lists.infradead.org" 
	<linux-arm-kernel@lists.infradead.org>
Subject: RE: linux interprets an fcntl int arg as long
Date: Tue, 1 Nov 2022 13:29:41 +0000	[thread overview]
Message-ID: <267402c9e66a4cac91a2e1df749dea6a@AcuMS.aculab.com> (raw)
In-Reply-To: <Y2EbR6YnQcgK4B8T@FVFF77S0Q05N>

From: Mark Rutland
> Sent: 01 November 2022 13:13
> 
> On Tue, Nov 01, 2022 at 12:19:51PM +0000, David Laight wrote:
> > From: 'Szabolcs Nagy' <szabolcs.nagy@arm.com>
> > > Sent: 01 November 2022 11:45
> > >
> > > The 11/01/2022 10:02, David Laight wrote:
> > > > From: Szabolcs Nagy
> 
> > > kernel code:
> > > ------------
> > > SYSCALL_DEFINE3(fcntl, unsigned int, fd, unsigned int, cmd, unsigned long, arg)
> > > {
> >
> > That is just a wrapper and calls do_fcntl().
> > which needs changing to be add:
> > 	arg &= ~0U;
> > before the switch(cmd) {
> 
> Just to check, do you mean the switch in do_fcntl(), or the switch within memfd_fcntl() ?
> 
> The former handles other APIs which do expect arg to be a long (e.g.
> F_SET_RW_HINT and F_GET_RW_HINT expect it to hold a full 64-bit pointer), so
> that'd break things.

The assignment to argv is earlier.

	David

-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)


  reply	other threads:[~2022-11-01 13:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-31 12:44 Szabolcs Nagy
2022-11-01  1:46 ` Theodore Ts'o
2022-11-01  9:11   ` Szabolcs Nagy
2022-11-01 10:02     ` David Laight
2022-11-01 11:44       ` 'Szabolcs Nagy'
2022-11-01 12:19         ` David Laight
2022-11-01 12:49           ` 'Szabolcs Nagy'
2022-11-01 13:12           ` Mark Rutland
2022-11-01 13:29             ` David Laight [this message]
2022-11-01 13:35               ` David Laight

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=267402c9e66a4cac91a2e1df749dea6a@AcuMS.aculab.com \
    --to=david.laight@aculab.com \
    --cc=linux-api@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=szabolcs.nagy@arm.com \
    --cc=tytso@mit.edu \
    /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