Thanks Ted, Casey and Al Viro. I am sorry for the inconvenience. I tried to follow the instructions listed under https://lore.kernel.org/lkml/20210330205750.428816-1-keescook@xxxxxxxxxxxx/ using git-send-email Thought that will reply to the original thread with the original subject . Let me know what I can do to correct this to avoid confusion. - Roy On Thu, Apr 1, 2021 at 1:13 PM Theodore Ts'o <tytso@xxxxxxx> wrote: > > On Thu, Apr 01, 2021 at 07:48:30PM +0000, Al Viro wrote: > > On Thu, Apr 01, 2021 at 12:17:44PM -0700, Roy Yang wrote: > > > Both Android and Chrome OS really want this feature; For Container-Optimized OS, we have customers > > > interested in the defense too. > > > > > > Thank you very much. > > > > > > Change-Id: I1eb1b726007aa8f9c374b934cc1c690fb4924aa3 > > > > You forgot to tell what patch you are refering to. Your > > Change-Id (whatever the hell that is) doesn't help at all. Don't > > assume that keys in your internal database make sense for the > > rest of the world, especially when they appear to contain a hash > > of something... > > The Change-Id fails to have any direct search hits at lore.kernel.org. > However, it turn up Roy's original patch, and clicking on the > message-Id in the "In-Reply-Field", it apperas Roy was replying to > this message: > > https://lore.kernel.org/lkml/20210330205750.428816-1-keescook@xxxxxxxxxxxx/ > > which is the head of this patch series: > > Subject: [PATCH v8 0/6] Optionally randomize kernel stack offset each syscall > > That being said, it would have been better if the original subject > line had been preserved, and it's yet another example of how the > lore.kernel.org URL is infinitely better than the Change-Id. :-) > > - Ted
