All of lore.kernel.org
 help / color / mirror / Atom feed
From: Al Viro <viro@ftp.linux.org.uk>
To: Ingo Molnar <mingo@elte.hu>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Greg KH <gregkh@suse.de>, Peter Zijlstra <a.p.zijlstra@chello.nl>
Subject: Re: [bug] crash when reading /proc/mounts (was: Re: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series..)
Date: Wed, 3 Oct 2007 14:34:22 +0100	[thread overview]
Message-ID: <20071003133422.GI8181@ftp.linux.org.uk> (raw)
In-Reply-To: <20071003084607.GC32218@elte.hu>

On Wed, Oct 03, 2007 at 10:46:07AM +0200, Ingo Molnar wrote:
> 
> hm, i just triggered the procfs crash below with -rc9 on a testbox. 
> Config attached. It's easy to reproduce it via 'service sshd restart'. 
> The crash site is:
> 
>  (gdb) list *0xc017599d
>  0xc017599d is in seq_path (fs/seq_file.c:354).
>  349             if (m->count < m->size) {
>  350                     char *s = m->buf + m->count;
>  351                     char *p = d_path(dentry, mnt, s, m->size - m->count);
>  352                     if (!IS_ERR(p)) {
>  353                             while (s <= p) {
>  354                                     char c = *p++;
>  355                                     if (!c) {
>  356                                             p = m->buf + m->count;
>  357                                             m->count = s - m->buf;
>  358                                             return s - p;
>  (gdb)
> 
> any ideas? Fortunately i was able to do an strace of the incident:

Charming...  So we get d_path() either returning junk or we get something
that isn't NUL-terminated.  Which one it is?  I.e. what does p look like
and what's in s?

  parent reply	other threads:[~2007-10-03 13:34 UTC|newest]

Thread overview: 85+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <alpine.LFD.0.999.0710012029400.3579@woody.linux-foundation.org >
2007-10-02  3:41 ` Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series Linus Torvalds
2007-10-02  9:17   ` Thomas Gleixner
2007-10-02  9:21     ` Andi Kleen
2007-10-02 10:37       ` Jeff Garzik
2007-10-02 10:48         ` Andi Kleen
2007-10-02 11:05           ` Thomas Gleixner
2007-10-02 14:07             ` Ingo Molnar
2007-10-02 14:23               ` Andi Kleen
2007-10-02 14:31                 ` Ingo Molnar
2007-10-02 14:54                   ` Andi Kleen
2007-10-02 14:58                   ` Sam Ravnborg
2007-10-02 15:24                     ` Andi Kleen
2007-10-02 15:27                     ` Ingo Molnar
2007-10-02 15:30                     ` Thomas Gleixner
2007-10-02 15:40                       ` Sam Ravnborg
2007-10-02 12:04       ` Jiri Kosina
2007-10-02 20:12     ` Rafael J. Wysocki
2007-10-02 20:11       ` Andrew Morton
2007-10-02 20:31         ` Rafael J. Wysocki
2007-10-02 20:32         ` Roland Dreier
2007-10-03  3:53     ` Eric St-Laurent
2007-10-02 12:07   ` Mel Gorman
2007-10-02 12:15     ` Ingo Molnar
2007-10-02 17:21       ` Mel Gorman
2007-10-02 22:09         ` Bill Davidsen
2007-10-03  0:37           ` Mel Gorman
2007-10-03  8:21             ` Ingo Molnar
2007-10-03 12:51               ` Mel Gorman
2007-10-22 15:56                 ` Ingo Molnar
2007-10-03  8:19         ` Ingo Molnar
2007-10-02 14:44   ` John Stoffel
2007-10-02 15:03     ` Ingo Molnar
2007-10-02 15:45     ` John Stoffel
2007-10-02 22:13     ` Bill Davidsen
2007-10-02 22:44   ` Willy Tarreau
2007-10-02 22:51   ` Alistair John Strachan
2007-10-02 23:00     ` Glauber de Oliveira Costa
2007-10-05  5:41       ` Ingo Molnar
2007-10-05  5:38     ` Ingo Molnar
2007-10-05  6:11       ` Sam Ravnborg
2007-10-05  8:32         ` Thomas Gleixner
2007-10-07 23:44           ` Alistair John Strachan
2007-10-02 23:07   ` Diego Calleja
2007-10-02 23:32     ` Linus Torvalds
2007-10-03 15:28       ` Diego Calleja
2007-10-03  8:46   ` [bug] crash when reading /proc/mounts (was: Re: Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series..) Ingo Molnar
2007-10-03  8:50     ` Ingo Molnar
2007-10-03  9:12       ` Ingo Molnar
2007-10-03  9:23         ` Ingo Molnar
2007-10-03 13:34     ` Al Viro [this message]
2007-10-03 14:08       ` Ingo Molnar
2007-10-03 14:26         ` Al Viro
2007-10-03 15:12           ` Arjan van de Ven
2007-10-03 15:11     ` Linus Torvalds
2007-10-03 15:40       ` Ingo Molnar
2007-10-03 16:07         ` Linus Torvalds
2007-10-03 15:47       ` Linus Torvalds
2007-10-03 15:49         ` Ingo Molnar
2007-10-03 16:07           ` Ingo Molnar
2007-10-03 15:51       ` Alan Cox
2007-10-03 16:09         ` Linus Torvalds
2007-10-03 16:25           ` Jan Engelhardt
2007-10-03 17:07             ` Linus Torvalds
2007-10-04 14:12       ` Adrian Bunk
2007-10-04 15:08         ` Alexey Dobriyan
2007-10-03 14:21   ` Linux 2.6.23-rc9 and a heads-up for the 2.6.24 series Timo Jantunen
2007-10-03 19:07   ` Jeff Garzik
2007-10-03 19:25     ` Linus Torvalds
2007-10-04 11:55   ` [patch] net, 9p: build fix with !CONFIG_SYSCTL Ingo Molnar
2007-10-04 17:05   ` [BUG] Linux 2.6.23-rc9 and MAX_ARG_PAGES Mathieu Chouquet-Stringer
2007-10-04 17:17     ` Peter Zijlstra
2007-10-04 20:47       ` Mathieu Chouquet-Stringer
2007-10-04 21:58       ` Mathieu Chouquet-Stringer
2007-10-04 17:27     ` Linus Torvalds
2007-10-04 20:44       ` Mathieu Chouquet-Stringer
2007-10-04 21:21         ` Linus Torvalds
2007-10-04 22:27           ` Paul Mackerras
2007-10-05  0:12             ` Linus Torvalds
2007-10-05  3:22               ` Mathieu Chouquet-Stringer
2007-10-05  7:43                 ` Peter Zijlstra
2007-10-04 21:50     ` Chuck Ebbert
2007-10-04 21:54       ` Mathieu Chouquet-Stringer
2007-10-06  8:29     ` Hans-Peter Jansen
2007-10-06 11:29       ` Hans-Peter Jansen
2007-10-06 17:36     ` Bill Davidsen

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=20071003133422.GI8181@ftp.linux.org.uk \
    --to=viro@ftp.linux.org.uk \
    --cc=a.p.zijlstra@chello.nl \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --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 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.