tech-kern archive
[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index][
Old Index]
Re: [PATCH] PUFFS backend allocation (round 3)
On 26 Oct 2014, at 17:55, Emmanuel Dreyfus <manu%netbsd.org@localhost> wrote:
> J. Hannken-Illjes <hannken%eis.cs.tu-bs.de@localhost> wrote:
>
>> What happens when libpuffs receives an unknown message (fallocate in
>> this case)?
>
> The filesystem using libpuffs tells the kernel what operations should be
> sent to userland when it calls puffs_init(). It can be done
> - by setting the list of wanted operation, in which case the kernel
> never sends an unknown message,
> - by requesting all operations to be sent to userland. In that case an
> unknown operation is handled in src/lib/libpuffs/dispatcher.c:dispatch()
> default:
> printf("inval op %d\n", preq->preq_optype);
> error = EINVAL;
> break;
Ok -- you don't need it here.
Since it was last incremented at Rev. 1.72 many messages got additional
fields so the version should be incremented independent of your change.
--
J. Hannken-Illjes - hannken%eis.cs.tu-bs.de@localhost - TU Braunschweig (Germany)
Home |
Main Index |
Thread Index |
Old Index