Re: netbsd32_{,u}int64 in sys/types.h for compat/sys/siginfo.h

2019-11-19 Thread Kamil Rytarowski
On 18.11.2019 13:08, Rin Okuyama wrote: > On 2019/11/18 20:15, Kamil Rytarowski wrote: >> I was thinking about something along these lines: >> >> http://netbsd.org/~kamil/patch-00196-siginfo_netbsd32_compat_uint64.txt >> >> In future some compat of i386 could use 8-byte alignment for 64-bit >> type

Re: adding linux syscall fallocate

2019-11-19 Thread Christoph Badura
On Mon, Nov 18, 2019 at 02:26:17PM -0800, Jason Thorpe wrote: > > On Nov 18, 2019, at 1:13 PM, Mouse wrote: > > All you need is a second magic block number. Block number zero is > > already reserved for holes. Making, say, block number 1, or -1, or > > some such, reserved to represent "block-of-

Re: adding linux syscall fallocate

2019-11-19 Thread Maciej
>You don't have to know where to write. Strictly speaking you only need to know >that the space is reserved. We do >have enough magic block numbers that could serve as a marker. E.g. anything up >to the end of the first super block >isn't allocatable. And there are enough spare fields in the fs,

Re: adding linux syscall fallocate

2019-11-19 Thread Edgar Fuß
> You don't have to know where to write. Strictly speaking you only need > to know that the space is reserved. Strictly speaking, yes. But callers of fallocate may expect that the space is not only available, mut more-or-less contiguous---as if zeroes had actually been written. I.e., when demult

Re: adding linux syscall fallocate

2019-11-19 Thread Mouse
>> You don't have to know where to write. Strictly speaking you only >> need to know that the space is reserved. Right. > One thing that I am missing here is: if you would keep info about reservatio$ You don't need to know history. You just need to know how many blocks are available to be newl