On Thu, 2014-04-17 at 15:40 -0700, Andy Grover wrote: > On 04/17/2014 01:41 PM, Nicholas A. Bellinger wrote: > > Hi Slava, > > > > Apologies for the delayed response, just catching up on list emails from > > the last weeks.. > > > > On Wed, 2014-04-09 at 11:34 +0300, Slava Shwartsman wrote: > >> Thank you Thomas, > >> I see that if configure my target with: > >> generate_node_acls=1 > >> In order to allow any initiator to connect to my target, I don't have > >> the acl directory at all - I can't see the connected initiators. > >> Any suggestions? > >> > > > > Unfortunately, there is currently no way to see what non explicitly > > ACL'ed initiators are connected to an endpoint configured in demo-mode > > with generate_node_acls=1. > > > > This is primarily due to two limitations in configfs: > > > > - The creation of configfs groups must be driven by userspace, and > > - the output of an individual configfs attribute is limited to > > PAGE_SIZE (4k on x86_64) > > > > So really, the latter will need to be addressed before we can expose an > > attribute that lists all active sessions, and not be limited to only 4K > > worth of text output. > > [adding configfs maintainer] > > Joel, what do you think? Is >PAGE_SIZE returned from configfs a > capability it might gain, or should we be looking for other ways to > expose this info? > AFAIK, this is not a specific to configfs itself. sysfs also suffers from the same PAGE_SIZE limitation as well. Really what both need is something similar to proc -> fs/seq_file.c, that allows for arbitrarily sized output to be read from individual attributes. --nab -- To unsubscribe from this list: send the line "unsubscribe target-devel" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
