mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Frantisek Hrbata <frantisek.hrbata@avg.com>
To: John Ogness <dazukocode@ogness.net>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"hch@infradead.org" <hch@infradead.org>,
	"alan@lxorguk.ukuu.org.uk" <alan@lxorguk.ukuu.org.uk>,
	"viro@zeniv.linux.org.uk" <viro@zeniv.linux.org.uk>,
	"malware-list@lists.printk.net" <malware-list@lists.printk.net>
Subject: Re: [malware-list] [PATCHv2 3/5] VFS: DazukoFS, stackable-fs,	file access control
Date: Sat, 21 Feb 2009 19:11:24 +0100	[thread overview]
Message-ID: <20090221191124.238743a4@humpdell> (raw)
In-Reply-To: <86skmvfhx6.fsf_-_@johno.fn.ogness.net>

On Tue, 3 Feb 2009 20:18:29 +0100
John Ogness <dazukocode@ogness.net> wrote:

> +/**
> + * dazukofs_add_group - add a new group
> + * @name: the name of the group to add
> + *
> + * Description: This function is called by the device layer to add a new
> + * group. It returns success if the group has been successfully created
> + * or if the group already exists.
> + *
> + * Returns 0 on success.
> + */
> +int dazukofs_add_group(const char *name)
> +{
> +       int ret = 0;
> +       int already_exists;
> +       int available_id = 0;
> +       struct dazukofs_group *grp;
> +
> +       write_lock(&group_count_rwlock);
> +
> +       mutex_lock(&work_mutex);

Hi,

you cannot hold spinlock and try to acquire mutex.

write_lock() -> preempt_disable() vs mutex_lock -> schedule()

-FH

  parent reply	other threads:[~2009-02-21 18:20 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-03 19:14 [PATCHv2 0/5] " John Ogness
2009-02-03 19:15 ` [PATCHv2 1/5] " John Ogness
2009-02-03 19:17   ` [PATCHv2 2/5] " John Ogness
2009-02-03 19:18     ` [PATCHv2 3/5] " John Ogness
2009-02-03 19:19       ` [PATCHv2 4/5] " John Ogness
2009-02-03 19:20         ` [PATCHv2 5/5] " John Ogness
2009-02-12 20:24           ` Eric W. Biederman
2009-02-12 20:20       ` [PATCHv2 3/5] " Eric W. Biederman
2009-02-17  8:55         ` John Ogness
2009-02-18  0:41           ` Eric W. Biederman
2009-02-21 18:11       ` Frantisek Hrbata [this message]
2009-02-12 16:00     ` [PATCHv2 2/5] " Jan Engelhardt
2009-02-13 19:33       ` John Ogness
2009-02-12 20:14     ` Eric W. Biederman
2009-02-13 19:39       ` John Ogness
2009-02-12 15:27   ` [PATCHv2 1/5] " Jan Engelhardt
2009-02-12 15:31     ` Al Viro
2009-02-12 15:59       ` Jan Engelhardt
2009-02-12 16:47         ` Al Viro
2009-02-13 19:31     ` John Ogness
2009-02-13 19:48       ` Al Viro
2009-02-13 20:00       ` Jan Engelhardt
2009-02-13 20:25         ` Al Viro
2009-02-14  8:43           ` John Ogness

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=20090221191124.238743a4@humpdell \
    --to=frantisek.hrbata@avg.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=dazukocode@ogness.net \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=malware-list@lists.printk.net \
    --cc=viro@zeniv.linux.org.uk \
    /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

Powered by JetHome