https://jira.whamcloud.com This file is an XML representation of an issue en-us 9.4.14 940014 05-12-2023 https://jira.whamcloud.com/browse/LU-5365 Lustre <p>When striping information is set for a file, the kernel will accept the name of an OST pool which does not exist. The lfs utility validates the pool name in user space, but this can be bypassed by using the ioctl() or fsetxattr() interfaces directly. See attached program.</p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>$ bass6@t222 &gt; gcc -I lustre/include -I libcfs/include pool_test.c lustre/utils/liblustreapi.a $ bass6@t222 &gt; sudo ./a.out /mnt/lustre/`mktemp -u XXXX` /mnt/lustre/`mktemp -u XXXX` asdf a.out: poolname 'asdf' accepted via ioctl() for file /mnt/lustre/uchD a.out: poolname 'asdf' accepted via fsetxattr() for file /mnt/lustre/Ba5t </pre> </div></div> LU-5365

invalid pool name accepted when setting stripe information

Bug Minor In Progress Unresolved Jian Yu Ned Bass Thu, 17 Jul 2014 21:50:54 +0000 Tue, 7 Jun 2016 15:38:05 +0000 Lustre 2.6.0 0 6 <p>Yu, Jian</p> <p>Could you please assist with this issue?</p> <p>Thanks</p> <p>Peter</p> <p>The current implementation on the MDS is that if a pool name doesn't exist, the file will be created in the default pool. This is to avoid problems creating files if e.g. a default striping is set on a directory with a specific pool but the pool is later removed. Rather than making the userspace validation more robust (which adds overhead and can always be defeated), it would be better to handle this differently on the MDS and return an error (e.g. <tt>-ENXIO</tt> or whatever) if the pool does not exist.</p> <p>Patch for master branch: <a href="http://review.whamcloud.com/11226" class="external-link" target="_blank" rel="nofollow noopener">http://review.whamcloud.com/11226</a></p> Development End date Fri, 25 Jul 2014 21:50:54 +0000 Rank 1|hzwrpr: Rank (Obsolete) 14962 Severity Start date Thu, 17 Jul 2014 21:50:54 +0000