From: "Lukas Bulwahn" <lukas.bulwahn@gmail.com>
To: linux-safety@lists.elisa.tech
Cc: development-process@lists.elisa.tech,
Lukas Bulwahn <lukas.bulwahn@gmail.com>
Subject: [PATCH] mm: vmscan: provide a change to the development-process group
Date: Thu, 17 Sep 2020 10:44:09 +0200 [thread overview]
Message-ID: <20200917084409.26992-1-lukas.bulwahn@gmail.com> (raw)
I think this change is needed for safety, whatever that might mean to you.
I am unqualified to really make a change here, as I have no clue what this
code does, nor what my change does, but sure, the testing and verification
reference process can now point out the required next steps in the
reference process to test this code and code change.
Good luck :)
Not intended for distribution to the general kernel mailing lists.
Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
---
I would like to submit such a patch, what do I need to do according to
the expected testing and verification recommendations for safety-related
systems?
Please help me. What do I need to compile, what test do I need to run,
which verification tool do I need to employ for this change?
Or even more basic: where would I even find that information?
mm/vmscan.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/mm/vmscan.c b/mm/vmscan.c
index 980155e257bf..aef8060efa8f 100644
--- a/mm/vmscan.c
+++ b/mm/vmscan.c
@@ -3893,7 +3893,7 @@ static int kswapd(void *p)
highest_zoneidx);
/* Read the new order and highest_zoneidx */
- alloc_order = reclaim_order = READ_ONCE(pgdat->kswapd_order);
+ alloc_order = READ_ONCE(pgdat->kswapd_order);
highest_zoneidx = kswapd_highest_zoneidx(pgdat,
highest_zoneidx);
WRITE_ONCE(pgdat->kswapd_order, 0);
--
2.17.1
next reply other threads:[~2020-09-17 8:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-17 8:44 Lukas Bulwahn [this message]
2020-09-17 12:59 ` [ELISA Development Process WG] [PATCH] mm: vmscan: provide a change to the development-process group Paoloni, Gabriele
2020-09-17 15:44 ` [linux-safety] " Lukas Bulwahn
2020-09-17 16:23 ` Paoloni, Gabriele
2020-09-17 16:28 ` Lukas Bulwahn
2020-09-17 15:14 ` [linux-safety] " Sudip Mukherjee
2020-09-17 15:29 ` Lukas Bulwahn
2020-09-17 15:47 ` [ELISA Development Process WG] " Sudip Mukherjee
2020-09-17 16:02 ` Lukas Bulwahn
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=20200917084409.26992-1-lukas.bulwahn@gmail.com \
--to=lukas.bulwahn@gmail.com \
--cc=development-process@lists.elisa.tech \
--cc=linux-safety@lists.elisa.tech \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).