On Fri, 9 Mar 2012, Peter Holm wrote:
On Fri, Mar 09, 2012 at 03:51:30PM +1100, Bruce Evans wrote:
On Thu, 8 Mar 2012, Peter Holm wrote:
Log:
syscall() fuzzing can trigger this panic. Return EINVAL instead.
MFC after: 1 week
If so, then, this is not the place to hide the bug.
OK
On Sat, Mar 10, 2012 at 01:48:20AM +1100, Bruce Evans wrote:
On Fri, 9 Mar 2012, Peter Holm wrote:
On Fri, Mar 09, 2012 at 03:51:30PM +1100, Bruce Evans wrote:
On Thu, 8 Mar 2012, Peter Holm wrote:
Log:
syscall() fuzzing can trigger this panic. Return EINVAL instead.
MFC after: 1 week
Author: pho
Date: Thu Mar 8 12:49:08 2012
New Revision: 232692
URL: http://svn.freebsd.org/changeset/base/232692
Log:
syscall() fuzzing can trigger this panic. Return EINVAL instead.
MFC after:1 week
Modified:
head/sys/ufs/ffs/ffs_vnops.c
Modified: head/sys/ufs/ffs/ffs_vnops.c
On Thu, 8 Mar 2012, Peter Holm wrote:
Log:
syscall() fuzzing can trigger this panic. Return EINVAL instead.
MFC after: 1 week
If so, then, this is not the place to hide the bug.
Modified: head/sys/ufs/ffs/ffs_vnops.c
On Fri, Mar 09, 2012 at 03:51:30PM +1100, Bruce Evans wrote:
On Thu, 8 Mar 2012, Peter Holm wrote:
Log:
syscall() fuzzing can trigger this panic. Return EINVAL instead.
MFC after: 1 week
If so, then, this is not the place to hide the bug.
OK
Modified: