From: Nikita Danilov <Nikita@Namesys.COM>
To: viro@parcelfarce.linux.theplanet.co.uk
Cc: Zan Lynx <zlynx@acm.org>,
linux-kernel@vger.kernel.org, reiserfs-list@namesys.com,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: 2.6.0-test6 crash while reading files in /proc/fs/reiserfs/sda1
Date: Thu, 2 Oct 2003 19:40:51 +0400 [thread overview]
Message-ID: <16252.18179.242071.708771@laputa.namesys.com> (raw)
In-Reply-To: <20031002120133.GC7665@parcelfarce.linux.theplanet.co.uk>
viro@parcelfarce.linux.theplanet.co.uk writes:
> [Linus, please wait with applying the patch below until ACK from Nikita, OK?]
>
[...]
>
>
> If you are OK with the patch below - please ACK it. AFAICS it's the minimal
> fix and combined with optimistic sget() patch it should address all objections.
Yes, it works (cum optimistic sget()).
>
> diff -urN B6-rest/fs/reiserfs/procfs.c B6-current/fs/reiserfs/procfs.c
> --- B6-rest/fs/reiserfs/procfs.c Sat Sep 27 22:04:57 2003
> +++ B6-current/fs/reiserfs/procfs.c Thu Oct 2 07:57:31 2003
> @@ -478,14 +478,15 @@
> static void *r_next(struct seq_file *m, void *v, loff_t *pos)
> {
> ++*pos;
> + if (v)
> + deactivate_super(v);
> return NULL;
> }
>
> static void r_stop(struct seq_file *m, void *v)
> {
> - struct proc_dir_entry *de = m->private;
> - struct super_block *s = de->data;
> - deactivate_super(s);
> + if (v)
> + deactivate_super(v);
> }
>
> static int r_show(struct seq_file *m, void *v)
Nikita.
prev parent reply other threads:[~2003-10-02 15:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-30 15:44 Zan Lynx
2003-09-30 15:51 ` Jonathan Briggs
2003-09-30 16:06 ` Vitaly Fertman
2003-09-30 19:18 ` Hans Reiser
2003-10-01 10:11 ` Vitaly Fertman
2003-10-01 14:44 ` Zan Lynx
2003-10-01 17:15 ` Vitaly Fertman
2003-10-01 17:54 ` Nikita Danilov
2003-10-01 18:43 ` viro
2003-10-02 10:08 ` Nikita Danilov
2003-10-02 10:26 ` viro
2003-10-02 10:35 ` viro
2003-10-02 10:51 ` Nikita Danilov
2003-10-02 12:01 ` viro
2003-10-02 15:40 ` Nikita Danilov [this message]
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=16252.18179.242071.708771@laputa.namesys.com \
--to=nikita@namesys.com \
--cc=linux-kernel@vger.kernel.org \
--cc=reiserfs-list@namesys.com \
--cc=torvalds@osdl.org \
--cc=viro@parcelfarce.linux.theplanet.co.uk \
--cc=zlynx@acm.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
all inboxes | Powered by JetHome®