> On 10/06/2014 02:36 PM, Michal Nazarewicz wrote:
>> However, all the ep# files will still exist on the filesystem. This may
>> be a bit confusing and error-prone, no?
On Mon, Oct 06 2014, Robert Baldyga <r.bald...@samsung.com> wrote:
> Shouldn't be error-prone, because opening them will fail with -ENODEV,
> but indeed it can be confusing. I will try to do something about that
I could imagine someone will write shell script like so:
ffs_active() {
test -d "$1" || return 1
set -- "$1"/ep*
test $# -gt 1
}
if ffs_active /dev/foo-ffs; then
# …
fi
With such a script, non-functional ep# files in the functionfs mount
point, could lead to some errors in user-space. I'm not saying that
this should block on any kind of changes to the way the filesystem works
when the function is inactive, but if possible, w/o a lot of additional
code, I'd rather if all the files disappeared in a zombie state.
--
Best regards, _ _
.o. | Liege of Serenely Enlightened Majesty of o' \,=./ `o
..o | Computer Science, Michał “mina86” Nazarewicz (o o)
ooo +--<m...@google.com>--<xmpp:min...@jabber.org>--ooO--(_)--Ooo--
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
