reiserfs-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: reiserfs-devel@vger.kernel.org
Subject: Your Kernel Bug Tracker bug list needs attention.
Date: Tue, 30 Oct 2012 15:50:05 +0000 (UTC)	[thread overview]
Message-ID: <20121030155005.D583E11FF17@bugzilla.kernel.org> (raw)

[This e-mail has been automatically generated.]

You have one or more bugs assigned to you in the Kernel Bug Tracker bug tracking system (https://bugzilla.kernel.org/) that require
attention.

All of these bugs are in the NEW orREOPENED state, and have not been
touched in 7 days or more.
You need to take a look at them, and decide on an initial action.

Generally, this means one of three things:

(1) You decide this bug is really quick to deal with (like, it's INVALID),
    and so you get rid of it immediately.
(2) You decide the bug doesn't belong to you, and you reassign it to
    someone else. (Hint: if you don't know who to reassign it to, make
    sure that the Component field seems reasonable, and then use the
    "Reassign bug to default assignee of selected component" option.)
(3) You decide the bug belongs to you, but you can't solve it this moment.
    Just use the "Accept bug" command.

To get a list of all NEW/REOPENED bugs, you can use this URL (bookmark
it if you like!):
https://bugzilla.kernel.org/buglist.cgi?bug_status=NEW&bug_status=REOPENED&assigned_to=reiserfs-devel@vger.kernel.org

Or, you can use the general query page, at 
https://bugzilla.kernel.org/query.cgi

Appended below are the individual URLs to get to all of your NEW bugs
that haven't been touched for 7 days or more.

You will get this message once a day until you've dealt with these bugs!

 crafted reiserfs filesystem image local DoS (reboot)
    -> https://bugzilla.kernel.org/show_bug.cgi?id=12335
 reiserfs panic (device null superblock)
    -> https://bugzilla.kernel.org/show_bug.cgi?id=13037
 reiserfs locking (v2)
    -> https://bugzilla.kernel.org/show_bug.cgi?id=16334
 Reiserfs hang with dataloss sometimes
    -> https://bugzilla.kernel.org/show_bug.cgi?id=29162
 Error-valued pointer dereferences
    -> https://bugzilla.kernel.org/show_bug.cgi?id=34362
 Error-valued pointer used in pointer arithmetic
    -> https://bugzilla.kernel.org/show_bug.cgi?id=34372
 Sometimes a partition hangs up: any process freezes if touches a file/directory on this partition
    -> https://bugzilla.kernel.org/show_bug.cgi?id=37782
 PROBLEM: problem with kswap/raiserfs
    -> https://bugzilla.kernel.org/show_bug.cgi?id=45431

             reply	other threads:[~2012-10-30 15:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-30 15:50 bugzilla-daemon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2012-10-31 15:50 Your Kernel Bug Tracker bug list needs attention bugzilla-daemon

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=20121030155005.D583E11FF17@bugzilla.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=reiserfs-devel@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).