public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Willy Tarreau <w@1wt.eu>
To: a.afach@hybridware.co
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Reiserfs Bug on linux 3.4.9
Date: Thu, 23 Jul 2015 12:51:39 +0200	[thread overview]
Message-ID: <20150723105139.GA2938@1wt.eu> (raw)
In-Reply-To: <a90f305d44dc64ad482d559deef8ba87@hybridware.co>

Hello,

On Thu, Jul 23, 2015 at 03:51:47AM -0500, a.afach@hybridware.co wrote:
> Dears
>  i have the following bug on reiserfs on gentoo linux kernel  3.4.9 how
> can i solve it

First, your kernel is totally outdated, you've been skipping 3 years of
fixes in 100 updates roughly covering 4600 bugs :

$ git log --oneline v3.4.9..v3.4.108 | wc -l
4683

7 of them directly affect reiserfs, and it's very likely that a number of
the other ones could as well :

$ git log --oneline v3.4.9..v3.4.108  -- fs/reiserfs/
15e5f90 reiserfs: fix race in readdir
b57644a reiserfs: Fix warning and inode leak when deleting inode with xattrs
a23d631 reiserfs: Protect reiserfs_quota_write() with write lock
8c7dcc4 reiserfs: Move quota calls out of write lock
8ed4d1c reiserfs: Protect reiserfs_quota_on() with write lock
394cbbc reiserfs: Fix lock ordering during remount
530258f tmpfs,ceph,gfs2,isofs,reiserfs,xfs: fix fh_len checking

So you first need to update your kernel to get the latest fixes. You're
lucky, your branch is still maintained!

Best regards,
Willy


      reply	other threads:[~2015-07-23 10:51 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-23  8:51 Reiserfs Bug on linux 3.4.9 a.afach
2015-07-23 10:51 ` Willy Tarreau [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=20150723105139.GA2938@1wt.eu \
    --to=w@1wt.eu \
    --cc=a.afach@hybridware.co \
    --cc=linux-kernel@vger.kernel.org \
    --cc=stable@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