Re: Dovetail/Evl confusion on my end

Philippe Gerum <[email protected]> writes:

> Philippe Gerum <[email protected]> writes:
>
>> Florian Bezdeka <[email protected]> writes:
>>
>>> Hi Philippe,
>>>
>>> I just recognized that you updated the source of my rebase branches
>>> meanwhile, so v7.0-dovetail-rebase (for dovetail) and next/v7.0-evl-
>>> rebase for evl.
>>>
>>> While syncing the missing pieces I noticed that commit 
>>> ad7e492ff2 ("/dev/{null, zero}: dovetail: drop deprecated .write handler ") 
>>> is part of v7.0-evl-rebase but is not part of v7.0-dovetail-rebase.
>>>
>>> Why is that? Any specific reason?
>>>
>>
>> I pushed this patch yesterday, and wanted to have some hindsight about
>> it for a couple of (testing) days of the evl tree. I believe it is
>> correct, but given the patched area, better safe than sorry. I plan to
>> merge it last on top of 7.0-dovetail.
>
> To elaborate a bit more, this patch only helps evl strictly speaking, by
> preventing stdout/err redirections through proxies to cause a kernel
> warning, which in fact reveals that some portion of the upstream code
> (namely the /null and /zero cdevs at least) are still using a deprecated
> file_operations handler, which the VFS complains about when using the
> kernel interface to write to them.

The feedback I received from internal users regarding this is
positive, no regression.

-- 
Philippe.