Date: Mon, 29 Mar 2010 23:47:16 +0300 From: Andriy Gapon <avg@freebsd.org> To: Fabian Keil <freebsd-listen@fabiankeil.de> Cc: Kostik Belousov <kostikbel@gmail.com>, freebsd-current@freebsd.org Subject: Re: newfs_msdos and DVD-RAM Message-ID: <4BB111D4.8060809@freebsd.org> In-Reply-To: <20100329222920.5eef6395@r500.local> References: <3a142e751003190508x6a06868ene2e8fd9ddd977f66@mail.gmail.com> <3a142e751003191021p141af009m6acf7d160c890cbb@mail.gmail.com> <20100319191133.46fe271c@r500.local> <3a142e751003191126j331e525fwb9e5573bbf6f7d58@mail.gmail.com> <4BAA30CB.1070707@icyb.net.ua> <20100328172537.501ed3d1@r500.local> <4BB0A053.9060007@freebsd.org> <20100329222920.5eef6395@r500.local>
next in thread | previous in thread | raw e-mail | index | archive | help
on 29/03/2010 23:29 Fabian Keil said the following: > Andriy Gapon <avg@freebsd.org> wrote: >> Thus, clearly, it is a fault of a tool that formatted the media for FAT. >> It should have picked correct values, or rejected incorrect values if >> those were provided as overrides via command line options. > > The kernel still shouldn't panic, though. A quick reply to this point only - yes, I completely agree. But remember that the panic happened only after the sources were modified :) Jokes aside, mountmsdosfs() should reject incorrect combination of bytes/sector and sectors/cluster and should produce proper diagnostics for that. -- Andriy Gapon
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?4BB111D4.8060809>