All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andries Brouwer <aeb@veritas.com>
To: Jan Niehusmann <jan@gondor.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: attempt to access beyond end of device
Date: Thu, 7 Dec 2000 17:34:28 +0100	[thread overview]
Message-ID: <20001207173428.A23936@veritas.com> (raw)
In-Reply-To: <20001207165659.A1167@gondor.com>
In-Reply-To: <20001207165659.A1167@gondor.com>; from jan@gondor.com on Thu, Dec 07, 2000 at 04:56:59PM +0100

On Thu, Dec 07, 2000 at 04:56:59PM +0100, Jan Niehusmann wrote:
> ll_rw_blk.c: generic_make_request() contains the following code:
> 
> if (maxsector < count || maxsector - count < sector) {
> 	bh->b_state &= (1 << BH_Lock) | (1 << BH_Mapped);
> 	if (blk_size[major][MINOR(bh->b_rdev)]) {
> 
> 		/* This may well happen - the kernel calls bread()
> 		   without checking the size of the device, e.g.,
> 		   when mounting a device. */
> 		printk(KERN_INFO
> 		       "attempt to access beyond end of device\n");
> 		printk(KERN_INFO "%s: rw=%d, want=%d, limit=%d\n",
> 		       kdevname(bh->b_rdev), rw,
> 		       (sector + count)>>1,
> 		       blk_size[major][MINOR(bh->b_rdev)]);
> 	}
> 	bh->b_end_io(bh, 0);
> 	return;
> }
> 
> 
> That means that if blk_size[major][MINOR(bh->b_rdev)] == 0, the request
> is canceled but no message is printed. Shouldn't there be a warning message?

Maybe that code fragment is mine. If so, then at some point
in time I decided that the answer to your question is no.

Andries
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  reply	other threads:[~2000-12-07 17:05 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-07 15:56 attempt to access beyond end of device Jan Niehusmann
2000-12-07 16:34 ` Andries Brouwer [this message]
2000-12-07 17:10   ` John Kennedy
  -- strict thread matches above, loose matches on Subject: below --
2014-03-24  7:13 Piotr Szymaniak
2014-03-24  7:37 ` Vyacheslav Dubeyko
2014-03-24 20:49   ` Piotr Szymaniak
2014-03-25  9:18     ` Vyacheslav Dubeyko
2014-03-27 12:39       ` Piotr Szymaniak
2014-03-29 14:49         ` Vyacheslav Dubeyko
2014-03-24 22:31   ` Piotr Szymaniak
2010-04-26 20:20 Re: Attempt to Access Beyond End of Device willis
2010-04-26 20:54 ` Eric Sandeen
2007-09-10 13:59 Federico Sevilla III
2007-09-10 14:44 ` Justin Piszcz
2007-09-10 14:59   ` Federico Sevilla III
2007-09-10 15:45     ` Justin Piszcz
2007-09-10 15:51       ` Federico Sevilla III
2007-09-10 15:47 ` Eric Sandeen
2007-09-10 15:54   ` Federico Sevilla III
2007-09-10 16:28     ` Eric Sandeen
     [not found]       ` <cc7060690709111208u3e0842f9rd6edff16539b8a28@mail.gmail.com>
2007-09-12  5:17         ` Federico Sevilla III
2006-12-05 14:01 attempt to access beyond end of device Koen Vereeken
2006-01-19 12:02 Handling of read errors in raid6 Filipe Maia
2006-01-19 20:39 ` attempt to access beyond end of device PFC
2004-04-13 10:03 Luca Ferrari
2004-04-13 10:41 ` Thomas Steudten
2004-04-13 11:08   ` Luca Ferrari
2004-04-13 11:20     ` Thomas Steudten
2004-04-13 11:45       ` Luca Ferrari
2004-04-13 12:44         ` Thomas Steudten
2004-04-13 12:53           ` Luca Ferrari
2002-12-06  5:21 Justin Pryzby
2002-12-05 18:54 Justin Pryzby
2000-11-24  9:02 Janek

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=20001207173428.A23936@veritas.com \
    --to=aeb@veritas.com \
    --cc=jan@gondor.com \
    --cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.