From: Andrew Morton <akpm@linux-foundation.org>
To: mm-commits@vger.kernel.org, akpm@linux-foundation.org,
yangyingliang@huawei.com, akpm@linux-foundation.org
Subject: [merged mm-nonmm-stable] fail_function-fix-wrong-use-of-fei_attr_remove.patch removed from -mm tree
Date: Sun, 11 Sep 2022 21:56:55 -0700 [thread overview]
Message-ID: <20220912045656.92ADDC433D6@smtp.kernel.org> (raw)
The quilt patch titled
Subject: fail_function: fix wrong use of fei_attr_remove()
has been removed from the -mm tree. Its filename was
fail_function-fix-wrong-use-of-fei_attr_remove.patch
This patch was dropped because it was merged into the mm-nonmm-stable branch
of git://git.kernel.org/pub/scm/linux/kernel/git/akpm/mm
------------------------------------------------------
From: Yang Yingliang <yangyingliang@huawei.com>
Subject: fail_function: fix wrong use of fei_attr_remove()
Date: Fri, 26 Aug 2022 15:33:37 +0800
If register_kprobe() fails, the new attr is not added to the list yet, so
it should call fei_attr_free() intstead.
Link: https://lkml.kernel.org/r/20220826073337.2085798-3-yangyingliang@huawei.com
Fixes: 4b1a29a7f542 ("error-injection: Support fault injection framework")
Signed-off-by: Yang Yingliang <yangyingliang@huawei.com>
Reviewed-by: Andrew Morton <akpm@linux-foundation.org>
Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
---
kernel/fail_function.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
--- a/kernel/fail_function.c~fail_function-fix-wrong-use-of-fei_attr_remove
+++ a/kernel/fail_function.c
@@ -295,7 +295,7 @@ static ssize_t fei_write(struct file *fi
ret = register_kprobe(&attr->kp);
if (ret) {
- fei_attr_remove(attr);
+ fei_attr_free(attr);
goto out;
}
fei_debugfs_add_attr(attr);
_
Patches currently in -mm which might be from yangyingliang@huawei.com are
reply other threads:[~2022-09-12 4:58 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20220912045656.92ADDC433D6@smtp.kernel.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mm-commits@vger.kernel.org \
--cc=yangyingliang@huawei.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 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.