From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751484AbdJEMHe (ORCPT ); Thu, 5 Oct 2017 08:07:34 -0400 Received: from mail-qt0-f194.google.com ([209.85.216.194]:52123 "EHLO mail-qt0-f194.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751239AbdJEMHd (ORCPT ); Thu, 5 Oct 2017 08:07:33 -0400 X-Google-Smtp-Source: AOwi7QCRYsjIipe5sChnvEPk2A2+3dnwna1JLWxABqxTuxaX3X6yAw56qf88c8MFcwrOKospKEL64/G8QPBFJh5m0gU= MIME-Version: 1.0 From: Alexey Dobriyan Date: Thu, 5 Oct 2017 14:07:31 +0200 Message-ID: Subject: Re: [PATCH] vfs: hard-ban creating files with control characters in the name To: Adam Borowski Cc: linux-kernel@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > Anything with bytes 1-31,127 will get -EACCES. You're making a mistake of catering to Unix shells which are pure garbage as programming languages instead of fixing them or switching to saner alternatives and then "fixing" kernel to sort-of workaround Unix shells deficiencies. Formally, you patch will break every program which creates git-style files with filenames only fixing up for \0 and '/'. Now such program should account for low ASCII as well.