Skip to contentSkip to conversation

syscalls/shmat03: Remove CVE tag

PATCH New Cyril Hrubis 2 participants 4 messages Nov 21, 2019 – Dec 9, 2019

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 syscalls/shmat03: Remove CVE tag

The CVE was proved to be bogus so as far as I can tell we shouldn't list it in tags.

---
 testcases/kernel/syscalls/ipc/shmat/shmat03.c | 1 -
 1 file changed, 1 deletion(-)
testcases/kernel/syscalls/ipc/shmat/shmat03.c +0 -1
index 8a0b89bd5..dfa427a56 100644
@@ -101,7 +101,6 @@ static struct tst_test test = {
 	.cleanup = cleanup,
 	.test_all = run,
 	.tags = (const struct tst_tag[]) {
-		{"CVE", "2017-5669"},
 		{"linux-git", "95e91b831f87"},
 		{"linux-git", "a73ab244f0da"},
 		{"linux-git", "8f89c007b6de"},
Signature · 1 line
2.21.0
#1 lore raw

PATCH 1/1 syscalls/shmat03: Remove CVE tag

Hi Cyril,

Quoted 2 lines

The CVE was proved to be bogus so as far as I can tell we shouldn't list it in tags.

ack (although a link claiming it bogus would be nice).

Kind regards,
Petr

#2 lore raw

PATCH 1/1 syscalls/shmat03: Remove CVE tag

Hi!

Quoted 3 lines
Quoted 2 lines

The CVE was proved to be bogus so as far as I can tell we shouldn't list it in tags.

ack (although a link claiming it bogus would be nice).

I've added added a commit hash of the commit that removed the test from runtest/cve to this commit message. It's nicely explained in the original commit so there is no need to copy the information over to the new commit. Thanks.

Signature · 2 lines
Cyril Hrubis
[email protected]
#3 lore raw

PATCH 1/1 syscalls/shmat03: Remove CVE tag

Hi Cyril,

Quoted 8 lines
Quoted 3 lines
Quoted 2 lines

The CVE was proved to be bogus so as far as I can tell we shouldn't list it in tags.

ack (although a link claiming it bogus would be nice).

I've added added a commit hash of the commit that removed the test from runtest/cve to this commit message. It's nicely explained in the original commit so there is no need to copy the information over to the new commit. Thanks.

Sure. Sorry, I didn't notice bogus explanation was already added in 2588dafd4651706ed7ae34ae3b744b0ee8cd6384.

Kind regards,
Petr