EcryptFS development
 help / color / mirror / Atom feed
From: Yichong Chen <chenyichong@uniontech.com>
To: Tyler Hicks <code@tyhicks.com>
Cc: Yichong Chen <chenyichong@uniontech.com>,
	Thorsten Blum <thorsten.blum@linux.dev>,
	Kees Cook <kees@kernel.org>,
	ecryptfs@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ecryptfs: release message context on send failure
Date: Wed,  1 Jul 2026 13:25:06 +0800	[thread overview]
Message-ID: <20260701052506.256345-1-chenyichong@uniontech.com> (raw)
In-Reply-To: <akSNYl2MglViekHR@yaupon>

Hi Tyler,

Yes, I agree. I rechecked the history and f66e883eb618 is where the
miscdev send path was introduced into ecryptfs_send_message_locked().
I'll send a v2 with the corrected Fixes tag.

Thanks for catching this.

Yichong

      reply	other threads:[~2026-07-01  5:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-27  9:01 [PATCH] ecryptfs: release message context on send failure Yichong Chen
2026-07-01  3:45 ` Tyler Hicks
2026-07-01  5:25   ` Yichong Chen [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=20260701052506.256345-1-chenyichong@uniontech.com \
    --to=chenyichong@uniontech.com \
    --cc=code@tyhicks.com \
    --cc=ecryptfs@vger.kernel.org \
    --cc=kees@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thorsten.blum@linux.dev \
    /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