On Wed 13-12-17 15:19:00, Kees Cook wrote: > On Wed, Dec 13, 2017 at 6:40 AM, Cyril Hrubis <chrubis@xxxxxxx> wrote: > > Hi! > >> You selected stupid name for a flag. Everyone and their dog agrees > >> with that. There's even consensus on better name (and everyone agrees > >> it is better than .._SAFE). Of course, we could have debate if it is > >> NOREPLACE or NOREMOVE or ... and that would be bikeshed. This was just > >> poor naming on your part. > > > > Well while everybody agrees that the name is so bad that basically > > anything else would be better, there does not seem to be consensus on > > which one to pick. I do understand that this frustrating and fruitless. > > Based on the earlier threads where I tried to end the bikeshedding, it > seemed like MAP_FIXED_NOREPLACE was the least bad option. > > > So what do we do now, roll a dice to choose new name? > > > > Or do we ask BFDL[1] to choose the name? > > I'd like to hear feedback from Michael Kerrisk, as he's had to deal > with these kinds of choices in the past. I'm fine to ask Linus too. I > just want to get past the name since the feature is quite valuable. > > And if Michal doesn't want to touch this patch any more, I'm happy to > do the search/replace/resend. :P I think Andrew can do the s@MAP_FIXED_SAFE@MAP_$FOO@ when adding the patch to the mmotm tree. The reason why I refuse to repost is that a) functionality doesn't really need a further rework (at least not based on the review feedback) and b) I do not really see any large consensus here. People claim to like this or that more but nobody (except of you Kees) was willing to put their name under their preference in a form of Acked-by. And that worries me, because generating "better" names sounds too easy to allow a forward progress. -- Michal Hocko SUSE Labs
