UBI: Can we handle -EINTR differently in erase/write path???

[Vinit Agnihotri]

I'll send the patch by tomorrow with handling for -EINTR in write also.

Thanks & Regards
Vinit.

On 7/17/07, Artem Bityutskiy <dedekind at infradead.org> wrote:
> On Fri, 2007-07-13 at 11:37 +0530, Vinit Agnihotri wrote:
> > Hi heres few code snip from erase_worker(); from wl.c
> > if (err != -EIO) {
> >         /*
> >          * If this is not %-EIO, we have no idea what to do. Scheduling
> >          * this physical eraseblock for erasure again would cause
> >          * errors again and again. Well, lets switch to RO mode.
> >          */
> >         ubi_ro_mode(ubi);
> >         return err;
> >     }
> > Suppose while erasure in progress & someone pressed "Ctrl+C" then UBI
> > straight way marks entire device as Read only & its really painful
> > because then you cant even delete that volume as UBI is read only.
> > Which I guess its not good way. If use cases are considered it is
> > highly likely that user can hit "Ctrl+c" , like he want to cancel
> > erase at that time or something like that. So we can handle -EINTR
> > differently by following way
>
> Please, feel free to ignore my silly question and just send the
> patch :-)
>
> --
> Best regards,
> Artem Bityutskiy (Битюцкий Артём)
>
>


-- 
I feel free now