From: Bartlomiej Zolnierkiewicz <bzolnier@gmail.com>
To: Alan Cox <alan@redhat.com>
Cc: Jeremy Higdon <jeremy@sgi.com>, Jes Sorensen <jes@sgi.com>,
Linus Torvalds <torvalds@osdl.org>,
linux-kernel@vger.kernel.org
Subject: Re: [patch] SGIIOC4 limit request size
Date: Wed, 1 Feb 2006 15:53:10 +0100 [thread overview]
Message-ID: <58cb370e0602010653g3c60b2ffoa9a84f83c7af45c1@mail.gmail.com> (raw)
In-Reply-To: <20060201133917.GA27011@devserv.devel.redhat.com>
On 2/1/06, Alan Cox <alan@redhat.com> wrote:
> On Wed, Feb 01, 2006 at 03:36:07AM -0800, Jeremy Higdon wrote:
> > Here's one that removes xcount. It seems to work too.
> > Should we set hwif->rqsize to 256, or are we pretty safe in
> > expecting that the default won't rise? The driver should be
>
> 255 is the safest for LBA28 devices because a small number incorrectly
> interpret 0 (meaning 256) as 0. And that can have unfortunate results
We can blacklist vulnerable devices if needed.
We have been using 256 for a long time now.
prev parent reply other threads:[~2006-02-01 14:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 8:59 [patch] SGIIOC4 limit request size Jes Sorensen
2006-02-01 10:34 ` Bartlomiej Zolnierkiewicz
2006-02-01 10:41 ` Jes Sorensen
2006-02-01 10:49 ` Jeremy Higdon
2006-02-01 11:08 ` Bartlomiej Zolnierkiewicz
2006-02-01 11:17 ` Jeremy Higdon
2006-02-01 11:26 ` Bartlomiej Zolnierkiewicz
2006-02-01 11:36 ` Jeremy Higdon
2006-02-01 12:44 ` Bartlomiej Zolnierkiewicz
2006-02-02 8:00 ` [patch] Fix DMA timeouts with sgiioc4 Jeremy Higdon
2006-02-02 8:45 ` Jes Sorensen
2006-02-01 13:39 ` [patch] SGIIOC4 limit request size Alan Cox
2006-02-01 14:53 ` Bartlomiej Zolnierkiewicz [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=58cb370e0602010653g3c60b2ffoa9a84f83c7af45c1@mail.gmail.com \
--to=bzolnier@gmail.com \
--cc=alan@redhat.com \
--cc=jeremy@sgi.com \
--cc=jes@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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).