bpf.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: KP Singh <kpsingh@kernel.org>
To: Song Liu <songliubraving@fb.com>
Cc: bpf <bpf@vger.kernel.org>, Networking <netdev@vger.kernel.org>,
	linux-mm@kvack.org, Alexei Starovoitov <ast@kernel.org>,
	Daniel Borkmann <daniel@iogearbox.net>,
	Andrii Nakryiko <andrii@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	Kernel Team <kernel-team@fb.com>,
	Andrew Morton <akpm@linux-foundation.org>,
	Yonghong Song <yhs@fb.com>
Subject: Re: [PATCH v3 bpf-next 2/4] bpf: allow bpf_d_path in sleepable bpf_iter program
Date: Fri, 8 Jan 2021 22:54:57 +0100	[thread overview]
Message-ID: <CACYkzJ4pvmMLx9NG3c3PHiU_nyYZZDuFkTC48GDezPA3onJZJQ@mail.gmail.com> (raw)
In-Reply-To: <20210107041801.2003241-3-songliubraving@fb.com>

On Thu, Jan 7, 2021 at 5:23 AM Song Liu <songliubraving@fb.com> wrote:
>
> task_file and task_vma iter programs have access to file->f_path. Enable
> bpf_d_path to print paths of these file.
>
> bpf_iter programs are generally called in sleepable context. However, it
> is still necessary to diffientiate sleepable and non-sleepable bpf_iter
> programs: sleepable programs have access to bpf_d_path; non-sleepable
> programs have access to bpf_spin_lock.
>
> Acked-by: Yonghong Song <yhs@fb.com>
> Signed-off-by: Song Liu <songliubraving@fb.com>

Acked-by: KP Singh <kpsingh@kernel.org>

      parent reply	other threads:[~2021-01-08 21:56 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-07  4:17 [PATCH v3 bpf-next 0/4] introduce bpf_iter for task_vma Song Liu
2021-01-07  4:17 ` [PATCH v3 bpf-next 1/4] bpf: introduce task_vma bpf_iter Song Liu
2021-01-12 18:43   ` Yonghong Song
2021-01-07  4:18 ` [PATCH v3 bpf-next 4/4] selftests/bpf: add test for bpf_iter_task_vma Song Liu
     [not found] ` <20210107041801.2003241-3-songliubraving@fb.com>
2021-01-08 21:54   ` KP Singh [this message]

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=CACYkzJ4pvmMLx9NG3c3PHiU_nyYZZDuFkTC48GDezPA3onJZJQ@mail.gmail.com \
    --to=kpsingh@kernel.org \
    --cc=akpm@linux-foundation.org \
    --cc=andrii@kernel.org \
    --cc=ast@kernel.org \
    --cc=bpf@vger.kernel.org \
    --cc=daniel@iogearbox.net \
    --cc=john.fastabend@gmail.com \
    --cc=kernel-team@fb.com \
    --cc=linux-mm@kvack.org \
    --cc=netdev@vger.kernel.org \
    --cc=songliubraving@fb.com \
    --cc=yhs@fb.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;
as well as URLs for NNTP newsgroup(s).