All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Vorel <petr.vorel@gmail.com>
To: Heiko Thiery <heiko.thiery@gmail.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [PATCH iproute2-next v2] lib/fs: fix issue when {name,open}_to_handle_at() is not implemented
Date: Sun, 2 May 2021 13:16:12 +0200	[thread overview]
Message-ID: <YI6J/EBwxd0+p5Ux@pevik> (raw)
In-Reply-To: <CAEyMn7Z4cr1=WYde4uxwu2tjEgX2Lwwx3S+vmFP8EZVVMaWRjg@mail.gmail.com>

> Hi Petr,

> Am Fr., 30. Apr. 2021 um 21:29 Uhr schrieb Petr Vorel <petr.vorel@gmail.com>:

> > Hi,

> > > > +++ b/lib/fs.c
> > > > @@ -30,6 +30,27 @@
> > > >  /* if not already mounted cgroup2 is mounted here for iproute2's use */
> > > >  #define MNT_CGRP2_PATH  "/var/run/cgroup2"

> > > > +
> > > > +#ifndef defined HAVE_HANDLE_AT
> > > This is also wrong, it must be:
> > > #ifndef HAVE_HANDLE_AT

> > > > +struct file_handle {
> > > > +   unsigned handle_bytes;
> > > > +   int handle_type;
> > > > +   unsigned char f_handle[];
> > > > +};
> > > > +
> > > > +int name_to_handle_at(int dirfd, const char *pathname,
> > > > +   struct file_handle *handle, int *mount_id, int flags)
> > > > +{
> > > > +   return syscall(name_to_handle_at, 5, dirfd, pathname, handle,
> > > > +                  mount_id, flags);
> > > Also I overlooked bogus 5 parameter, why is here? Correct is:

> > >       return syscall(__NR_name_to_handle_at, dfd, pathname, handle,
> > >                          mount_id, flags);
> > Uh, one more typo on my side, sorry (dfd => dirfd):
> >         return syscall(__NR_name_to_handle_at, dirfd, pathname, handle,
> >                            mount_id, flags);


> Thanks for the review and finding the sloppiness. I really should test
> the changes before. Nevertheless, I will prepare a new version and
> test it this time.
I tested ss with changed I proposed and it looks like it's ok.
But I run ss on qemu without any daemon running => I'll retest your v3 once you
post it with some daemons running so that the code is really triggered.

Kind regards,
Petr

> BR,

  reply	other threads:[~2021-05-02 11:16 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-30  6:26 [PATCH iproute2-next v2] lib/fs: fix issue when {name,open}_to_handle_at() is not implemented Heiko Thiery
2021-04-30 18:43 ` Petr Vorel
2021-04-30 19:07 ` Petr Vorel
2021-04-30 19:29   ` Petr Vorel
2021-05-02  8:35     ` Heiko Thiery
2021-05-02 11:16       ` Petr Vorel [this message]
2021-05-01 15:03 ` David Ahern
2021-05-02  8:38   ` Heiko Thiery
2021-05-02 11:20     ` Petr Vorel
2021-05-02 13:07       ` David Ahern

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=YI6J/EBwxd0+p5Ux@pevik \
    --to=petr.vorel@gmail.com \
    --cc=heiko.thiery@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=stephen@networkplumber.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.