linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Matt Porter <mporter@kernel.crashing.org>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] consistent_sync unaligned buffers debug check, resend
Date: Tue, 5 Aug 2003 13:48:28 -0700	[thread overview]
Message-ID: <20030805134828.B722@home.com> (raw)
In-Reply-To: <5.1.0.14.2.20030804213501.00b08410@mail.ebshome.net>; from ebs@ebshome.net on Mon, Aug 04, 2003 at 09:40:02PM -0700


On Mon, Aug 04, 2003 at 09:40:02PM -0700, Eugene Surovegin wrote:
> I suspect original e-mail had bad timing, all important people were busy
> preparing/flying to OLS ;-)

Heh

> So, here is another try...
>
> These patches add new debugging option under "Kernel hacking|Kernel debugging".
> This option enables rate-limited warning print out when consistent_sync is
> called with unaligned buffer.

Looks fine to me.  I'll add it to my large queue of changesets for
Paul to review/pull to marcelo's tree.

FWIW, I talked to a bunch of SCSI folks at OLS about DMA off the stack
and they believe it's all gone in 2.6.  I double-checked and that does
seem to be the case.  Nevertheless, I think we will always be fighting
poorly written drivers so this seems to be a great debug option.

Regards,
--
Matt Porter
mporter@kernel.crashing.org

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-08-05 20:48 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-05  4:40 [PATCH] consistent_sync unaligned buffers debug check, resend Eugene Surovegin
2003-08-05 20:48 ` Matt Porter [this message]

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=20030805134828.B722@home.com \
    --to=mporter@kernel.crashing.org \
    --cc=ebs@ebshome.net \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    /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).