output file cannot be in the UBIFS root directory check is not working quite well

[Ricard Wanderlof]

On Fri, 5 Oct 2012, kyak wrote:

> I observe the same problem with any other directory (namely, with my
> /home, which is not reabable).
>
> When one of the directories in "-d" hierarchy is not readable, 
> mkfs.ubifs will fail all the time, thinking that the output file is 
> located in UBIFS root directory.

I can agree with you that the error message looks wrong for this case, but 
what is the point of attempting to create a file system image from a 
directory tree which is not readable?

/Ricard

>
> On Wed, 3 Oct 2012, kyak wrote:
>
>> Hi,
>>
>> Consider the following sequence of commands:
>>
>> cd ~
>> mkdir -p /tmp/wtf/wtf1
>> chmod u-r /tmp/wtf
>> mkfs.ubifs -m 4096 -e 516096 -c 4095 -d /tmp/wtf/wtf1 -o mytest.img
>> Error: output file cannot be in the UBIFS root directory
>>
>> mytest.img is not inside /tmp/wtf/wtf1, but mkfs.ubifs fails because /tmp/wtf
>> is not readable.
>> It seems that implementation of in_path(..) in mkfs.ubifs.c is not quite
>> correct to handle this type of situations.
>>
>> If you are wondering, my /home is not readable, and this prevents me from
>> building any ubifs image inside of /home/user.
>>
>> Thanks in advance.
>>
>
> ______________________________________________________
> Linux MTD discussion mailing list
> http://lists.infradead.org/mailman/listinfo/linux-mtd/
>

-- 
Ricard Wolf Wanderlöf                           ricardw(at)axis.com
Axis Communications AB, Lund, Sweden            www.axis.com
Phone +46 46 272 2016                           Fax +46 46 13 61 30