> We've no reason to believe that there are broken SetVariable() implementations in the wild. If any ever crop up, we can deal with > them as and when. OK. I will make a patch disabling just get_next_variable(). I'm thinking that it is reasonable to set ops->get_next_variable to NULL in register_efivars(), instead of introducing a new global variable.... Seiji > -----Original Message----- > From: Matt Fleming [mailto:matt@xxxxxxxxxxxxxxxxx] > Sent: Tuesday, March 19, 2013 11:27 AM > To: Seiji Aguchi > Cc: Lingzhu Xiang; Andre Heider; linux-efi@xxxxxxxxxxxxxxx > Subject: Re: sysfs: cannot create duplicate filename > > On 03/19/2013 02:25 PM, Seiji Aguchi wrote: > > I see, you are concerned that a set_variable service may not work correctly. > > If so, the set_variable service should be disabled in addition to get_next_variable service. > > We've no reason to believe that there are broken SetVariable() implementations in the wild. If any ever crop up, we can deal with > them as and when. > > -- > Matt Fleming, Intel Open Source Technology Center ��.n��������+%������w��{.n�����{����* jg��� �����ݢj����G���� ���j:+v���w�m������w�������h�����٥
