From: mroos@linux.ee
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: David Miller <davem@davemloft.net>,
sparclinux@vger.kernel.org, edumazet@google.com,
netdev@vger.kernel.org
Subject: Re: Invalid sk_policy[] access
Date: Tue, 23 Feb 2016 20:37:13 +0000 [thread overview]
Message-ID: <alpine.LRH.2.20.1602232236080.30129@math.ut.ee> (raw)
In-Reply-To: <20160223202901.GC4941@oracle.com>
> > Indeed, the kernel is 64-bit in both cases.
> > And the userland bit-arity has no relevance whatsoever for this bug.
>
> hang on; The sizeof (and offsetof) values I listed were obtained either
> from /usr/bin/crash (on the T5) or from simple printk's of the structures
> in the case of the v440. And they *are* different, and the numbers
> match the values dumped on the console on pnaic. So isnt there actually
> a problem here?
There certianly seems to be a problem - that's how you ended up looking
under that rock.
Maybe the offsets are different because of different kernel config?
--
Meelis Roos (mroos@linux.ee)
WARNING: multiple messages have this Message-ID (diff)
From: mroos@linux.ee
To: Sowmini Varadhan <sowmini.varadhan@oracle.com>
Cc: David Miller <davem@davemloft.net>,
sparclinux@vger.kernel.org, edumazet@google.com,
netdev@vger.kernel.org
Subject: Re: Invalid sk_policy[] access
Date: Tue, 23 Feb 2016 22:37:13 +0200 (EET) [thread overview]
Message-ID: <alpine.LRH.2.20.1602232236080.30129@math.ut.ee> (raw)
In-Reply-To: <20160223202901.GC4941@oracle.com>
> > Indeed, the kernel is 64-bit in both cases.
> > And the userland bit-arity has no relevance whatsoever for this bug.
>
> hang on; The sizeof (and offsetof) values I listed were obtained either
> from /usr/bin/crash (on the T5) or from simple printk's of the structures
> in the case of the v440. And they *are* different, and the numbers
> match the values dumped on the console on pnaic. So isnt there actually
> a problem here?
There certianly seems to be a problem - that's how you ended up looking
under that rock.
Maybe the offsets are different because of different kernel config?
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2016-02-23 20:37 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-06 15:21 Recent spontaneous reboots on multiple machines Meelis Roos
2016-01-06 15:22 ` Meelis Roos
2016-01-07 17:41 ` Sowmini Varadhan
2016-01-07 19:46 ` Meelis Roos
2016-01-07 20:14 ` Sowmini Varadhan
2016-01-08 17:20 ` Sowmini Varadhan
2016-01-08 19:02 ` David Miller
2016-01-08 20:18 ` mroos
2016-01-08 21:15 ` Sowmini Varadhan
2016-01-08 21:29 ` Meelis Roos
2016-01-10 10:03 ` Meelis Roos
2016-02-05 9:06 ` Meelis Roos
2016-02-14 10:51 ` Sowmini Varadhan
2016-02-15 5:54 ` Meelis Roos
2016-02-18 2:30 ` Sowmini Varadhan
2016-02-22 1:02 ` Sowmini Varadhan
2016-02-23 12:12 ` Invalid sk_policy[] access (was Re: Recent spontaneous reboots on multiple machines) Sowmini Varadhan
2016-02-23 12:12 ` Sowmini Varadhan
2016-02-23 19:36 ` Meelis Roos
2016-02-23 19:36 ` Meelis Roos
2016-02-23 19:39 ` Sowmini Varadhan
2016-02-23 19:39 ` Sowmini Varadhan
2016-02-23 20:45 ` Meelis Roos
2016-02-23 20:45 ` Meelis Roos
2016-02-23 20:20 ` Invalid sk_policy[] access David Miller
2016-02-23 20:20 ` David Miller
2016-02-23 20:29 ` Sowmini Varadhan
2016-02-23 20:29 ` Sowmini Varadhan
2016-02-23 20:37 ` mroos [this message]
2016-02-23 20:37 ` mroos
2016-02-23 20:51 ` mroos
2016-02-23 20:51 ` mroos
2016-02-23 20:53 ` Sowmini Varadhan
2016-02-23 20:53 ` Sowmini Varadhan
2016-02-23 23:05 ` David Miller
2016-02-23 23:05 ` David Miller
2016-02-23 22:59 ` David Miller
2016-02-23 22:59 ` David Miller
2016-02-23 23:59 ` Sowmini Varadhan
2016-02-23 23:59 ` Sowmini Varadhan
2016-02-24 0:23 ` David Miller
2016-02-24 0:23 ` David Miller
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=alpine.LRH.2.20.1602232236080.30129@math.ut.ee \
--to=mroos@linux.ee \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=netdev@vger.kernel.org \
--cc=sowmini.varadhan@oracle.com \
--cc=sparclinux@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.