public inbox for cluster-cvs@sourceware.org help / color / mirror / Atom feed
From: rpeterso@sourceware.org To: cluster-cvs@sources.redhat.com Subject: cluster/gfs-kernel/src/gfs diaper.c ops_fstype.c Date: Fri, 23 Feb 2007 20:57:00 -0000 [thread overview] Message-ID: <20070223205729.18013.qmail@sourceware.org> (raw) CVSROOT: /cvs/cluster Module name: cluster Branch: STABLE Changes by: rpeterso@sourceware.org 2007-02-23 20:57:29 Modified files: gfs-kernel/src/gfs: diaper.c ops_fstype.c Log message: This fixes some issues reported on linux-cluster. Essentially, the previous code was deadlocking in some cases, primarily, when you run the sync command. That's because sync does a down_read on the s_umount semaphore. The deadlock was caused by some code I removed with the port to the 2.6.20 kernel. However, I removed it because s_umount was needed in the down state for unmounts. That's because the diaper device isn't managed by the normal mount path in vfs. I also fixed a kernel panic I discovered in testing when trying to mount an invalid fs; for example, trying to mount a gfs2 file system as gfs. Patches: http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/diaper.c.diff?cvsroot=cluster&only_with_tag=STABLE&r1=1.1.2.1.4.1.2.2&r2=1.1.2.1.4.1.2.3 http://sourceware.org/cgi-bin/cvsweb.cgi/cluster/gfs-kernel/src/gfs/ops_fstype.c.diff?cvsroot=cluster&only_with_tag=STABLE&r1=1.13.2.1.4.2.2.4&r2=1.13.2.1.4.2.2.5
reply other threads:[~2007-02-23 20:57 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070223205729.18013.qmail@sourceware.org \ --to=rpeterso@sourceware.org \ --cc=cluster-cvs@sources.redhat.com \ /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: linkBe 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; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).