Skip to contentSkip to conversation

Patch "ppp: mppe: Revert "ppp: mppe: Add softdep to arc4"" has been added to the 4.4-stable tree

DISCUSSION Eric Biggers 2 participants 3 messages May 24, 2020 – May 26, 2020 1 message not in the archive Stable branch

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

#1 lore raw
Quoted 10 lines · Sasha Levin

This is a note to let you know that I've just added the patch titled

ppp: mppe: Revert "ppp: mppe: Add softdep to arc4"

to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
ppp-mppe-revert-ppp-mppe-add-softdep-to-arc4.patch
and it can be found in the queue-4.4 subdirectory.

I already explained last time that this shouldn't be backported:
https://lore.kernel.org/stable/[email protected]/

The commit message explains it too.

Is there something I could have done last time around to properly prevent this from being backported, or do I have to continue to be ready to respond to these emails which can come at arbitrary times forever?

Quoted 3 lines

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

Hard for "anyone else" to object to it when you didn't Cc any real mailing lists (stable-commits doesn't count) and just sent this to me. Lucky I saw this.

- Eric

maintainer
#2 lore raw
Quoted 12 lines · Eric Biggers
Quoted 10 lines · Sasha Levin

This is a note to let you know that I've just added the patch titled

ppp: mppe: Revert "ppp: mppe: Add softdep to arc4"

to the 4.4-stable tree which can be found at:
http://www.kernel.org/git/?p=linux/kernel/git/stable/stable-queue.git;a=summary

The filename of the patch is:
ppp-mppe-revert-ppp-mppe-add-softdep-to-arc4.patch
and it can be found in the queue-4.4 subdirectory.

Quoted 8 lines

I already explained last time that this shouldn't be backported:
https://lore.kernel.org/stable/[email protected]/

The commit message explains it too.

Is there something I could have done last time around to properly prevent this from being backported, or do I have to continue to be ready to respond to these emails which can come at arbitrary times forever?

Appologies, I had to revert back to (older) backups for some of my data and sadly forgot it can cause this type of issues. I'll drop the patch.

Quoted 5 lines
Quoted 2 lines

If you, or anyone else, feels it should not be added to the stable tree, please let <[email protected]> know about it.

Hard for "anyone else" to object to it when you didn't Cc any real mailing lists (stable-commits doesn't count) and just sent this to me. Lucky I saw this.

This is just the "added to the queue" mail, you would see another mail when this release goes to -rc1. No reason for too much spam...

Signature · 2 lines
Thanks,
Sasha
#3 lore raw
Quoted 7 lines · Sasha Levin
Quoted 3 lines

Hard for "anyone else" to object to it when you didn't Cc any real mailing lists (stable-commits doesn't count) and just sent this to me. Lucky I saw this.

This is just the "added to the queue" mail, you would see another mail when this release goes to -rc1. No reason for too much spam...

So that second email would have gone to the real mailing lists that would need to review this patch (linux-crypto and netdev)? I don't think that's what happens, hence my concern...

- Eric