Arnd,

On Tue, 20 Jun 2006, Arnd Bergmann wrote:
> 
> Alternatively, it might be possible to stuff i_private into the same
> union as i_pipe, i_cdev and i_bdev. The rationale here being that
> a file system implementing different file types already is complex
> enough that you would normally want your own alloc_inode for a
> derived struct. The simple file systems OTOH normally only support
> regular files, and sometimes directories.

Placing i_private and i_pipe in the same union will break FIFOs.

Also, i_pipe should not be combined with i_cdev and i_bdev.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/