public inbox for ltp@lists.linux.it
 help / color / mirror / Atom feed
From: Avinesh Kumar <akumar@suse.de>
To: Martin Doucha <mdoucha@suse.cz>, Petr Vorel <pvorel@suse.cz>
Cc: ltp@lists.linux.it
Subject: Re: [LTP] [PATCH] setfsuid02: using -1 as invalid fsuid for setfsuid()
Date: Wed, 02 Nov 2022 13:10:06 +0530	[thread overview]
Message-ID: <20846440.eidTIuNkkK@localhost> (raw)
In-Reply-To: <Y2BAiPUPKS3gimLD@pevik>

Hi Petr, Martin,

Thank you for the discussion and fixing the patch for 16-bit.
I am making a note to always test 16-bit binaries also.

On Tuesday, November 1, 2022 3:09:20 AM IST Petr Vorel wrote:
> > On 31. 10. 22 15:56, Petr Vorel wrote:
> > > Ah, sure, I see current_uid is used for checking only. So what is your
> > > suggestion to fix the problem on 16-bit?
> 
> > I guess using UID_T (defined in the LTP compat headers) instead of uid_t is
> > the solution, then -1 will be cast to the correct bitsize.
> 
> Thank you, that worked.
> 
> Merged, with additional cast to long to keep compiler happy.
> 
> Kind regards,
> Petr
> 

Regards,
Avinesh



-- 
Mailing list info: https://lists.linux.it/listinfo/ltp

  reply	other threads:[~2022-11-02  7:40 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27 14:09 [LTP] [PATCH] setfsuid02: using -1 as invalid fsuid for setfsuid() Avinesh Kumar
2022-10-31 11:37 ` Petr Vorel
2022-10-31 13:36   ` Martin Doucha
2022-10-31 13:50     ` Petr Vorel
2022-10-31 14:00       ` Martin Doucha
2022-10-31 14:56         ` Petr Vorel
2022-10-31 17:23           ` Martin Doucha
2022-10-31 21:39             ` Petr Vorel
2022-11-02  7:40               ` Avinesh Kumar [this message]
2022-10-31 13:01 ` Richard Palethorpe
2022-10-31 21:40   ` Petr Vorel
2022-11-01  9:03     ` Richard Palethorpe
2022-11-02  7:52       ` Avinesh Kumar

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=20846440.eidTIuNkkK@localhost \
    --to=akumar@suse.de \
    --cc=ltp@lists.linux.it \
    --cc=mdoucha@suse.cz \
    --cc=pvorel@suse.cz \
    /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