linux-kernel - Re: [PATCHSET 0/5 v2] brd: partition fixes

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: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Wed, 27 Aug 2014 18:57:04 +0300
From:	Boaz Harrosh <boaz@...xistor.com>
To:	Dmitry Monakhov <dmonakhov@...nvz.org>, Jens Axboe <axboe@...com>,
	Matthew Wilcox <willy@...ux.intel.com>
CC:	Ross Zwisler <ross.zwisler@...ux.intel.com>,
	linux-kernel <linux-kernel@...r.kernel.org>,
	linux-fsdevel <linux-fsdevel@...r.kernel.org>
Subject: Re: [PATCHSET 0/5 v2] brd: partition fixes

On 08/27/2014 06:45 PM, Dmitry Monakhov wrote:
> On Wed, 27 Aug 2014 18:22:21 +0300, Boaz Harrosh <boaz@...xistor.com> wrote:
<>
>> [v2]
>> Based on Jens's linux-next [30e996a] incorporating the brd patch by Dmitry Monakhov.
>> Dmitry has introduced a new part_show parameter, this parameter is now
>> removed
>   In which commit or kernel-tree this parameter was removed?

I mean after this patchset, see patch
	[PATCH 4/5] brd: Fix all partitions BUGs

It will remove this param

>> and we always "part_show=1".
>> Scripts that did part_show=1 will work just the same but will display a
>> message in logs. This is harmless. (And scripts can be modified to
>> remove this parameter)
>   Which script are you talking about? Why you want use it?
> 

I meant that if any user-mode code was doing
	modprobe brd part_show=1
Then this "part_show=1" is now deprecated and can be removed

Though the part_show=1 has not yet been released in any kernel
and it is a very low chance that any one had a chance to
use it

Thanks
Boaz


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/