Thread (14 messages) 14 messages, 3 authors, 2013-11-05

Re: [PATCH 2/2] xfs: add FALLOC_FL_ZERO_RANGE to fallocate

From: Paolo Bonzini <pbonzini@redhat.com>
Date: 2012-06-13 06:24:12
Also in: linux-fsdevel, lkml

Il 13/06/2012 04:16, Dave Chinner ha scritto:
quoted
quoted
+	BUG_ON((mode & FALLOC_FL_PUNCH_HOLE) && (mode & FALLOC_FL_ZERO_RANGE));
Never put BUG_ON() or BUG() in XFS code that can return an error.
Return EINVAL if we chose not to support it, and if it's really
something we consider bad, emit a warning to syslog (i.e.
xfs_warn()) and potentially add a ASSERT() case so that debug
kernels will trip over it. Nobody should be panicing a production
system just because a user supplied a set of incorrect syscall
paramters....
I know, the BUG_ON() is because it is ruled out in VFS code.  Of course
if I remove that code, this will not be a BUG_ON() anymore.

Paolo

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help