From: Neil Brown <neilb@suse.de>
To: ml-raid@syscall.eu
Cc: linux-raid@vger.kernel.org
Subject: Re: Possible bug
Date: Wed, 9 Dec 2009 12:57:24 +1100 [thread overview]
Message-ID: <20091209125724.2652d413@notabene.brown> (raw)
In-Reply-To: <4B1E5220.8030500@syscall.eu>
On Tue, 08 Dec 2009 14:18:24 +0100
ml-raid@syscall.eu wrote:
> Hello,
> I have a 2.6.27.29-4-grsec (from http://kernelsec.cr0.org) Linux box, on
> x86, running debian lenny. On sunday, during the monthly rebuild of my
> standard RAID1 setup (/proc/mdstat):
>
> Personalities : [raid1]
> md127 : active raid1 sda1[0] sdb1[1]
> 488383936 blocks [2/2] [UU]
>
> unused devices: <none>
>
> The kernel started outputting thousands of backtraces (see attached log)
> The IO throughput was drastically reduced but the resync finally
> completed after about 38 hours.
>
> This is the first time I have been bitten by this bug. The server has
> been running on this kernel for 74 days and the previous resync didn't
> exhibit any problem.
This is not a RAID problem - it was a problem with the grsec patches.
They assume that any atomic variable is used as a counter and should not
overflow. That is not the case with bd_disk->sync_io. It is expected to
overflow. So the "PAX: ..." report is a false positive.
NeilBrown
next prev parent reply other threads:[~2009-12-09 1:57 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-08 13:18 Possible bug ml-raid
2009-12-09 1:57 ` Neil Brown [this message]
2009-12-09 9:39 ` ml-raid
-- strict thread matches above, loose matches on Subject: below --
2016-05-06 19:48 David Kiarie
[not found] ` <5d645be8-fbd0-0454-af00-baf34a2816a0@iommu.org>
[not found] ` <5d645be8-fbd0-0454-af00-baf34a2816a0-6ukY98dZOFrYtjvyW6yDsg@public.gmane.org>
2016-05-07 8:33 ` David Kiarie
2016-03-31 12:34 Possible Bug Roger H Newell
2016-03-31 14:37 ` Valdis.Kletnieks at vt.edu
[not found] ` <56FD5089.5070302@canonical.com>
2016-03-31 17:52 ` Valdis.Kletnieks at vt.edu
2016-03-31 18:16 ` Roger H Newell
2016-03-31 19:23 ` Valdis.Kletnieks at vt.edu
2016-03-31 20:22 ` Roger H Newell
[not found] ` <56FDD8D9.9010408@gmail.com>
2016-04-01 13:00 ` Roger H Newell
[not found] ` <56FD38C4.8030201@gmail.com>
2016-03-31 15:08 ` Roger H Newell
[not found] ` <56FD4C35.5040301@gmail.com>
2016-03-31 16:25 ` Roger H Newell
2016-03-31 17:22 ` Valdis.Kletnieks at vt.edu
2016-03-31 16:30 ` Carlo Caione
[not found] ` <56FD5358.5010101@gmail.com>
2016-03-31 17:29 ` Roger H Newell
2016-03-31 18:42 ` Valdis.Kletnieks at vt.edu
2012-07-21 7:09 Possible bug Ariel Norberto Bellino
2012-07-24 12:01 ` Thomas Renninger
2012-07-24 12:07 ` Jukka Ruohonen
2012-07-25 4:23 ` Ariel Norberto Bellino
2011-07-23 20:25 Reuben Thomas
2003-06-09 19:40 Possible Bug Angelo
2002-10-01 15:44 possible bug undertow
2002-10-01 16:37 ` DervishD
2002-10-03 1:29 ` Denis Vlasenko
2002-10-02 22:38 ` DervishD
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=20091209125724.2652d413@notabene.brown \
--to=neilb@suse.de \
--cc=linux-raid@vger.kernel.org \
--cc=ml-raid@syscall.eu \
/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.