DMA Engine development
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: dmaengine@vger.kernel.org, Dave Jiang <dave.jiang@intel.com>
Cc: vinicius.gomes@intel.com, arjan@linux.intel.com, nathan.lynch@amd.com
Subject: Re: [PATCH v2] dmaengine: idxd: Fix allowing write() from different address spaces
Date: Thu, 24 Apr 2025 11:06:26 +0530	[thread overview]
Message-ID: <174547298664.315671.10538699041361455695.b4-ty@kernel.org> (raw)
In-Reply-To: <20250421170337.3008875-1-dave.jiang@intel.com>


On Mon, 21 Apr 2025 10:03:37 -0700, Dave Jiang wrote:
> Check if the process submitting the descriptor belongs to the same
> address space as the one that opened the file, reject otherwise.
> 
> 

Applied, thanks!

[1/1] dmaengine: idxd: Fix allowing write() from different address spaces
      commit: 8dfa57aabff625bf445548257f7711ef294cd30e

Best regards,
-- 
~Vinod



      reply	other threads:[~2025-04-24  5:36 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-21 17:03 [PATCH v2] dmaengine: idxd: Fix allowing write() from different address spaces Dave Jiang
2025-04-24  5:36 ` Vinod Koul [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=174547298664.315671.10538699041361455695.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --cc=arjan@linux.intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dmaengine@vger.kernel.org \
    --cc=nathan.lynch@amd.com \
    --cc=vinicius.gomes@intel.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