From: Al Viro <viro@ZenIV.linux.org.uk>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Alejandro Riveira Fern?ndez <ariveira@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Dmitry Baryshkov <dbaryshkov@gmail.com>,
Alistair John Strachan <alistair@devzero.co.uk>,
"Michael B. Trausch" <mike@trausch.us>
Subject: Re: Linux 2.6.28-rc7
Date: Tue, 2 Dec 2008 20:29:41 +0000 [thread overview]
Message-ID: <20081202202941.GG28946@ZenIV.linux.org.uk> (raw)
In-Reply-To: <alpine.LFD.2.00.0812021120110.3256@nehalem.linux-foundation.org>
On Tue, Dec 02, 2008 at 11:23:42AM -0800, Linus Torvalds wrote:
>
>
> On Tue, 2 Dec 2008, Alejandro Riveira Fern??ndez wrote:
> >
> > Here you go
> >
> > [alex@varda:kernel/linux-2.6]$ git bisect bad
> > 31168481c32c8a485e1003af9433124dede57f8d is first bad commit
>
> Excellent. One last step - can you verify that just reverting this commit
> makes your problems go away?
I would be _very_ surprised if it did; the only thing that could possibly
happen there is executing code from freed memory if the section changes
are fucked up and that definitely does not match the symptoms described.
next prev parent reply other threads:[~2008-12-02 20:29 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-02 4:11 Linux 2.6.28-rc7 Linus Torvalds
2008-12-02 12:14 ` Alejandro Riveira Fernández
2008-12-02 13:11 ` pazke
2008-12-02 14:48 ` Alejandro Riveira Fernández
2008-12-02 15:20 ` Alistair John Strachan
2008-12-02 15:50 ` Alejandro Riveira Fernández
2008-12-02 16:14 ` Alistair John Strachan
2008-12-02 15:54 ` Alejandro Riveira Fernández
2008-12-02 15:50 ` Linus Torvalds
2008-12-02 15:56 ` Alejandro Riveira Fernández
2008-12-02 16:13 ` Linus Torvalds
2008-12-02 16:29 ` About git-bisect (was: Linux 2.6.28-rc7) Renato S. Yamane
2008-12-02 16:55 ` Sam Ravnborg
2008-12-02 17:05 ` Linus Torvalds
2008-12-02 17:01 ` Linus Torvalds
2008-12-02 18:49 ` Linux 2.6.28-rc7 Alejandro Riveira Fernández
2008-12-02 19:22 ` Alejandro Riveira Fernández
2008-12-02 19:23 ` Linus Torvalds
2008-12-02 19:45 ` Alejandro Riveira Fernández
2008-12-02 20:40 ` Linus Torvalds
2008-12-02 20:29 ` Al Viro [this message]
[not found] <fa.IDjfwzrT2B02+NHfmYwtICnzOOA@ifi.uio.no>
[not found] ` <fa.J8MFTCUT8El3sK8BuYDBvaMRaB8@ifi.uio.no>
[not found] ` <fa.q/4H3AtoJGSJ+i8tlXR4X35LFFU@ifi.uio.no>
[not found] ` <fa.98CeSgxJ/GGaLLyZ97s1oHgh7hE@ifi.uio.no>
2008-12-02 17:11 ` Michael B. Trausch
2008-12-02 18:06 ` Alejandro Riveira Fernández
2008-12-02 18:56 ` Michael B. Trausch
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=20081202202941.GG28946@ZenIV.linux.org.uk \
--to=viro@zeniv.linux.org.uk \
--cc=alistair@devzero.co.uk \
--cc=ariveira@gmail.com \
--cc=dbaryshkov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mike@trausch.us \
--cc=torvalds@linux-foundation.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