On 2010-10-12, Andriy Gapon wrote:
> on 12/10/2010 16:36 Matthew Jacob said the following:
> > Good workaround, still a nasty surprising bug.
>
> Yeah. I also would prefer ignoring such a partition or somehow sanitizing its
> name or etc. panic(9) on bad internal state of a kernel sounds approp
I am antisocial.
Okay, changed it so my replies are above the quotes. Seems to have
attributes here. And I usually hit 'reply list' since multiple copies
burns bandwidth.
On 10/12/2010 1:57 PM, Andriy Gapon wrote:
P.S. Matthew, it seems like you have a really unhelpful mail client program:
on 12/10/2010 16:36 Matthew Jacob said the following:
> Good workaround, still a nasty surprising bug.
Yeah. I also would prefer ignoring such a partition or somehow sanitizing its
name or etc. panic(9) on bad internal state of a kernel sounds appropriate,
panic(9) on bad input sounds like trou
Good workaround, still a nasty surprising bug.
On 2010-10-11, barbara wrote:
The panic is caused by:
g_dev_taste(): make_dev_p() failed (gp->name=ext2fs//, error=22)
as I have a linux partition (I swear, it's for my mom!) on the same machine.
As I don't care about that partition (being ext4 I
On 2010-10-11, barbara wrote:
> The panic is caused by:
> g_dev_taste(): make_dev_p() failed (gp->name=ext2fs//, error=22)
> as I have a linux partition (I swear, it's for my mom!) on the same machine.
> As I don't care about that partition (being ext4 I can't even mount
> it), is there any solutio
Since r213526 device names are checked on device registration. That is,
if you call a make_dev*() function with an invalid device name, a panic
will occur by default. For make_dev_credf(9) or make_dev_p(9) you can
specify the MAKEDEV_CHECKNAME flag to get an error return instead of a
panic.
Inval
