* [PATCH v2] bdi: show error log when fail to create bdi debugfs entry
@ 2018-01-10 16:36 weiping zhang
2018-01-19 17:36 ` weiping zhang
0 siblings, 1 reply; 4+ messages in thread
From: weiping zhang @ 2018-01-10 16:36 UTC (permalink / raw)
To: axboe, jack, Bart.VanAssche; +Cc: linux-block
bdi debugfs dir/file may create fail, add error log here.
Signed-off-by: weiping zhang <zhangweiping@didichuxing.com>
---
V1->V2:
fix indentation and make log message more clear
mm/backing-dev.c | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
diff --git a/mm/backing-dev.c b/mm/backing-dev.c
index b5f940c..0a49665 100644
--- a/mm/backing-dev.c
+++ b/mm/backing-dev.c
@@ -885,7 +885,9 @@ int bdi_register_va(struct backing_dev_info *bdi, const char *fmt, va_list args)
cgwb_bdi_register(bdi);
bdi->dev = dev;
- bdi_debug_register(bdi, dev_name(dev));
+ if (bdi_debug_register(bdi, dev_name(dev)))
+ pr_warn("blkdev %s: creation of bdi debugfs entries failed.\n",
+ dev_name(dev));
set_bit(WB_registered, &bdi->wb.state);
spin_lock_bh(&bdi_lock);
--
2.9.4
^ permalink raw reply related [flat|nested] 4+ messages in thread
* Re: [PATCH v2] bdi: show error log when fail to create bdi debugfs entry
2018-01-10 16:36 [PATCH v2] bdi: show error log when fail to create bdi debugfs entry weiping zhang
@ 2018-01-19 17:36 ` weiping zhang
2018-01-19 19:54 ` Jens Axboe
0 siblings, 1 reply; 4+ messages in thread
From: weiping zhang @ 2018-01-19 17:36 UTC (permalink / raw)
To: Jens Axboe, Jan Kara, Bart Van Assche, linux-block
2018-01-11 0:36 GMT+08:00 weiping zhang <zhangweiping@didichuxing.com>:
> bdi debugfs dir/file may create fail, add error log here.
>
> Signed-off-by: weiping zhang <zhangweiping@didichuxing.com>
> ---
> V1->V2:
> fix indentation and make log message more clear
>
> mm/backing-dev.c | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
>
> diff --git a/mm/backing-dev.c b/mm/backing-dev.c
> index b5f940c..0a49665 100644
> --- a/mm/backing-dev.c
> +++ b/mm/backing-dev.c
> @@ -885,7 +885,9 @@ int bdi_register_va(struct backing_dev_info *bdi, const char *fmt, va_list args)
> cgwb_bdi_register(bdi);
> bdi->dev = dev;
>
> - bdi_debug_register(bdi, dev_name(dev));
> + if (bdi_debug_register(bdi, dev_name(dev)))
> + pr_warn("blkdev %s: creation of bdi debugfs entries failed.\n",
> + dev_name(dev));
> set_bit(WB_registered, &bdi->wb.state);
>
> spin_lock_bh(&bdi_lock);
> --
Hi Jens,
madam has no permission to create debuts entry if SELINUX is enable at
Fedora and Centos,
and we have revert 6d0e4827b72 Revert "bdi: add error handle for
bdi_debug_register", that is to say
bdi debugfs is not the key component of block device, this patch just
add warning log.
Thanks
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v2] bdi: show error log when fail to create bdi debugfs entry
2018-01-19 17:36 ` weiping zhang
@ 2018-01-19 19:54 ` Jens Axboe
2018-01-20 0:09 ` weiping zhang
0 siblings, 1 reply; 4+ messages in thread
From: Jens Axboe @ 2018-01-19 19:54 UTC (permalink / raw)
To: weiping zhang, Jan Kara, Bart Van Assche, linux-block
On 1/19/18 10:36 AM, weiping zhang wrote:
> 2018-01-11 0:36 GMT+08:00 weiping zhang <zhangweiping@didichuxing.com>:
>> bdi debugfs dir/file may create fail, add error log here.
>>
>> Signed-off-by: weiping zhang <zhangweiping@didichuxing.com>
>> ---
>> V1->V2:
>> fix indentation and make log message more clear
>>
>> mm/backing-dev.c | 4 +++-
>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>
>> diff --git a/mm/backing-dev.c b/mm/backing-dev.c
>> index b5f940c..0a49665 100644
>> --- a/mm/backing-dev.c
>> +++ b/mm/backing-dev.c
>> @@ -885,7 +885,9 @@ int bdi_register_va(struct backing_dev_info *bdi, const char *fmt, va_list args)
>> cgwb_bdi_register(bdi);
>> bdi->dev = dev;
>>
>> - bdi_debug_register(bdi, dev_name(dev));
>> + if (bdi_debug_register(bdi, dev_name(dev)))
>> + pr_warn("blkdev %s: creation of bdi debugfs entries failed.\n",
>> + dev_name(dev));
>> set_bit(WB_registered, &bdi->wb.state);
>>
>> spin_lock_bh(&bdi_lock);
>> --
>
> Hi Jens,
>
> madam has no permission to create debuts entry if SELINUX is enable at
> Fedora and Centos,
> and we have revert 6d0e4827b72 Revert "bdi: add error handle for
> bdi_debug_register", that is to say
> bdi debugfs is not the key component of block device, this patch just
> add warning log.
Have we fixed the case where we know it will trigger?
--
Jens Axboe
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: [PATCH v2] bdi: show error log when fail to create bdi debugfs entry
2018-01-19 19:54 ` Jens Axboe
@ 2018-01-20 0:09 ` weiping zhang
0 siblings, 0 replies; 4+ messages in thread
From: weiping zhang @ 2018-01-20 0:09 UTC (permalink / raw)
To: Jens Axboe; +Cc: Jan Kara, Bart Van Assche, linux-block
2018-01-20 3:54 GMT+08:00 Jens Axboe <axboe@kernel.dk>:
> On 1/19/18 10:36 AM, weiping zhang wrote:
>> 2018-01-11 0:36 GMT+08:00 weiping zhang <zhangweiping@didichuxing.com>:
>>> bdi debugfs dir/file may create fail, add error log here.
>>>
>>> Signed-off-by: weiping zhang <zhangweiping@didichuxing.com>
>>> ---
>>> V1->V2:
>>> fix indentation and make log message more clear
>>>
>>> mm/backing-dev.c | 4 +++-
>>> 1 file changed, 3 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/mm/backing-dev.c b/mm/backing-dev.c
>>> index b5f940c..0a49665 100644
>>> --- a/mm/backing-dev.c
>>> +++ b/mm/backing-dev.c
>>> @@ -885,7 +885,9 @@ int bdi_register_va(struct backing_dev_info *bdi, const char *fmt, va_list args)
>>> cgwb_bdi_register(bdi);
>>> bdi->dev = dev;
>>>
>>> - bdi_debug_register(bdi, dev_name(dev));
>>> + if (bdi_debug_register(bdi, dev_name(dev)))
>>> + pr_warn("blkdev %s: creation of bdi debugfs entries failed.\n",
>>> + dev_name(dev));
>>> set_bit(WB_registered, &bdi->wb.state);
>>>
>>> spin_lock_bh(&bdi_lock);
>>> --
>>
>> Hi Jens,
>>
>> madam has no permission to create debuts entry if SELINUX is enable at
>> Fedora and Centos,
>> and we have revert 6d0e4827b72 Revert "bdi: add error handle for
>> bdi_debug_register", that is to say
>> bdi debugfs is not the key component of block device, this patch just
>> add warning log.
>
> Have we fixed the case where we know it will trigger?
The reason is that mdadm has no permission to create dir/file under
/sys/kernel/debug/
, I think we can solve it in two possible ways.
1.Add proper SELINUX policy to allow mdadm create
/sys/kernel/debug/bdi/xxx, but not
every user add this allowance, so kernel show a warning for this case.
2.Split mdadm into 2 part, Firstly, user proccess mdadm trigger a
kwork and wait a event
done, secondly kwork will create gendisk)and then wake up event. But
it is more likely a
hack, and it may break SELINUX mechanism, so I give up this way.
https://marc.info/?l=linux-mm&m=151456540928231&w=2
> --
> Jens Axboe
>
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2018-01-20 0:09 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-01-10 16:36 [PATCH v2] bdi: show error log when fail to create bdi debugfs entry weiping zhang
2018-01-19 17:36 ` weiping zhang
2018-01-19 19:54 ` Jens Axboe
2018-01-20 0:09 ` weiping zhang
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).