From: Seamus Connor <sconnor@purestorage.com>
To: Ming Lei <ming.lei@redhat.com>
Cc: Jens Axboe <axboe@kernel.dk>,
linux-block@vger.kernel.org,
Caleb Sander <csander@purestorage.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ublk: fix ublksrv pid handling for pid namespaces
Date: Mon, 12 Jan 2026 10:09:04 -0800 [thread overview]
Message-ID: <CAB5MrP4ZAe3Zw677eHBaMRsv9TugpEGpmMC_1v+Dm2GMo7CiNA@mail.gmail.com> (raw)
In-Reply-To: <aWSJRAEbC3SUuRk-@fedora>
> Can we fix it in the following way?
>
> + struct pid *pid = find_vpid(ublksrv_pid);
> +
> + if (!pid || pid_nr(pid) != ub->ublksrv_tgid)
> + return -EINVAL;
Sure that makes sense. Let me try that out.
> Also your patch has patch style issue, please check it before posting out
> by `./scripts/checkpatch.pl`. Or you may have to use `git send-email` to
> send patch file.
Sorry about that.
prev parent reply other threads:[~2026-01-12 18:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-11 0:00 Seamus Connor
2026-01-12 5:40 ` Ming Lei
2026-01-12 18:09 ` Seamus Connor [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=CAB5MrP4ZAe3Zw677eHBaMRsv9TugpEGpmMC_1v+Dm2GMo7CiNA@mail.gmail.com \
--to=sconnor@purestorage.com \
--cc=axboe@kernel.dk \
--cc=csander@purestorage.com \
--cc=linux-block@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.lei@redhat.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
all inboxes | Powered by JetHome®