On Fri, 19 Jul 2013, Todd C. Miller wrote:
> On Fri, 19 Jul 2013 21:02:41 +0200, Christian Weisgerber wrote:
> > Switching the processing order in getmntname() fixes the behavior.
> > Can anybody think of something that would be broken by this?
>
> I can't see any reason not do to this. I'm sure
> On Wed, Jul 17, 2013 at 12:11, Sergey Bronnikov wrote:
> > Bug was catched by fsfuzzer. Probably that bug cannot be
> > found in real life with real usecase, but anyway it is a bug.
>
> Sorry, but I don't think these bugs are interesting. The filesystem
> code panics when it encounters a broken
On Wed, Jul 17, 2013 at 12:11, Sergey Bronnikov wrote:
> Bug was catched by fsfuzzer. Probably that bug cannot be
> found in real life with real usecase, but anyway it is a bug.
Sorry, but I don't think these bugs are interesting. The filesystem
code panics when it encounters a broken filesystem.
Todd C. Miller:
> > Switching the processing order in getmntname() fixes the behavior.
> > Can anybody think of something that would be broken by this?
>
> I can't see any reason not do to this. I'm sure you were trying
> for a minimal diff but doesn't it make more sense to make the loop
> more
Thankyou for your advice to this. Gonna look into recommended athn card to
replace our ral selection.
Maintainer team at OpenBSD would you be kind to correct manual pages for
ral for future users? This manpage typo costed us NNN Euro ;-)
2013/7/16 stolendata.net
>
> I recently opted for gettin
I've just installed the latest snapshot of OpenBSD/amd64 on a
Thinkpad T410 a few days ago, and I'm getting various "iwn0: fatal
firmware error"s.
I had a NMI_INTERRUPT_WDG just when I was /connect'ing in irssi:
firmware error log:
error type = "NMI_INTERRUPT_WDG" (0x0004)
program co
