All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@lst.de>
To: shaopeijie@cestc.cn
Cc: kbusch@kernel.org, axboe@kernel.dk, hch@lst.de, sagi@grimberg.me,
	linux-nvme@lists.infradead.org, linux-kernel@vger.kernel.org,
	zhang.guanghui@cestc.cn, gechangzhong@cestc.cn
Subject: Re: [PATCH] nvme-tcp: fix selinux denied when calling sock_sendmsg
Date: Thu, 20 Mar 2025 08:25:17 +0100	[thread overview]
Message-ID: <20250320072517.GA14672@lst.de> (raw)
In-Reply-To: <20250320063523.2201926-1-shaopeijie@cestc.cn>

Looks good:

Reviewed-by: Christoph Hellwig <hch@lst.de>

Can you send a patch for the target side as well?



  reply	other threads:[~2025-03-20  7:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-20  6:35 [PATCH] nvme-tcp: fix selinux denied when calling sock_sendmsg shaopeijie
2025-03-20  7:25 ` Christoph Hellwig [this message]
     [not found]   ` <1382721899.82743.1742525374789.JavaMail.xmail@wm-2>
2025-03-21  5:05     ` Christoph Hellwig
2025-03-20 20:15 ` Keith Busch

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=20250320072517.GA14672@lst.de \
    --to=hch@lst.de \
    --cc=axboe@kernel.dk \
    --cc=gechangzhong@cestc.cn \
    --cc=kbusch@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-nvme@lists.infradead.org \
    --cc=sagi@grimberg.me \
    --cc=shaopeijie@cestc.cn \
    --cc=zhang.guanghui@cestc.cn \
    /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.