From: "Nicholas A. Bellinger" <nab@linux-iscsi.org>
To: James Bottomley <James.Bottomley@suse.de>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
Randy Dunlap <randy.dunlap@oracle.com>,
Joel Becker <jlbec@evilplan.org>,
scsi <linux-scsi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Linux 2.6.38-rc4 (target_core: rmmod GP fault)
Date: Wed, 09 Feb 2011 12:20:35 -0800 [thread overview]
Message-ID: <1297282835.18212.57.camel@haakon2.linux-iscsi.org> (raw)
In-Reply-To: <1297282433.3016.43.camel@mulgrave.site>
On Wed, 2011-02-09 at 14:13 -0600, James Bottomley wrote:
> On Wed, 2011-02-09 at 12:02 -0800, Nicholas A. Bellinger wrote:
> > On Wed, 2011-02-09 at 11:00 -0800, Linus Torvalds wrote:
> > > On Wed, Feb 9, 2011 at 9:28 AM, Randy Dunlap <randy.dunlap@oracle.com> wrote:
> > > > x86_64, nearly allmodconfig. No target hardware.
<SNIP>
> > <nod> I believe the above patch resolves the specific rmmod issue.
> > However, during SLUB poisioning testing we also came across errors with
> > the incorrect use of struct config_item_operations->release() in
> > target_core_configfs.c and target_core_fabric_configfs.c code. The
> > series to address these was included in the last series to James here:
> >
> > [PATCH 00/12] target: Updates for .38-rc4
> > http://marc.info/?l=linux-scsi&m=129680191624837&w=2
> >
> > Note that this series for-38 mainline needs to be applied on top of the
> > original update series after the drivers/target/ mainline merge:
> >
> > [PATCH 00/24] target updates for .38-rc3 (v2)
> > http://marc.info/?l=linux-scsi&m=129632617326015&w=2
> >
> > The entire series is available from
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/nab/scsi-post-merge-2.6.git for-38-rc4
> >
> > James, please review + sign-off so we can get these updates into mainline.
>
> Firstly, could we get the serious bug fixes identified and separated
> from the general enhancement updates, so they can go in a fixes tree
> without depending on enhancements? The former category would include
> the /proc interface removal, since we don't want the legacy interface to
> be in a released kernel.
>
Everything in those two series should be considered bug fixes and
immediate for-38 mainline material.
The target_core_mib.c statistics logic using procfs seq_list() has been
removed in [PATCH 12/12] of the most recent series above.
Thanks,
--nab
next prev parent reply other threads:[~2011-02-09 20:20 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-08 0:23 Linux 2.6.38-rc4 Linus Torvalds
2011-02-08 10:17 ` lockdep: possible reason: unannotated irqs-off. (was: Re: Linux 2.6.38-rc4) Borislav Petkov
2011-02-08 10:41 ` Peter Zijlstra
2011-02-08 12:11 ` Yong Zhang
2011-02-08 12:14 ` [PATCH 2/2] timer: use local_bh_enable_force_wake() in del_timer_sync() Yong Zhang
2011-02-08 13:34 ` lockdep: possible reason: unannotated irqs-off. (was: Re: Linux 2.6.38-rc4) Yong Zhang
2011-02-08 13:48 ` Peter Zijlstra
2011-02-08 14:18 ` Peter Zijlstra
2011-02-08 15:15 ` Ingo Molnar
2011-02-08 15:51 ` [tip:core/urgent] Revert "lockdep, timer: Fix del_timer_sync() annotation" tip-bot for Peter Zijlstra
2011-02-09 1:46 ` lockdep: possible reason: unannotated irqs-off. (was: Re: Linux 2.6.38-rc4) Yong Zhang
2011-02-14 14:51 ` Yong Zhang
2011-02-14 18:53 ` Thomas Gleixner
2011-02-08 20:28 ` Heads up Linux 2.6.38-rc4 compile problems Eric W. Biederman
2011-02-08 20:44 ` Linus Torvalds
2011-02-09 9:01 ` Eric W. Biederman
2011-02-09 14:59 ` Alex Riesen
2011-02-09 16:02 ` Linus Torvalds
2011-02-13 17:39 ` Linus Torvalds
2011-02-14 2:04 ` Eric W. Biederman
2011-02-14 2:45 ` Linus Torvalds
2011-02-14 3:40 ` Eric W. Biederman
2011-02-14 5:34 ` Eric W. Biederman
2011-02-14 15:26 ` Linus Torvalds
2011-02-14 15:37 ` Eric W. Biederman
2011-02-14 16:37 ` Linus Torvalds
2011-02-14 17:39 ` Eric W. Biederman
2011-02-14 17:49 ` Linus Torvalds
2011-02-14 18:08 ` Linus Torvalds
2011-02-14 19:44 ` Eric W. Biederman
2011-02-14 20:13 ` Andrew Morton
2011-02-14 18:25 ` Andi Kleen
2011-02-14 16:58 ` Mike Snitzer
2011-02-15 14:07 ` [Crash-utility] " Dave Anderson
2011-02-09 17:08 ` Linux 2.6.38-rc4 (test_nx: BUG) Randy Dunlap
2011-02-09 17:10 ` Arjan van de Ven
2011-02-17 19:33 ` Kees Cook
2011-02-09 17:24 ` Linux 2.6.38-rc4 (hysdn: BUG) Randy Dunlap
2011-02-09 19:44 ` Linus Torvalds
2011-02-09 21:25 ` Randy Dunlap
2011-02-09 21:57 ` David Miller
2011-02-09 22:00 ` Linus Torvalds
2011-02-09 17:26 ` Linux 2.6.38-rc4 (tty/ifx6x60: BUG) Randy Dunlap
2011-02-09 18:28 ` Alan Cox
2011-02-09 17:28 ` Linux 2.6.38-rc4 (target_core: rmmod GP fault) Randy Dunlap
2011-02-09 19:00 ` Linus Torvalds
2011-02-09 20:02 ` Nicholas A. Bellinger
2011-02-09 20:13 ` James Bottomley
2011-02-09 20:20 ` Nicholas A. Bellinger [this message]
2011-02-09 20:28 ` James Bottomley
2011-02-09 20:44 ` Nicholas A. Bellinger
2011-02-09 17:36 ` Linux 2.6.38-rc4 (other bugs) Randy Dunlap
2011-02-09 22:01 ` David Miller
2011-02-09 22:16 ` Randy Dunlap
2011-02-10 4:58 ` Linux 2.6.38-rc4 (other bugs: x25) Randy Dunlap
2011-02-10 5:48 ` David Miller
2011-02-10 6:29 ` Randy Dunlap
2011-02-10 6:35 ` David Miller
2011-02-10 19:34 ` Linux 2.6.38-rc4 (other bugs: ipmi Oops) Randy Dunlap
2011-02-10 20:03 ` Linus Torvalds
2011-02-10 20:08 ` Corey Minyard
2011-02-10 21:41 ` Randy Dunlap
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=1297282835.18212.57.camel@haakon2.linux-iscsi.org \
--to=nab@linux-iscsi.org \
--cc=James.Bottomley@suse.de \
--cc=jlbec@evilplan.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=randy.dunlap@oracle.com \
--cc=torvalds@linux-foundation.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®