From: Anton Blanchard <anton@samba.org>
To: Wayne Boyer <wayneb@linux.vnet.ibm.com>
Cc: betabandido@gmail.com, linux-scsi@vger.kernel.org,
linuxppc-dev@ozlabs.org
Subject: Re: [PATCH] [SCSI] ipr: Fix stack overflow in ipr_format_resource_path
Date: Thu, 3 Jun 2010 14:20:19 +1000 [thread overview]
Message-ID: <20100603042019.GI28295@kryten> (raw)
In-Reply-To: <4C072C18.4030005@linux.vnet.ibm.com>
Hi Wayne,
> We also saw a variation of this problem last week and I have an alternative
> patch that I'd prefer over this one. I'll post the patch in a separate
> email.
Thanks. Can you get it into -stable too? As you can see users are hitting it.
Anton
next prev parent reply other threads:[~2010-06-03 4:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 11:16 [PATCH] [SCSI] ipr: Fix stack overflow in ipr_format_resource_path Anton Blanchard
2010-06-03 4:14 ` Wayne Boyer
2010-06-03 4:20 ` Anton Blanchard [this message]
2010-06-03 23:02 ` [PATCH 1/1] [SCSI] ipr: fix resource path display and formatting Wayne Boyer
2010-06-04 19:04 ` Brian King
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=20100603042019.GI28295@kryten \
--to=anton@samba.org \
--cc=betabandido@gmail.com \
--cc=linux-scsi@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=wayneb@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).