lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <ef1481e8-c664-5f17-4a19-bb90daabc0b7@kernel.dk>
Date:   Mon, 8 Apr 2019 09:17:58 -0600
From:   Jens Axboe <axboe@...nel.dk>
To:     Paolo Valente <paolo.valente@...aro.org>,
        Johannes Thumshirn <jthumshirn@...e.de>
Cc:     linux-block <linux-block@...r.kernel.org>,
        linux-kernel <linux-kernel@...r.kernel.org>,
        Ulf Hansson <ulf.hansson@...aro.org>,
        Linus Walleij <linus.walleij@...aro.org>,
        Mark Brown <broonie@...nel.org>,
        'Paolo Valente' via bfq-iosched 
        <bfq-iosched@...glegroups.com>,
        Oleksandr Natalenko <oleksandr@...alenko.name>,
        Angelo Ruocco <angeloruocco90@...il.com>,
        lennart@...ttering.net, mkoutny@...e.cz
Subject: Re: [PATCH 1/1] block, bfq: delete "bfq" prefix from cgroup filenames

On 4/8/19 9:14 AM, Paolo Valente wrote:
> 
> 
>> Il giorno 8 apr 2019, alle ore 17:08, Johannes Thumshirn <jthumshirn@...e.de> ha scritto:
>>
>> On Mon, Apr 08, 2019 at 09:05:19AM -0600, Jens Axboe wrote:
>>> I did consider that, and that would be doable. But honestly, I'm having a
>>> hard time seeing what issue we are attempting to fix by doing this.
>>
>> Yeah, I guess the real fix would be to update the documentation and the
>> expectations user-space has. Including eventual re-write of some udev rules or
>> whatever is facing these files. But to me that sounds more like a systemd or
>> even distro thing than a kernel thing.
>>
> 
> Unfortunately the user-space people I have interacted with find crazy
> to have to change their software to call bfq.weight the weight of a
> group.  And are not willing to do it [1].

Then you need to educate them. Some of the issues were called out years
ago, at the time when we could have potentially renamed. A rename now
will solve nothing.

-- 
Jens Axboe

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ