Flexible I/O Tester development
 help / color / mirror / Atom feed
From: Jens Axboe <axboe@kernel.dk>
To: Ken Raeburn <raeburn@permabit.com>
Cc: fio@vger.kernel.org
Subject: Re: [PATCH] Fix crash with absurdly but not impossibly deeply nested device stacks.
Date: Wed, 30 Jan 2013 12:58:51 +0100	[thread overview]
Message-ID: <20130130115851.GX8800@kernel.dk> (raw)
In-Reply-To: <6e1ud3r699.fsf@just-testing.permabit.com>

On Tue, Jan 29 2013, Ken Raeburn wrote:
> 
> Sure, I'll work up some patches for the [v]snprintf calls and the
> missing smalloc failure check...

I patched up the smalloc already, but the *snprintf() stuff would be
excellent to have fixed up.

-- 
Jens Axboe


  reply	other threads:[~2013-01-30 11:59 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-29  1:24 path name lengths Ken Raeburn
2013-01-29  1:48 ` [PATCH] Fix crash with absurdly but not impossibly deeply nested device stacks Ken Raeburn
2013-01-29  9:17   ` Jens Axboe
2013-01-29  9:19     ` Jens Axboe
2013-01-29 21:06     ` Ken Raeburn
2013-01-29 21:15       ` Jens Axboe
2013-01-29 22:09         ` Ken Raeburn
2013-01-30 11:58           ` Jens Axboe [this message]
2013-01-30 21:25             ` [PATCH] Fix bugs in [v]snprintf usage Ken Raeburn
2013-01-30 21:48               ` Jens Axboe

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20130130115851.GX8800@kernel.dk \
    --to=axboe@kernel.dk \
    --cc=fio@vger.kernel.org \
    --cc=raeburn@permabit.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox