Hi - thanks for the update. Assuming the only thing you changed was
catching the errno (there's no changelog but I assume so and don't
want to take another close look),
Acked-by: Serge Hallyn
Let's apply and finally close this mysterious and aggravating (for some)
chapter! :)
thanks,
-serge
Hi again,
> Sorry I didn't reply earlier.
>
>> Thanks, sorry for the trouble. Looks good, with one exception - if
>> ioctl failed, then you may end up returning the wrong errno (from the
>> close syscall). With that fixed, please do apply.
>
> Oh, yes, nice catch. I've attached a fixed patch
Hi,
Sorry I didn't reply earlier.
> Thanks, sorry for the trouble. Looks good, with one exception - if
> ioctl failed, then you may end up returning the wrong errno (from the
> close syscall). With that fixed, please do apply.
Oh, yes, nice catch. I've attached a fixed patch.
Thanks!
Chris
On 12/04/2011 05:18 PM, Daniel Lezcano wrote:
> On 12/05/2011 12:11 AM, Serge Hallyn wrote:
>> On 12/04/2011 04:28 AM, Daniel Lezcano wrote:
>>> On 11/16/2011 05:49 PM, Christian Seiler wrote:
Hi,
I've run into the same problem as was discussed in BUG #3411497 [1]
and on
th
On 12/05/2011 12:11 AM, Serge Hallyn wrote:
> On 12/04/2011 04:28 AM, Daniel Lezcano wrote:
>> On 11/16/2011 05:49 PM, Christian Seiler wrote:
>>> Hi,
>>>
>>> I've run into the same problem as was discussed in BUG #3411497 [1]
>>> and on
>>> the users mailing list [2]. To solve this, I've decided t
On 12/04/2011 04:28 AM, Daniel Lezcano wrote:
> On 11/16/2011 05:49 PM, Christian Seiler wrote:
>> Hi,
>>
>> I've run into the same problem as was discussed in BUG #3411497 [1] and on
>> the users mailing list [2]. To solve this, I've decided to implement the
>> patch that was proposed on the maili
On 11/16/2011 05:49 PM, Christian Seiler wrote:
> Hi,
>
> I've run into the same problem as was discussed in BUG #3411497 [1] and on
> the users mailing list [2]. To solve this, I've decided to implement the
> patch that was proposed on the mailing list [3].
>
> The attached patch is against curren
Hi,
I've run into the same problem as was discussed in BUG #3411497 [1] and on
the users mailing list [2]. To solve this, I've decided to implement the
patch that was proposed on the mailing list [3].
The attached patch is against current trunk. Since trunk currently doesn't
compile for me, I tes
