On Tue, Dec 03, 2013 at 09:13:18AM +0100, Jan Danielsson wrote:
If you use objdump -d or nm -n or gdb or whatever to find the code
that's at 0x8031162f in your kernel, you'll probably get a
fairly good idea of what broke.
A lot of pf_state_* around there, so it looks like
On Tue, Dec 03, 2013 at 08:13:29AM +0100, Jan Danielsson wrote:
I'm running netbsd-6 (a month old or so) on a Soekris net6501
(NetBSD/amd64), and tonight I had an unexpected reboot.
/var/log/messages contains:
Dec 3 03:15:46 aria syslogd[188]: restart
Dec 3 03:15:46 aria /netbsd:
On Sat, Nov 23, 2013 at 12:59:04AM -0500, Mouse wrote:
Note that the bog-standard (struct sockaddr *) cast that one needs
and conventionally uses to call bind(2), connect(2), accept(2), and
similar is, strictly speaking, illegal.
I don't think so. The aliasing rules don't say
On Thu, Nov 21, 2013 at 11:02:24PM -0500, Ken Hornstein wrote:
Modulo some administrative details, it's just no object in memory may
be accessed using more than one type.
Ok ... I _think_ I see it. But doesn't that mean that like 90% of the casts
used by C programmers are totally
On Thu, Nov 21, 2013 at 08:55:44AM -0500, Ken Hornstein wrote:
On Wed, Nov 20, 2013 at 07:01:15PM -0500, Ken Hornstein wrote:
#define TAILQ_PREV(elm, headname, field) \
(*(((struct headname *)((elm)-field.tqe_prev))-tqh_last))
There's another
On Wed, Nov 20, 2013 at 07:01:15PM -0500, Ken Hornstein wrote:
#define TAILQ_PREV(elm, headname, field)\
(*(((struct headname *)((elm)-field.tqe_prev))-tqh_last))
There's another wrinkle, however, which is that this code (TAILQ_PREV)
also violates the
On Thu, Nov 21, 2013 at 01:16:44AM +0100, Rhialto wrote:
Ever since I grokked the elegance of Lists in AmigaOS, I've always
wondered why other list implementations do it differently.
One reason is that with Amiga lists is that the list node structure
needs to be at the beginning of the
On Sun, Nov 17, 2013 at 02:02:15AM +0100, Emmanuel Dreyfus wrote:
NetBSD-current seems to lack posix_fallocate(2)
http://pubs.opengroup.org/onlinepubs/009695299/functions/posix_fallocate
.html
Is someone already working on it, or has thoughs about how it should be
implemented?
I have
On Sun, Nov 17, 2013 at 01:32:03PM +0100, Hubert Feyrer wrote:
I plan to import it and to make it available to both lua(1) and lua(4)
I wonder if we really need to get all this into NetBSD,
instead of moving it to pkgsrc somehow.
This...
--
David A. Holland
dholl...@netbsd.org
On Sun, Nov 17, 2013 at 10:24:04AM +0100, Rhialto wrote:
I think the chief question at this level is whether to support the
keep the length flag for fallocate, fdiscard, both, or neither. The
What keep the length flag? I don't see one at the indicated URL.
It's a linuxism in linux's
On Sun, Nov 17, 2013 at 10:24:04AM +0100, Emmanuel Dreyfus wrote:
I think the chief question at this level is whether to support the
keep the length flag for fallocate, fdiscard, both, or neither. The
linux fallocate uses this to allow allocating blocks past EOF, which
strikes me as
On Sun, Nov 17, 2013 at 10:33:43AM +0100, Emmanuel Dreyfus wrote:
To answer both you and the Mouse - the difference is that a user process
actually writing data consumes measurable resources, and thus is easy to
find and kill. When everything happens in the kernel, spotting which
On Sat, Nov 16, 2013 at 12:40:22AM -0500, Mouse wrote:
The documentation I have (which is consistent across 1.4T, 4.0.1, and
5.2) says that [a] file I/O operation that would create a file larger
that the process' soft limit will cause the write to fail and a signal
SIGXFSZ to be generated.
On Tue, Nov 12, 2013 at 12:43:35AM +0100, Edgar Fu? wrote:
What the hell is this?
Nov 8 05:50:29 donau /netbsd: free inode /export/home/7 had -7306144 blocks
It looks as if ffs prints that when it finds trash in the blocks field
of an inode it's allocating.
probably time to fsck :(
I
On Sun, Nov 03, 2013 at 07:48:54PM -0500, Mouse wrote:
On Unix System V, the link command would allow hard-linking
directories when used as root.
Also, recently enough that at least some versions of NetBSD do it,
unlink(2) performed by root on the last non-. link to a directory would
On Fri, Nov 01, 2013 at 01:17:50PM -0400, Mouse wrote:
As zero-length symlinks aren't sensible, this should probably be
prohibited. Does anyone see any reason they shouldn't be?
I think not sensible is not a good enough reason to prohibit
something.
Yeah yeah, but still nowadays we
rmind@ points out that it's possible to create zero-length symlinks.
As zero-length symlinks aren't sensible, this should probably be
prohibited. Does anyone see any reason they shouldn't be?
(rmind wants me to post this message for some reason)
--
David A. Holland
dholl...@netbsd.org
On Wed, Oct 23, 2013 at 01:03:16PM -0400, Jeff Read wrote:
I was wondering if anyone was still actively working on ext3fs support
in NetBSD. I noticed it listed in the projects page and wanted to
synchronize my own extNfs efforts with anything currently ongoing.
To my knowledge nobody is
On Fri, Oct 18, 2013 at 12:34:24AM -0700, Matt Thomas wrote:
If the XIP code is not mergeable, what's entailed in doing a different
implementation that would be? Also, is the getpages/putpages interface
expressive enough to allow doing this without major UVM surgery? For
now I'm
On Fri, Oct 18, 2013 at 09:15:33AM -0700, Matt Thomas wrote:
The only problem is marking data as copy-on-write
but again these pages aren't managed so the current COW code won't
be happy.
We shouldn't have to care about that unless we want to move to
MAP_COPY from MAP_PRIVATE.
On Tue, Oct 15, 2013 at 12:17:30AM -0700, Matt Thomas wrote:
On Oct 14, 2013, at 11:41 PM, David Holland dholland-t...@netbsd.org wrote:
Did uebayasi@'s XIP work get finished/committed? Which things does it
work with? And (other than UTSL) where am I supposed to look to find
out more
On Mon, Oct 14, 2013 at 03:26:19PM -0700, Paul Goyette wrote:
-current is where development should take place.
I disagree. That way - doing development in the master tree - lies the
madness that has given Linux some of its worst problems. Development
should take place on branches,
Did uebayasi@'s XIP work get finished/committed? Which things does it
work with? And (other than UTSL) where am I supposed to look to find
out more?
--
David A. Holland
dholl...@netbsd.org
On Wed, Oct 09, 2013 at 11:00:53AM +0200, Marc Balmer wrote:
My question was about source code location, the other issues raised have
been discussed already in the past, but for the record:
Where and when? Several people have gone looking and not found this
discussion in the archives.
On Sat, Jun 15, 2013 at 11:56:55PM +, David Holland wrote:
I had almost forgotten about this; but a few months back when I came
into contact with the wd TRIM support in current I wanted to change
the interface around before it appears in a release.
Ok, as of this writing I have
On Sun, Sep 22, 2013 at 03:28:58AM +, David Holland wrote:
So, here's some thinking out loud on the subject of fixing it.
:
(I also have no real idea yet how to get to where I'm describing from
where we are in a decently incremental fashion.)
I think the first step forward
jakllsch@ and I just spent quite some time (so far unsuccessfully)
trying to figure out a hack to keep afs from deadlocking in vget().
As a consequence of this I've been looking through a bunch of the
vnode lifecycle code and my irritation level has gone past some
critical threshold.
So, here's
On Wed, Sep 18, 2013 at 03:34:19AM +0200, Emmanuel Dreyfus wrote:
Christos Zoulas chris...@zoulas.com wrote:
On large filesystems with many files fsck can take a really long time after
a crash. In my personal experience power outages are much less frequent
than
crashes (I crash
It seems that FreeBSD's and NetBSD's ffs superblock flags have been
allowed to diverge:
-FreeBSD
+NetBSD
#define FS_UNCLEAN 0x001 /* file system not clean at mount (unused) */
#define FS_DOSOFTDEP 0x002 /* file system using soft dependencies */
#define FS_NEEDSFSCK 0x004 /* needs
On Tue, Sep 03, 2013 at 02:04:18AM +, David Holland wrote:
FreeBSD apparently arbitrarily changed FS_INDEXDIRS when they merged
the softupdates-journaling code,
I have adopted this change as FS_SUJ actually appears in the wild, and
FS_INDEXDIRS doesn't I think correspond to anything
On Sun, Aug 18, 2013 at 06:04:55PM +0200, Johnny Billquist wrote:
Looking at 2.11BSD, it looks like this:
struct direct {
[snip]
In NetBSD (fairly current):
struct dirent {
careful, you want struct direct, not struct dirent:
struct direct {
u_int32_t d_fileno;
On Sun, Aug 18, 2013 at 12:24:12PM -0400, Mouse wrote:
A directory may contain entries other than subdirectories. Since there
is no enforced ordering of entries in a directory, the whole directory
must be read to find all the subdirectories (unless 32767 subdirs are
found first, I
On Mon, Aug 19, 2013 at 09:01:35AM +0200, Johnny Billquist wrote:
careful, you want struct direct, not struct dirent:
Hmm. Probably a good point. I was wondering if NetBSD had just
renamed direct to dirent, but that was just me getting confused
then. (And lazy, since I didn't really
On Sat, Jul 27, 2013 at 11:52:20PM -0700, Matt Thomas wrote:
I have several SoC targets that I've stalled on due to the need of writing
a tty driver. Sure I could cut paste from another driver but having to
do that 3+ times seems inordinately stupid. So I've been thinking of
making
On Fri, Jun 28, 2013 at 02:44:46PM +0200, Edgar Fu? wrote:
On an NFS-mounted file system, when you try to write to a file and are
over-quota, the write() succeeds, but a following fsync() or close() fails.
However, when you insert a utimes() or futimes() call after the write(),
the fsync()
As has come up many times in the past, we have a long-standing
problem, or family of problems, where in the course of operating on a
particular file system we end up not calling the file system's own
vnode or fs operations, but the root file system's operations. This
causes varying degrees of
I had almost forgotten about this; but a few months back when I came
into contact with the wd TRIM support in current I wanted to change
the interface around before it appears in a release.
The current interface is two ioctls:
- first you call DIOCGDISCARDINFO; this tells you the maximum
On Mon, Jun 03, 2013 at 11:37:29AM -0400, Mouse wrote:
At $JOB, we have two i386 machines with wm interfaces connected
back-to-back with a short patch cable and a /30 subnet of 192.168. One
is NFS-serving some disk space to the other over this link. They are
running 4.0.1 (with a few
On Mon, Jun 03, 2013 at 11:16:25PM -0400, Matt W. Benjamin wrote:
NFS-per se has change a lot since...NFSv4 came out. What NFS
versions does NetBSD currently support? I had the sense that it
probably tracked Rick Macklem's FreeBSD work at some distance...
Like, does NetBSD support pNFS?
On Wed, May 29, 2013 at 07:51:15PM +0200, Yann Sionneau wrote:
I am wondering how I can manage virtual memory (especially how to
avoid tlb miss, or deal with them) in exception handlers.
At first my idea was to do most of the low level stuff in exception
handlers with MMU turned off, I
On Thu, Feb 28, 2013 at 12:40:27AM -0500, Mouse wrote:
I'm looking at writing driver code for 5.2. A few manpages (notably
selinit(9) and other aliases for the same page) speak of non-MPSAFE
drivers, but I have been unable to find what a driver has to do in
order to be MPSAFE - nor for
On Wed, Feb 06, 2013 at 01:16:11AM +0100, Joerg Sonnenberger wrote:
On Tue, Feb 05, 2013 at 10:25:23AM +, David Holland wrote:
On Mon, Feb 04, 2013 at 09:39:04PM +0100, Joerg Sonnenberger wrote:
we have quite a few tools in base that still require KVM or optionally
support
On Wed, Jan 16, 2013 at 04:24:15PM -0600, Frank Zerangue wrote:
Migrating from 5.1.2 to 6.0.1 I have noticed many changes in the
virtual filesystem support interface. Can anyone point me to some
discussion or documentation of these changes?
http://www.netbsd.org/~dholland/outoftree.html
On Sun, Jan 13, 2013 at 09:36:24AM +0100, Martin Husemann wrote:
build and run. I've also arranged lib/libc/c063/t_o_search.c so that
the tests that make use of the O_SEARCH semantics will disappear until
O_SEARCH comes back, and fixed some mistakes and/or incorrect hacks
that were
The following (untested) patch reverts the defective O_SEARCH
implementation that was committed along with the *at calls back in
November.
I am currently building and testing it and will commit it when that
finishes.
I have left O_SEARCH defined and visible and made open() explicitly
ignore it.
On Tue, Dec 11, 2012 at 01:27:09AM +, Roland C. Dowdeswell wrote:
As an example, I often define a macro when I am using Kerberos or
GSSAPI that looks roughly like:
#ifdef K5BAIL(x) do {
ret = x;
if (ret) {
/* format error message
On Thu, Dec 06, 2012 at 10:32:01AM +, Julian Yon wrote:
I think you could take some inspiration from Linux here: it has a very
handy umount -l which detaches the filesystem from the tree, but defers
the rest of the unmount/cleanup until the fs is no longer busy. This
can help in
; in this case there won't be
processes hanging; but by the time you've confirmed this, there also
won't be processes using the fs, so the current scheme is more or less
safe enough...
Looks like this thread is dead. No one beside David Holland is
interested and David objects. I take back my proposal
On Wed, Dec 05, 2012 at 01:08:14PM -0500, Mouse wrote:
This system call embodies a fairly fundamental shift away from the
Unix model that object permissions are checked when you get a handle
to an object -- not when you use that handle.
Actually, I think that's true only of file
On Wed, Dec 05, 2012 at 08:39:55AM -0500, Thor Lancelot Simon wrote:
I also think we need to check, for all the fch*, fexec* syscalls:
* permissions both retained from the file's open and at the time
of use
I don't think this is necessary, any more than it is for read and
I am tired of PR 3019 and its many duplicates, so I'd like to see a
scheme that allows managing arbitrary subtrees of the filesystem
namespace in a reasonably useful manner.
The immediate application is nfs exports and mountd; however, I expect
the resulting mechanism will also be useful for
On Wed, Dec 05, 2012 at 04:03:40PM -0500, Mouse wrote:
* whether the name in question is within the process' current
root (forbidding fchdir and fchroot otherwise).
Definitely.
I'm actually not convinced this is so obviously a good thing.
I see an analogy between root
On Thu, Dec 06, 2012 at 08:55:56AM +0700, Robert Elz wrote:
| I am tired of PR 3019 and its many duplicates, so I'd like to see a
| scheme that allows managing arbitrary subtrees of the filesystem
| namespace in a reasonably useful manner.
If you're going to do something like
On Sat, Dec 01, 2012 at 11:38:55PM -0500, Mouse wrote:
things. What I care about is the largest size sector that will (in
^^^
the ordinary course of things anyway) be written atomically.
Then those are 512-byte-sector drives [...]
No; because
On Mon, Dec 03, 2012 at 12:19:58AM +, Julian Yon wrote:
You appear to have just agreed with me, which makes me wonder what I'm
missing, given you continue as though you disagree.
You asked why 4096-byte-sector disks accept 512-byte writes. I was
trying to explain.
However, we're
On Tue, Dec 04, 2012 at 09:26:17AM -0500, Thor Lancelot Simon wrote:
And, can't you do that with traditional drives, drives which really do
have 512-byte sectors? Do a 4K transfer and you write 8 physical
sectors with no opportunity for any other operation to see the write
On Tue, Dec 04, 2012 at 09:59:46AM +0300, Alan Barrett wrote:
the genfs code also never writes clean pages to disk, even though for
RAID5 storage it would likely be more efficient to write clean pages
that are in the same stripe as dirty pages if that would avoid issuing
partial-stripe
On Tue, Dec 04, 2012 at 01:58:13PM +, Julian Yon wrote:
The descriptor is probably already closed on exec before the syscall
tries to use it.
Nope. That happens later. I was looking through this code yesterday as
the topic interests me. The namei lookup happens pretty early on. I
On Sun, Dec 02, 2012 at 05:29:01PM +0100, J. Hannken-Illjes wrote:
I'm convinced -- having fstrans_start() return ERESTART is the way to go.
Ok then :-)
Also I wonder if there's any way to accomplish this that doesn't
require adding fstrans calls to every operation in every fs.
On Sat, Dec 01, 2012 at 04:27:14PM -0500, Mouse wrote:
Neither. The sector size claimed to the host should equal both the
sector size on the media and the granularity of the interface.
As a consumer of block devices, I don't care about either of these
things. What I care about is the largest
On Sat, Dec 01, 2012 at 07:07:36PM -0500, Mouse wrote:
Neither. The sector size claimed to the host should equal both the
sector size on the media and the granularity of the interface.
As a consumer of block devices, I don't care about either of these
things. What I care about is the
On Sun, Dec 02, 2012 at 01:32:17AM +, Julian Yon wrote:
I don't care about the block granularity of the interface. (Unless I
suppose it's larger than the atomic write size; but that would be
weird.)
If it's smaller than the atomic write size that's equally weird.
Because that
On Thu, Nov 29, 2012 at 06:19:37PM +0100, J. Hannken-Illjes wrote:
In short the attached diff:
- Adds a new kernel-internal errno ERESTARTVOP and changes VCALL() to
restart a vnode operation once it returns ERESTARTVOP.
- Changes fstrans_start() to take an optional `hint
On Fri, Nov 30, 2012 at 12:00:52PM +, David Laight wrote:
I must look at how to determine that disks have 4k sectors and to
ensure filesystesm have 4k fragments - regardless of the fs size.
newfs should already ensure that fragment = sector.
These disks lie about their actual
On Mon, Nov 26, 2012 at 03:06:34PM +0100, J. Hannken-Illjes wrote:
In short the attached diff:
- Adds a new kernel-internal errno ERESTARTVOP and changes VCALL() to
restart a vnode operation once it returns ERESTARTVOP.
- Changes fstrans_start() to take an optional `hint vnode' and
On Mon, Nov 26, 2012 at 01:49:09AM +0300, Alan Barrett wrote:
If necessary, the open(2) syscall could be versioned so that
O_RDONLY is no longer defined as zero.
This seems possibly worth doing to avoid all the annoyance with
FREAD/FWRITE vs. O_RDONLY/O_WRONLY, but I really don't see how it's
On Wed, Nov 28, 2012 at 03:12:36PM +, David Holland wrote:
On Mon, Nov 26, 2012 at 01:49:09AM +0300, Alan Barrett wrote:
If necessary, the open(2) syscall could be versioned so that
O_RDONLY is no longer defined as zero.
This seems possibly worth doing to avoid all the annoyance
On Thu, Nov 22, 2012 at 08:07:14PM +0100, Manuel Bouyer wrote:
On Thu, Nov 22, 2012 at 11:00:34AM -0800, John Nemeth wrote:
Would that prevent recovering in the case where the user
disconnects a device (typical example is a thumb drive) and later
reconnects it (once we have the
On Sat, Nov 17, 2012 at 06:42:50PM -0500, Thor Lancelot Simon wrote:
O_EXEC cause open()/openat() to fail if the file mode does not grant
execute rights
There are security concerns with fd passed to chrooted processes, which
could help executing code. Here is a proposal for
On Sun, Nov 18, 2012 at 06:16:00PM +, David Holland wrote:
This appears to contradict either the description of O_EXEC in the
standard, or the standard's rationale for adding fexecve(). The
standard says O_EXEC causes the file to be open for execution only.
In other words
On Sun, Nov 18, 2012 at 07:42:43PM +0100, Emmanuel Dreyfus wrote:
The standard is clearly wrong on a number of points and doesn't match
the historical design and behavior of Unix. Let's either implement
something correct, or not implement it at all.
Do you have something correct to
On Sun, Nov 18, 2012 at 06:51:51PM +, David Holland wrote:
This appears to contradict either the description of O_EXEC in the
standard, or the standard's rationale for adding fexecve(). The
standard says O_EXEC causes the file to be open for execution only
On Thu, Nov 15, 2012 at 11:58:59PM -0500, Thor Lancelot Simon wrote:
The problem is that there is a great deal of existing code in the
world which receives file descriptors and which is not designed with
the possibility that they might then be used to exec.
Then those programs
On Fri, Nov 16, 2012 at 12:35:46PM +, Julian Yon wrote:
Meanwhile, if you can own the other end to the point where you can
open an executable file containing code you supplied and pass it down
an existing socket connection, you've already done arbitrary code
execution. If the other
On Fri, Nov 16, 2012 at 09:13:13AM -0500, Thor Lancelot Simon wrote:
On Fri, Nov 16, 2012 at 09:14:14AM +, David Holland wrote:
On Thu, Nov 15, 2012 at 11:58:59PM -0500, Thor Lancelot Simon wrote:
Well, no. You have to first receive a new file descriptor from
somewhere, either
On Thu, Nov 15, 2012 at 11:03:15AM -0500, Thor Lancelot Simon wrote:
Here is a patch that implements fexecve(2) for review:
http://ftp.espci.fr/shadow/manu/fexecve.patch
This strikes me as profoundly dangerous. Among other things, it
means you can't allow any program running in a
On Thu, Nov 15, 2012 at 04:53:26PM -0500, Thor Lancelot Simon wrote:
Here is a patch that implements fexecve(2) for review:
http://ftp.espci.fr/shadow/manu/fexecve.patch
This strikes me as profoundly dangerous. Among other things, it
means you can't allow any program
On Sun, Nov 11, 2012 at 08:17:26AM +0100, Emmanuel Dreyfus wrote:
I know this is a bike shed, and I'm sorry to be the one to bring it
up, but can we use the names chmodat, chownat, c., for our native
system calls, and just use libc aliases or _BLAH_SOURCE nonsense or
something for the
On Sun, Nov 11, 2012 at 05:55:23AM +0100, Emmanuel Dreyfus wrote:
+ /*
+ * openat() falls back to open() behavior if
+ * - path is absolute XXX check this.
+ * - fd is AT_FDCWD
+ */
Have you checked the XXX, and/or written automatic tests for it?
On Sun, Nov 11, 2012 at 08:31:02AM +0100, Emmanuel Dreyfus wrote:
I don't think namei.h / vfs_lookup.c is the right place to be handling
file descriptors. Can you make these take vnodes, rather than file
descriptors, or move them into vfs_syscalls.c?
I made the change, but it makes
On Sun, Nov 11, 2012 at 10:39:06AM +0200, Alan Barrett wrote:
However, I also want the inconsistent POSIX names to be provided.
I don't know a good way of satisfying both goals.
#if defined(_POSIX_C_SOURCE) || defined(_XOPEN_SOURCE) /* or whatever */
int fchmodat(int, const char *, mode_t,
On Wed, Nov 07, 2012 at 11:34:08AM +0100, Edgar Fu? wrote:
wapbl_register_inode shouldn't be able to reach that panic...
Maybe that's some stack frame optimization.
Well... as far as I can tell wapbl_register_inode does not call
wapbl_register_deallocation, so it shouldn't be. But maybe ddb
On Wed, Nov 07, 2012 at 12:04:01PM +0100, J. Hannken-Illjes wrote:
ffs_truncate calls both, but mkdir shouldn't result in things being
released... or so I'd think.
It does. Just before returning ufs_direnter() tries to short the
directory and calls UFS_TRUNCATE() aka ffs_truncate().
On Tue, Nov 06, 2012 at 11:16:29PM +0100, Edgar Fu? wrote:
So, while investigating my WAPL performance problems, It looks like I can
crash the machine (not reliably, but more often that not) with a simple
seq 1 3000 |?xargs mkdir
command. I get the following backtrace in ddb (wetware
On Sun, Nov 04, 2012 at 06:54:57AM +0100, Emmanuel Dreyfus wrote:
But that cannot handle negative caching. FUSE allows the filesystem to
specify a TTL for a ENOENT. I cannot implement it at the PUFFS level
like I did before, since there is no struct puffs_node associated with
an unexistant
On Tue, Oct 23, 2012 at 12:54:43PM +0200, tlaro...@polynum.com wrote:
On Tue, 23 Oct 2012, Emmanuel Dreyfus wrote:
About PAM modules invoking libpthread.
I don't know if this is related or not, but is this an explanation of
why, sometimes, generally using pkgsrc (when it switches to
On Tue, Oct 23, 2012 at 07:53:28PM +0200, Edgar Fu? wrote:
the output of ps -lax on the NFS server during the 18-20 second window
As far as I remember (you need the s option, too), the main nfsd
thread is on select, one subthread on biowait or biolock and the
others on tstile.
It would
In the long-term interests of making struct componentname go away
entirely, here's the next step in namei-related cleanup.
This patch: (1) moves the namecache's hash computation inside the
namecache, instead of being spread around all over everywhere; (2)
fixes the namecache to no longer require
On Mon, Oct 15, 2012 at 12:34:44PM +0200, haad wrote:
These four pieces are available as separate patches, but since nobody
seems to be interested in that, the following is all of them rolled
together.
Can you fix zfs, too ? Or I can fix it after your commit.
I did. Not sure why it
On Sun, Oct 14, 2012 at 07:20:02AM +, Taylor R Campbell wrote:
I'm working on fixing ZFS locking, and I ran into a diference between
NetBSD's and Solaris's interpretation of condvars.
In Solaris, it seems to be kosher to do
cv_broadcast(cv);
cv_destroy(cv);
at least
On Sat, Oct 06, 2012 at 04:15:20PM +0200, Rhialto wrote:
That's what Linux does for the most part. I don't think our current
VFS protocol is particularly amenable to making this work easily.
A first version may always implement the async calls as sync, right?
I've seen no requirement
On Fri, Oct 05, 2012 at 04:07:38PM +, paul_kon...@dell.com wrote:
I am playing with oracle XE on 6.0_RC2 and ktrace tells me that this
requires Linux aio_* system calls.
[...]
Is there any advantage to using aio rather than regular I/O from
threads? I've used both (aio only a
On Tue, Sep 18, 2012 at 02:01:25AM +0700, Robert Elz wrote:
| Sorry but I can't see how a kernel with COMPAT_LINUX but without
| mfi would compile.
The way I proposed it, it wouldn't, but given that we have control
of the mfi driver, we can do interesting stuff to its cdevsw.
On Wed, Sep 05, 2012 at 06:40:22AM +0200, Emmanuel Dreyfus wrote:
Sure, but regardless of where that other check is implemented, it
seems like it might be wrong, since it's checking the real uid,
not the effective uid.
That would be nice to have a fix for that in 6.0. The thing
On Wed, Sep 05, 2012 at 12:00:47PM -0500, Eric Haszlakiewicz wrote:
Changing it to effective uid seems like a good plan.
The change below fixes the test case. Is it safe to commit?
It fixes the test case, but it is still wrong. This UID check
needs to be implemented in the
On Wed, Sep 05, 2012 at 12:14:11PM -0500, Eric Haszlakiewicz wrote:
Changing it to effective uid seems like a good plan.
The change below fixes the test case. Is it safe to commit?
It fixes the test case, but it is still wrong. This UID check
needs to be
On Tue, Aug 21, 2012 at 11:10:05AM +0200, Adam Ciarci?ski wrote:
I strongly disagree. Clang works excellently. Here's my way to
build NetBSD (does not need command line tools being installed,
Xcode in /Applications is sufficient):
#!/bin/csh
*cough*
--
David A. Holland
On Sun, Aug 26, 2012 at 12:24:33PM -0700, Paul Goyette wrote:
Well, in the case of the BBU it would be better to display good or bad.
ABSENT would be misleading, becase what we really want to report
is that the BBU is present but bad.
I'm sure we could come up with dozens of pairs of
On Wed, Aug 22, 2012 at 06:25:43PM +0100, Roger Pau Monn? wrote:
I've hit this when deleting a large number of files inside a DomU (but
I'm not sure this is related to Xen specific code). I'm using the 6.0
branch, fetched this morning (RC1), XEN3_DOMU kernel amd64 and the
filesystem is
On Tue, May 15, 2012 at 04:57:42PM +, David Holland wrote:
With an interactive edquota, I got
edquota: /export/test (ufs/ffs quota v2):
: bad format
[...]
Is this expected behaviour?
[...]
However, edquota is supposed to work. It is definitely possible that I
401 - 500 of 795 matches
Mail list logo
